I've been trying to update my Verizon Galaxy Nexus to Jelly Bean with the OTA update. I've tried the Framework workaround but that doesn't seem to work. I've seen where people have been able to get it to work by deleting the cache, but when I look in the cache it has 0 bytes. I was wondering how I can get cache on the Google Services Framework and then delete it from there. I think that may work but I'm not sure. Any Suggestions? Thanks!
manual update. done
You can NOT force this update unless you flash it yourself.
Millions of Verizon iPhones updated in ONE EFFING day, and somehow the Galaxy Nexus takes ???
You can always call and complain.
Sent from my Galaxy Nexus using xda premium
Yup. You have to wait for it to be pushed. If you don't want to wait efrants guide makes it as easy as it gets.
http://forum.xda-developers.com/showthread.php?t=1419170
Sent from my Galaxy Nexus using Tapatalk 2
power off
JSHART said:
I've been trying to update my Verizon Galaxy Nexus to Jelly Bean with the OTA update. I've tried the Framework workaround but that doesn't seem to work. I've seen where people have been able to get it to work by deleting the cache, but when I look in the cache it has 0 bytes. I was wondering how I can get cache on the Google Services Framework and then delete it from there. I think that may work but I'm not sure. Any Suggestions? Thanks!
Click to expand...
Click to collapse
This method to force the update worked on the first try:
1. Go to Settings - Apps - Google Services Framework 2. Force stop GSF 3. Clear data in GSF (If data is at 0, there is nothing to clear and you can proceed) 4. Power down and restart phone 5. Go to Settings - About Phone -System Updates, press "Check now" 6. The initial response was that the phone was up to date, but within a few seconds the message about Jelly Bean popped up and the update started to download.
Note step 4 (powering down & restarting phone) seemed to make the difference. Several attempts without this step failed. Also note I was on wifi.
gdad said:
This method to force the update worked on the first try:
1. Go to Settings - Apps - Google Services Framework 2. Force stop GSF 3. Clear data in GSF (If data is at 0, there is nothing to clear and you can proceed) 4. Power down and restart phone 5. Go to Settings - About Phone -System Updates, press "Check now" 6. The initial response was that the phone was up to date, but within a few seconds the message about Jelly Bean popped up and the update started to download.
Note step 4 (powering down & restarting phone) seemed to make the difference. Several attempts without this step failed. Also note I was on wifi.
Click to expand...
Click to collapse
I can confirm these steps worked on my device as well, cheers!
didn't work for me
If I force closed it, it didn't work. If I just clear data it worked first try.
Sent from my SCH-I510 using xda app-developers app
this sucks..
This also worked for me ... downloading now.
bubarub said:
If I force closed it, it didn't work. If I just clear data it worked first try.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
This also worked for me. I am downloading now.
gdad said:
This method to force the update worked on the first try:
1. Go to Settings - Apps - Google Services Framework 2. Force stop GSF 3. Clear data in GSF (If data is at 0, there is nothing to clear and you can proceed) 4. Power down and restart phone 5. Go to Settings - About Phone -System Updates, press "Check now" 6. The initial response was that the phone was up to date, but within a few seconds the message about Jelly Bean popped up and the update started to download.
Note step 4 (powering down & restarting phone) seemed to make the difference. Several attempts without this step failed. Also note I was on wifi.
Click to expand...
Click to collapse
Had been trying this for the past 2 days without restarting the phone. I followed these instructions exactly and the third time I tired it, I finally got the jelly bean OTA screen. Updating now. THANKS!
Related
Anyone have this happening on their glide?
I tried all of the following:
- clear data
- clear cache
- wipe cache on boot screen
- delete and reinstall the apk.
- 3G only instead of Wifi.
When I reset everything, all works fine until I try to update an app and that's when the FC's begin
The google play apk I have is v3.5.15
Is this what you guys have as well?
I'm seeing few other posts on other forums, but no solutions yet.
clockwork58 said:
Anyone have this happening on their glide?
I tried all of the following:
- clear data
- clear cache
- wipe cache on boot screen
- delete and reinstall the apk.
- 3G only instead of Wifi.
When I reset everything, all works fine until I try to update an app and that's when the FC's begin
The google play apk I have is v3.5.15
Is this what you guys have as well?
I'm seeing few other posts on other forums, but no solutions yet.
Click to expand...
Click to collapse
Try reselecting your Language in Settings > Language and Keyboard, after re-selecting, a media scan should occur, then try launching Market Play Store
no luck.
Damn that sucks bro. I had 3 updates and i updated with no problem. On both my KF and Evo 4G.
What rom are you using?
Sent from my Kindle Fire using XDA App
clockwork58 said:
no luck.
Click to expand...
Click to collapse
okay last one that i think worked on me before:
- turn off internet first, then uninstall updates on Play store
- reselect language again,
- turn data/wifi on back, wait for Market to update to Play store
I'm using Stock Rogers ROM but the phone is rooted.
I've had quite a few calls missed recently (doesn't even ring), so i think i think i think I'm gonna give it a factory reset.
maybe take a gander and some of the new custom roms out there now as well.
Wow that was painful...
Did a factory reset and GPlay still FC's
Did a full factory reset + Wipe USB and SDCard storage and GPlay still FC's (v3.5.15)
I now have found a tool that allows me to download APK's from Gplay web site and load them manually onto my phone, until Google can fix their latest version of Gplay which has affected others as well.
clockwork58 said:
I'm using Stock Rogers ROM but the phone is rooted.
I've had quite a few calls missed recently (doesn't even ring), so i think i think i think I'm gonna give it a factory reset.
maybe take a gander and some of the new custom roms out there now as well.
Click to expand...
Click to collapse
I flashed back to Rogers Stock a few days back to replicate your issue, but until now, my Play Store is still at v3.4.7 and no FCs. I am still investigating for I got this one before but solved it with just uninstalling updates and re-updating...
clockwork58 said:
Wow that was painful...
Did a factory reset and GPlay still FC's
Did a full factory reset + Wipe USB and SDCard storage and GPlay still FC's (v3.5.15)
I now have found a tool that allows me to download APK's from Gplay web site and load them manually onto my phone, until Google can fix their latest version of Gplay which has affected others as well.
Click to expand...
Click to collapse
Cool how do you do this? I have a cousin of mine that has the HP touch pad with Cynagen Mod installed on it but when he goes to the store a lot of apps say not available for you're device. So then he asks me to get them and backup my app with Astro and then send him the apk. If he used the tool you use he would not need my help.
dudejb said:
Cool how do you do this? I have a cousin of mine that has the HP touch pad with Cynagen Mod installed on it but when he goes to the store a lot of apps say not available for you're device. So then he asks me to get them and backup my app with Astro and then send him the apk. If he used the tool you use he would not need my help.
Click to expand...
Click to collapse
http://codekiem.com/2012/02/24/apk-downloader/
Finally got my Nexus to start downloading Jelly Bean after 3 days of nonstop tapping the check now. Follow these steps an you will be using the buttery goodness like me.
-Go into Setting -> Apps -> All -> Google Services Framework
-You will see a button for “Clear Data”; clear it.
-Go into your dialer and type *#*#2432546#*#* - This will cause a ‘force checkin’. You will notice that it shows “checkin succeeded” across the top.
Go back to Setting -> About Phone -> System updates and then click the check now button.
YOU HAVE TO BE ON WIFI TO DOWNLOAD UPDATE!!!
Hit the thanks button if it helps!!!! Best of luck!
I think there's a lot of steps that are being added in and making a ton of variants of this frameworks... 'exploit'.
People might just have the right timing or something...
Sent from my Galaxy Nexus using xda premium
I hope someone can help me...I flashed takju image using efrant's guide a while back. Did everything to the letter. Then today I did the trick above, except just cleared cache and data then went to check update and it triggered the ota jellybean. But the ota failed and I saw a sad android bot with red sign and a ! In the middle. Phone finally restarted on its own and is on same ics 4.0.4.
Any ideas what went wrong???!!
Sent from my Galaxy Nexus using xda app-developers app
You need to be connected to a WIFI for download the update, look at my screenshot (its in spanish But it says: "for WIFI only until july 12") so there.
Hope it helps , remember you have be on WiFi.
Sent from my Galaxy Nexus using xda app-developers app
mcniick9 said:
Finally got my Nexus to start downloading Jelly Bean after 3 days of nonstop tapping the check now. Follow these steps an you will be using the buttery goodness like me.
-Go into Setting -> Apps -> All -> Google Services Framework
-You will see a button for “Clear Data”; clear it.
-Go into your dialer and type *#*#2432546#*#* - This will cause a ‘force checkin’. You will notice that it shows “checkin succeeded” across the top.
Go back to Setting -> About Phone -> System updates and then click the check now button.
Best of luck!
Click to expand...
Click to collapse
Non of this works JBQ has stated this himself, it was just your time on the server. It could take weeks to update all the gsm phones as bandwidth isn't free or unlimited.
Sent from my Galaxy Nexus using Tapatalk 2
I was on wifi, the update downloaded, then I saw the sad bot with the exclamation point. I was worried it was bricked but then phone restarted. Also why is it showing 4.1? Shouldn't it be 4.1.1?
Sent from my Galaxy Nexus using xda app-developers app
mcniick9 said:
Finally got my Nexus to start downloading Jelly Bean after 3 days of nonstop tapping the check now. Follow these steps an you will be using the buttery goodness like me.
-Go into Setting -> Apps -> All -> Google Services Framework
-You will see a button for “Clear Data”; clear it.
-Go into your dialer and type *#*#2432546#*#* - This will cause a ‘force checkin’. You will notice that it shows “checkin succeeded” across the top.
Go back to Setting -> About Phone -> System updates and then click the check now button.
Best of luck!
Click to expand...
Click to collapse
I tried this but I keep getting the same 4.0.4 update for some reason and no JB. I'm running yakju imm76d gnex dunno why it keeps cycling to the same exact update
I just cleared and force stopped the framework app. After a out 20 tries, it worked.
Sent from my Galaxy Nexus using Tapatalk 2
I followed the following steps to get the OTA update in the first attempt.
i) Force stop the Google Services Framework.
ii)Clear data of Google Services Framework
iii) Go to System Updates and check again and voila !!!
Sent from my Galaxy Nexus using xda app-developers app
Worked! Although the force checkin was not necessary. Just force-stopped Google Services Framework, cleared it's cached data and checked for updates a couple of times. The JB update screen came up approx. on the 4th or 5th try. Obviously Google's servers give the update to every "n"-th requesting device. So doing this cycle enough times guarantees success.
(Of course this works only if you're Ice Cream Sandwich is from Google ... if your phone's Android came from a phone company -eg. Samsung-, you might not be so lucky since your phone will check in with the phone company's servers and not Google's servers.)
I understand that It may be the time for the update. Normal update check does not get the update pushed but the framework fix does.
anupash said:
I followed the following steps to get the OTA update in the first attempt.
i) Force stop the Google Services Framework.
ii)Clear data of Google Services Framework
iii) Go to System Updates and check again and voila !!!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Worked on first try. apparently the force stop is what helped. thanks
Just worked for me!!!! YES! Thanks guys!
adadabhoy said:
I tried this but I keep getting the same 4.0.4 update for some reason and no JB. I'm running yakju imm76d gnex dunno why it keeps cycling to the same exact update
Click to expand...
Click to collapse
You must first update to IMM76I (android 4.0.4) and then you should receive update to JRO03C (android 4.1.1)
THANKS! worked great
eskeyy said:
You must first update to IMM76I (android 4.0.4) and then you should receive update to JRO03C (android 4.1.1)
Click to expand...
Click to collapse
yh i realized that and am trying to do that right now
mine just keeps saying:
E: failed to verify whole-file signature
E: signature verification failed.
Why is that ??
cgp1 said:
THANKS! worked great
Click to expand...
Click to collapse
glad to help
It worked perfectly! I've been trying to get the OTA all week, smashing that "check now" button and nothing happend, but now, thanks to this, it worked perfectly.
Thanks!
Almost.
Did this AND then rebooted before it worked for me.
Just recieved OTA update on my stock gnex using the google-framework cache clear/close process method.
I cleared cache of google-framework process and then stopped it, rebooted the device and after reboot was done i got the OTA, installed it and phone booted again. update was installed without any problems.
BUT: when going into settings => location access => and then tapping "access to my location" settings force closes.
i rebooted the phone a few times and tried everything that came into my mind, no solution
anybody got the same problem or maybe even a solution?
gaga111 said:
Just recieved OTA update on my stock gnex using the google-framework cache clear/close process method.
I cleared cache of google-framework process and then stopped it, rebooted the device and after reboot was done i got the OTA, installed it and phone booted again. update was installed without any problems.
BUT: when going into settings => location access => and then tapping "access to my location" settings force closes.
i rebooted the phone a few times and tried everything that came into my mind, no solution
anybody got the same problem or maybe even a solution?
Click to expand...
Click to collapse
No problems for me. Ive just got 4.1.2
Anbody else :S
Just to be clear.. i dont mean switching it on and off
Sent from my Galaxy Nexus using xda app-developers app
edit:
seems like light flow is causing the force close...
as soon as i deactivate lightflow from the accessibility settings this doesnt happen anymore
gaga111 said:
Anbody else :S
as soon as i deactivate lightflow from the accessibility settings this doesnt happen anymore
Click to expand...
Click to collapse
Same problem here and that fixes it for me too! Happens on my wife's Nexus 7 too, but she has NoLED there so this may be a bug that has to do with anything enabled under accessibility settings (or at least not ONLY Light Flow).
Edit: I wonder if this is related:
http://forum.swype.com/showthread.p...Swype-Issue-Thread&p=35850&posted=1#post35850
"Note: We have found that this issue is related to running apps that have settings in the accessibility menu in Android settings. In the meantime, you should be able to use Swype by disabling any apps that are in Android Settings > Accessibility."
Sounds like 4.1.2 has some kind of Accessibility bug,
I'm trying to use the Android Device Manager, but I only get one device and no options to change..
I have an Samsung Galaxy Nexus with android 4.3 (JWR66V)
Could this have anything to do with me trying to root my device (Nexus Root Toolkit)?
I tried to root, but even though I got a message that my device was rooted, It's still un-rooted (But with unlocked bootloader)
The only device that shows up for me is my son's Nexus 7, which I have a profile on. My Galaxy Nexus doesn't show up and there's no drop down to select it.
What version of the toolkit did you use? If it wasn't the latest version (1.6.8 as of this writing) there may be additional steps required (beyond what's in the toolkit UI) when rooting 4.3.
I have allowed Device Manager in Settings, but on the web I see No active devices.
UncleMike said:
What version of the toolkit did you use? If it wasn't the latest version (1.6.8 as of this writing) there may be additional steps required (beyond what's in the toolkit UI) when rooting 4.3.
Click to expand...
Click to collapse
Latest version...
orbit09 said:
I have allowed Device Manager in Settings, but on the web I see No active devices.
Click to expand...
Click to collapse
Same here.. Only my tablet is showing..
Sweet! I'm not the only one with this problem, But I think I found the fix. It worked for me. I too am running a Galaxy Nexus on 4.3
If your Android device doesn't appear in Android Device Manager, or if you see Unknown location despite your device being online and running Google Play services version 3.2.25 or higher, follow these steps:
1. Open Google Settings from your device's apps menu.
2. Touch Android Device Manager.
3. Uncheck Allow remote factory reset.
4. Go to your device's main Settings menu, then touch Apps > All > Google Play services.
5. Touch Clear Data. Note that this action doesn't remove personal data.
6. Go back to Google Settings and select Allow remote factory reset.
7. Restart your device.
Make sure you follow the directiions exactly or it won't work
majorcovert said:
Sweet! I'm not the only one with this problem, But I think I found the fix. It worked for me. I too am running a Galaxy Nexus on 4.3
If your Android device doesn't appear in Android Device Manager, or if you see Unknown location despite your device being online and running Google Play services version 3.2.25 or higher, follow these steps:
1. Open Google Settings from your device's apps menu.
2. Touch Android Device Manager.
3. Uncheck Allow remote factory reset.
4. Go to your device's main Settings menu, then touch Apps > All > Google Play services.
5. Touch Clear Data. Note that this action doesn't remove personal data.
6. Go back to Google Settings and select Allow remote factory reset.
7. Restart your device.
Make sure you follow the directiions exactly or it won't work
Click to expand...
Click to collapse
doesnt work for me.....
pandorra said:
doesnt work for me.....
Click to expand...
Click to collapse
it did work for me,thx.
in my case my device did not appear in the android device managerpage, now it appear.
thx:laugh::good::good::good::good::good::good::good:
Dude!!!! Thanks a million times!!!!!!
majorcovert said:
sweet! I'm not the only one with this problem, but i think i found the fix. It worked for me. I too am running a galaxy nexus on 4.3
if your android device doesn't appear in android device manager, or if you see unknown location despite your device being online and running google play services version 3.2.25 or higher, follow these steps:
1. Open google settings from your device's apps menu.
2. Touch android device manager.
3. Uncheck allow remote factory reset.
4. Go to your device's main settings menu, then touch apps > all > google play services.
5. Touch clear data. Note that this action doesn't remove personal data.
6. Go back to google settings and select allow remote factory reset.
7. Restart your device.
Make sure you follow the directiions exactly or it won't work
Click to expand...
Click to collapse
Has anyone else had the situation where all devices were initially showing up in Android Device Manager, but no longer show up? Mine was working fine for a few days, and then out of nowhere, both my N4 and N10 disappeared from the web, and I'm getting the "No Active Devices" message. I tried the above tip, but it didn't work for me.
nyijedi said:
Has anyone else had the situation where all devices were initially showing up in Android Device Manager, but no longer show up? Mine was working fine for a few days, and then out of nowhere, both my N4 and N10 disappeared from the web, and I'm getting the "No Active Devices" message. I tried the above tip, but it didn't work for me.
Click to expand...
Click to collapse
Both my N4 and N10 originally worked too, not just my N10 shows up. What's more disturbing is my N4 also disappeared from the Play Store on the web and my devices in my Google account dashboard.
mbwelch said:
Both my N4 and N10 originally worked too, not just my N10 shows up. What's more disturbing is my N4 also disappeared from the Play Store on the web and my devices in my Google account dashboard.
Click to expand...
Click to collapse
Very weird. I haven't had either device disappear from the Play Store, but nothing I do will make them show up again in the Device Manager. Oh well. Guess I'm sticking with Cerberus as my anti-theft solution for now.
pandorra said:
doesnt work for me.....
Click to expand...
Click to collapse
worked for me. follow the guide properly
ibnmurad said:
worked for me. follow the guide properly
Click to expand...
Click to collapse
Umm, thanks? I've "followed the guide properly" more than once on two devices, and it doesn't work for me. It also hasn't worked for others as well, according to comments on a few sites that re-posted the guide.
mbwelch said:
Both my N4 and N10 originally worked too, not just my N10 shows up. What's more disturbing is my N4 also disappeared from the Play Store on the web and my devices in my Google account dashboard.
Click to expand...
Click to collapse
Same here, devices were showing fine just yesterday, now suddenly my GNex and Nexus 10 are both gone from the Play Store and ADM. What gives Google.
nyijedi said:
Has anyone else had the situation where all devices were initially showing up in Android Device Manager, but no longer show up? Mine was working fine for a few days, and then out of nowhere, both my N4 and N10 disappeared from the web, and I'm getting the "No Active Devices" message. I tried the above tip, but it didn't work for me.
Click to expand...
Click to collapse
Yes, same with my N4. I'm not rooted. Neither is my phone
I've tried the instructions above 3 times and still it says "No active devices". Booo Google! Boo.
As with the other users, my N4 also no longer appears on the Play Store, so I can't install apps via a desktop browser any more. I guess the Play Store is now relying on Android Device Manager, which it shouldn't because it's clearly buggy as hell.
God forbid I lose my phone at this stage, having uninstalled Seekdroid. :-/
This worked for me:
http://www.svartling.net/2013/08/this-is-how-to-fix-don-have-any-devices.html
Note: You do NOT need to do step 5.
majorcovert said:
Sweet! I'm not the only one with this problem, But I think I found the fix. It worked for me. I too am running a Galaxy Nexus on 4.3
If your Android device doesn't appear in Android Device Manager, or if you see Unknown location despite your device being online and running Google Play services version 3.2.25 or higher, follow these steps:
1. Open Google Settings from your device's apps menu.
2. Touch Android Device Manager.
3. Uncheck Allow remote factory reset.
4. Go to your device's main Settings menu, then touch Apps > All > Google Play services.
5. Touch Clear Data. Note that this action doesn't remove personal data.
6. Go back to Google Settings and select Allow remote factory reset.
7. Restart your device.
Make sure you follow the directiions exactly or it won't work
Click to expand...
Click to collapse
worked for me thanks
This might be a given but... Do you guys that are having issues have location services activated in Google Settings and also in your phone settings? I've noticed on more than one 4.3 ROM this gets shut off for some reason.. Also you need to accept the agreement to turn location services on. Just something to check.
CJSnet said:
This worked for me:
http://www.svartling.net/2013/08/this-is-how-to-fix-don-have-any-devices.html
Note: You do NOT need to do step 5.
Click to expand...
Click to collapse
jaizero said:
This might be a given but... Do you guys that are having issues have location services activated in Google Settings and also in your phone settings? I've noticed on more than one 4.3 ROM this gets shut off for some reason.. Also you need to accept the agreement to turn location services on. Just something to check.
Click to expand...
Click to collapse
Woohoo! I got my N4 working! The original steps alone DID NOT work for me. I tried them multiple times. However, a combination of adding the steps of disabling all location services and re-enabling them, as well as clearing data for Google Services Framework and Google Play Store (in addition to clearing data for Google Play Services and performing the other suggested steps) did the trick. I did a bunch of rebooting after most of these steps, but I don't remember exactly when (sorry). I did not have to remove/add my Google account.
I still have to get my N10 to be detected. I'll do this when I get a chance, and I'll pay closer attention to which steps fixed the issue.
Does the force stopping, clear data, roboot for Google Services Framework and then system update sequence still to force an OTA on a stock N7?
It used to show a 1969 date before clicking the check now button but now shows the current date each time I have tried.
Edited - I forgot that if you do a system update before rebooting it shows 1969 before clicking check now.
The question still applies, does our has this method worked for anyone recently.
Sent from my Nexus 7
That method has never worked.
If your device isn't already on the list of devices in the roll out you won't get it.
All it did was force your device to check if it was already on the roll out.
That's it and nothing more.
Funny. It worked for me when upgrading to 4.3 on my original N7. Haven't gotten it work the new one.
Sent from my Nexus 7 using Tapatalk 4
I don't recall it ever working for me as far back as 4.1.2 on the N7 2012.