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.
Related
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.
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!
So I just picked up a sprint galaxy nexus and so far I like it...Kinda wondering why i keep getting a notification that chrome has a update but it fails to install. I have tried clearing the data for the market and chrome app. I have even did a ODIN restor back to stock to try to backup my google wallet so I could use it even tho I was rooted. (unsucessful). Anyone have anyone else seen this?
Have you changed your display density?
martonikaj said:
Have you changed your display density?
Click to expand...
Click to collapse
this.
and did you try uninstall/reinstall chrome?
No I have not changed the density. And it won't let me uninstall it came preinstalled. Force stop and disable are the only options available for it
Sent from my Galaxy Nexus using xda app-developers app
Anyone have any other ideas? I had this issue by the time I got home with the phone before I even had a chance to mess with it lol. I left and it started the JB update after that some apps updated but chrome failed. I played around a bit and ignored it..But then after doing rooting and unlocked boot loader it tried doing the update again and failed. Then I was messing around with google wallet and relized I needed to setup pre-root and odin'd back to stock and again after that the chrome update failed...still not sure which browser going to use as primary but it seems very weird. other than Root/boot loader and nova launcher I have not done anything to the phone.
why do you keep using odin?
use fastboot, it's the officially supported tool, even Google uses and has tutorials on it.
if you have CWM installed, then the official update will NOT work when started from android os.
that said, if you have root access, you can just remount /system to rw and uninstall/delete chrome apk from /system/app.
sent from my i9250
bk201doesntexist said:
why do you keep using odin?
use fastboot, it's the officially supported tool, even Google uses and has tutorials on it.
if you have CWM installed, then the official update will NOT work when started from android os.
that said, if you have root access, you can just remount /system to rw and uninstall/delete chrome apk from /system/app.
sent from my i9250
Click to expand...
Click to collapse
I did try fastboot's restore the first time but it just went to the dead (or whatever) android guy so I looked on the forums and saw a thread with a sticky about removing root/going back to stock so just did that and it showed odin. Thanks for the suggestion I will give it a try later when I have a few spare mins to play.
Avaliable from today? Now i installing new update
Odoslané z LT30p pomocou Tapatalku
Yes, it seems to work very well. Re-rooted with Nexus Root Toolkit v1.8.3. Just had to re-enable usb debigging first. The toolkit even updated itself with KTU84L binary (4.4.3 for Nexus2013).
I just updated mine, nothing different though, I guess its only bugs fix
Nam Huy Linux http://namhuy.net
Hi guys, so I got the notification about the update, but I forgot I had to have the stock recovery to install it, and I pressed the install update, it locked my bootloader, but didn't update to 4.4.3, now if I go to system update, press check for updates, it say I'm on latest update. What should I do now?
Szighy said:
Hi guys, so I got the notification about the update, but I forgot I had to have the stock recovery to install it, and I pressed the install update, it locked my bootloader, but didn't update to 4.4.3, now if I go to system update, press check for updates, it say I'm on latest update. What should I do now?
Click to expand...
Click to collapse
Boot into twrp, and flash it manually, you'll find the ota zip in /cache.
Unless you are serious/correct about it locking your bootloader, which I never heard of an update doing, then you got a different issue.
I did the same thing, but there's no update in that folder
Sent from my Nexus 7 using XDA Free mobile app
one got it, not the other
I've two Nexus 7 2013 units. One got the update message (and it worked) but the other has not. Tried checking for updates on it and it says it's up to date (running 4.4.2). No biggie, just curious that one got it but not the other.
Still haven't rooted either of them yet.
wkearney99 said:
I've two Nexus 7 2013 units. One got the update message (and it worked) but the other has not. Tried checking for updates on it and it says it's up to date (running 4.4.2). No biggie, just curious that one got it but not the other.
Still haven't rooted either of them yet.
Click to expand...
Click to collapse
Nothing to be curious about, it's just the way they roll it out.
Go to all applications and clear cache for google services framework. Then recheck for update..
mulperi said:
Go to all applications and clear cache for google services framework. Then recheck for update..
Click to expand...
Click to collapse
Not trying to start that debate again, but anyone considering doing this should at least be aware of this article before doing it: Don't clear data for Google Services Framework
phazerorg said:
Not trying to start that debate again, but anyone considering doing this should at least be aware of this article before doing it: Don't clear data for Google Services Framework
Click to expand...
Click to collapse
Yep. Agreed, it's much safer to just side load it.
Sent from my 831C using Tapatalk
phazerorg said:
Not trying to start that debate again, but anyone considering doing this should at least be aware of this article before doing it: Don't clear data for Google Services Framework
Click to expand...
Click to collapse
Agreed, blanket dumping of data certainly has it's place. I wasn't sure this was one of them. That and I'm honestly ot in any kind of rush to force updates. Still, it's been a few days and the one tablet is still not showing 4.4.3 as available yet. Both are logged into the same google account. No rush, my to-do list has PLENTY of other things on it...
so its october 12th, and i still dont have the september update, let alone the october update.
magisk/twrp installed
opted into the beta and back out to try to refresh some kind of hidden cache or something, no luck
going to manually install via pc, but id like to know potential reasons this would happen and how to resolve it so i can do the november one using the magisk method from their github
system update says up to date with august 5th patch installed
EDIT: please move to pixel 2 forum (although same info still applies)
If you are rooted you can't receive OTA, you must sideload it.
Did you sign up for the Android Pie beta testing programme? I was still signed up on my Pixel 2 XL and wasn't getting the update too until I left the programme.
The same happened to my friend's 2xl. I ended up sideloading the ota for him however one of my relatives was complaining as well. No ota notification popped up for her. No root, no custom recovery, full stock. She factory reset the phone and the update notification immediately popped up at the first boot. In the past it worked and triggered the ota update if you force stopped Google services framework and cleared cache and data. I don't know it it works now. Anyway, sideload the update and hopefully next month it will work again or try a factory reset if your device is stock with no root.
dj_ooms said:
Did you sign up for the Android Pie beta testing programme? I was still signed up on my Pixel 2 XL and wasn't getting the update too until I left the programme.
Click to expand...
Click to collapse
I was not in the beta program. I did sign up yesterday and immediately leave it, thinking maybe that would force some kind of hidden cache to be cleared. No luck.
siggey said:
If you are rooted you can't receive OTA, you must sideload it.
Click to expand...
Click to collapse
This is not true. I've always gotten the notifications until these past 2 months. There is now a way to get the ota without side loading, and it worked on our other one, I just wasn't getting the notifications on mine.
I was in the pie beta program and once the official release came out I got the monthly update in September. However, I still haven't gotten the October one which is weird. Guess I shouldn't really care since I have the 3 coming soon anyway.
Ive always had the notification of the update when rooted on this phone.