Related
Hi all,
After searching for answers to this issue not only in this forum but elsewhere on the web, and failing to find any reference to it, I decided to create this thread.
I have a non-rooted Nexus 7 (2012), which received an OTA update to Android 4.3 some three weeks ago. I have successfully completed the updated, after which my device's build number became JWR66V. So far, so good. :good:
But, days later, my device displayed a new notification that a "System update [was] downloaded". I thought it could be a new, different update addressing bugs, so I "touch[ed] to install". Again, everything went smoothly. I checked however the build number and it was still JWR66V.
Days later, new notification: "System update downloaded". I installed it to get rid of the notification.
And again and again for the fifth time now. It usually happens after I reboot.
I wonder whether anyone is experience similar issue - and whether this is an issue at all.
Any help or information is highly appreciated.
Thanks!
Is your kernel 3.1.10-g1e8b3d8? Maybe there is some sort of mismatch.
Groid said:
Is your kernel 3.1.10-g1e8b3d8? Maybe there is some sort of mismatch.
Click to expand...
Click to collapse
Thanks for the reply, Groid, but this doesn't seem to be the issue.
As you can see from the two screenshots attached - one taken before I 'updated' (note the "System updated downloaded" icon on the top left corner) and the second after the 'update' - there is no difference between kernel and build number versions. In fact, I believe nothing happens whenever I 'touch to update' (i.e. install the 'new' update)...
I find this strange, even more so as I haven't read about other persons experiencing the same... it does not cause me trouble, but it's annoying and curious, therefore, any feedback is still welcomed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try flashing a stock image of the latest 4.3
digitano said:
Thanks for the reply, Groid, but this doesn't seem to be the issue.
As you can see from the two screenshots attached - one taken before I 'updated' (note the "System updated downloaded" icon on the top left corner) and the second after the 'update' - there is no difference between kernel and build number versions. In fact, I believe nothing happens whenever I 'touch to update' (i.e. install the 'new' update)...
I find this strange, even more so as I haven't read about other persons experiencing the same... it does not cause me trouble, but it's annoying and curious, therefore, any feedback is still welcomed.
Click to expand...
Click to collapse
I have the same issue on my Nexus 7 and Nexus 4...no answer found yet.
Schonplayer said:
I have the same issue on my Nexus 7 and Nexus 4...no answer found yet.
Click to expand...
Click to collapse
Having the same problem on my n7, am rooted, but have a question: if I install this update will i lose root? Should i install ota rootkeeper?
I too have just noticed the update icon as of today's date, despite having successfully updated my tablet at the beginning of the month.
Unlike the OP my tablet was rooted and unlocked so I had to use the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2390286
The update was successful and has been running perfectly.
fangthorn said:
I too have just noticed the update icon as of today's date, despite having successfully updated my tablet at the beginning of the month.
Unlike the OP my tablet was rooted and unlocked so I had to use the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2390286
The update was successful and has been running perfectly.
Click to expand...
Click to collapse
I'm having the problem on my N7 as well. Haven't found a solution yet. I'm gonna try searching more
maybe just re-flash it with 4.3 rom (using pc), and it should be ok
Sorry to hear you guys are experiencing same issue, but at least I'm not alone.
I'm still facing same issue. The New update icon shows up whenever I restart my n7. And it has successfully updated all the times. It's more annoying than anything, but, still, shouldn't be happening.
Sent from my Nexus 7 using xda app-developers app
did you originally install 4.3 from the OTA?
i went from 4.2.2 to 4.3 via fastboot, and then received this update via OTA. and this hasn't happened to me. (yet, but hopefully not at all)
To remove the notification, long press the message in the notification dropdown, press the app info popup, and uncheck the show notifications box. This worked for me.
Sent from my ADR6425LVW using xda app-developers app
Installed
I installed it, nothing changed and i kept root.
That's because the latest 4.3 build is JWR66Y (the screenshots show JWR66V) which is a small update incorporating some critical security fixes. So that's probably why it's still prompting for an update.
Sent from my GT-N5110 using Tapatalk 4
Just installed 4.3 update on the wife's N7 again and noticed there is no sound with media.
Notification and alarm sounds work as does media with headphones. Just no speaker with media.
Please see this thread: http://forum.xda-developers.com/showthread.php?t=2413535&page=10
I've got the same problem and that's how I got rid of it. Essentially, for one reason or another, the new update V->Y build fails.
Long story short, I received a new 2nd Gen 7 yesterday, it was built on 07/13 and its running JWR66N. I found that odd, but figured I would update the build but I haven't been able to. I check for an update and it is telling me by device is up to date. I know this is not true as there are newer builds out there and now KitKit is rolling out. Is there a chance that I will not be able to updated the 7 until KitKat is rolled out to me?
Curious if my device is bad, or if there are no updates actually available to me at this time.
Thanks!
Is it an LTE or a Wifi-Only model? Go to settings >apps> >all> Google Services Framework. Force stop and clear data, then try to check for updates again. Repeat this process a few times for good measure and see if you get anything. If still no updates, get the factory image from here https://developers.google.com/android/nexus/images (JSS15R for the WiFi version) and flash it with fastboot to get yourself ready for the kitkat update to roll out. Don't flash any images unless you know for sure what kind you have and know what you are doing.
Have you tried to manually update your device with the latest 4.3 image posted on Google's development site? I haven't done it myself but they have instructions there that should help you do it. Make sure you download the right image for your particular device.
https://developers.google.com/android/nexus/images
Paten said:
Have you tried to manually update dur device with the latest 4.3 image posted on Google's development site? I haven't done it myself but they have instructions there that should help you do it. Make sure you download the right image for your particular device.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks for the help, unfortunately I am not quite tech savvy enough to take these steps... I have cleared the data with no luck and hard reset a few times with no luck. Am I stuck with having to return yet another tablet?
vulcaninvt said:
Thanks for the help, unfortunately I am not quite tech savvy enough to take these steps... I have cleared the data with no luck and hard reset a few times with no luck. Am I stuck with having to return yet another tablet?
Click to expand...
Click to collapse
Unfortunately I think you may be stuck if you can't update manually. I had the same problem I had to update from about 3 versions back. It may just be best to take it back and hope for a new one.
PS From what I under stand this was a very old build on the nexus 7 that showed up on the first batch of tablets produced, this would explain why the default wallpaper is different.
Found that out from this link: http://forum.xda-developers.com/showthread.php?t=2416793
That is strange, since JWR66 is a 2012 Nexus 7 rom. You are sure it is a 2013 model? It is all black, not gray-ish?
GSLEON3 said:
That is strange, since JWR66 is a 2012 Nexus 7 rom. You are sure it is a 2013 model? It is all black, not gray-ish?
Click to expand...
Click to collapse
It's all black, 2gb Ram. It's definitely 2nd gen, it's pretty jacked... getting more errors when trying to reset. Unfortunately after having five faulty 7s I am moving on. I really wanted to stick it out, but I have lost trust in the device.
vulcaninvt said:
It's all black, 2gb Ram. It's definitely 2nd gen, it's pretty jacked... getting more errors when trying to reset. Unfortunately after having five faulty 7s I am moving on. I really wanted to stick it out, but I have lost trust in the device.
Click to expand...
Click to collapse
Contact google and tell them your problem, they usually help really fast like when my friends nexus 4 came with a off build number.
---------- Post added at 09:29 PM ---------- Previous post was at 09:12 PM ----------
vulcaninvt said:
It's all black, 2gb Ram. It's definitely 2nd gen, it's pretty jacked... getting more errors when trying to reset. Unfortunately after having five faulty 7s I am moving on. I really wanted to stick it out, but I have lost trust in the device.
Click to expand...
Click to collapse
Contact google and tell them your problem, they usually help really fast like when my friends nexus 4 came with a off build number.
GSLEON3 said:
That is strange, since JWR66 is a 2012 Nexus 7 rom. You are sure it is a 2013 model? It is all black, not gray-ish?
Click to expand...
Click to collapse
The first OS they had on the original 2013 nexus7 shipments were JWR66N.
I'm getting this on my N7 2013LTE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My nexus 7 32GB came with the same firmware JWR66N, but there is an easier way to flash the latest 4.3 or 4.4 if you wish to
First of all download the right firmware from google, somebody already posted a link.
Next you need Nexus rootkit 1.7.6
http://www.wugfresh.com/
When you first run rootkit 2 boxes will pop up, just cancel these you can root ect later if you wish.
Then what you need to do is pretty simple
in your nexus 7 enable dev option, then put it into debug mode
then in storage option "top right" select camera PTP
Connect your nexus 7, if ADB or whatever is called isn't working, then there is an option in rootkit to install the universal drivers, you need to do this before you can flash it found in the initial setup option at the top just follow the guide, once that installed it will test and if everything is then working your good to go.
Next you need to unlock it first click the option saying unlock, this will wipe your nexus 7.
Once that done, next you need to click Flash stock+Unroot
Then click other browse
bit futher down click the option called I downloaded a Factory image myself, then click ok, and goto were you downloaded the firmware to.
click on firmware, it do some checks to make sure the MD5 is ok then it extract it from then on it begin to flash to the new firmware for you.
Once that done you can relock your nexus 7 by clicking OEM lock if you wish to.
and job a good un new firmware installed :good:
Hi guys
I upgraded to stock Kit Kat today from stock 4.4. I used WugFresh's Nexus root toolkit to flash the factory image to my device as I had a bootloop on my first flash and I was too lazy to troubleshoot it
Anyway, after setting everything up I realized that Google search was not giving me the option of turning on Google Now for some reason.
I searched online and found one post: https://productforums.google.com/forum/#!msg/nexus/_kIWjcSg2vo/GM2mNVhl55IJ
It seems like the new Google Search app isn't allowing me to "opt in" on Google Now. I am in Iceland so that may be an issue, although it wasn't before...
What I did was revert back to 4.3, set up all as normal, turned on Google Now and then dirty flashed a stock(ish) 4.4 build with CWM. That worked, I've still got Google Now, but I'm wondering if anybody has the same issue and if there is a better solution. If I would like to wipe all and then flash a build I would be unable to use Google Now.
Did you update google search ?
Sent from my Nexus 4 using xda app-developers app
captor34 said:
Did you update google search ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes, and tried uninstalling all updates.
The only thing that has worked is going back to 4.3 (older Google Search app) and turning on Google Now, then dirty flashing 4.4 on top of that.
Seems like the Google Search app after 3.XX does not allow Google Now in Iceland, which is a strange move to say the least...
bjornvil said:
Yes, and tried uninstalling all updates.
The only thing that has worked is going back to 4.3 (older Google Search app) and turning on Google Now, then dirty flashing 4.4 on top of that.
Seems like the Google Search app after 3.XX does not allow Google Now in Iceland, which is a strange move to say the least...
Click to expand...
Click to collapse
On KitKat, long press homescreen, settings, enable google now :laugh:
Same problem for me, google now was working fine on 4.3, and now I can't activate it in 4.4.
i'm in Tunisia.
pike2hc said:
On KitKat, long press homescreen, settings, enable google now :laugh:
Click to expand...
Click to collapse
There is no option
Nexus 7, wiped and reset with 4.4 factory image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nexus 4, dirty flash 4.4 image over 4.3, Google Now already enabled on 4.3
I have this same problem on my nexus 7. I am in Scotland and didn't get any 4.4 OTA, so I sideloaded 16S over 4.3 and got google services error. I've also tried to flash the factory new 4.4 image and got the same problem.
I finally gave up on 4.4... I'll just wait for the official OTA. I'm to scared to try the same process on the Nexus 4 and end up in the same place.
Ah google, why do you have such a bad OTA roll-out system... takes too long
Thanks guys! It's good to see that I'm not the only one affected.
Is there a way to notify Google/Android team about this and hopefully get this fixed asap?
bjornvil said:
Thanks guys! It's good to see that I'm not the only one affected.
Is there a way to notify Google/Android team about this and hopefully get this fixed asap?
Click to expand...
Click to collapse
We can send feedback through the app itself and post it on the support forum
http://productforums.google.com/forum/#!categories/websearch/mobile-search
EDIT: Posted now https://productforums.google.com/forum/#!topic/nexus/MvbqgfzgFJ4
Some "mee too"s might help.
EDIT2: Changed URL since my post got moved to Nexus forum
Google Now (FIXED)
Hi everyone,
I had this problem too and there was only one way I could fix it.
Install Google Search v2.6 and update it later if you want.
Cheers.
bjornvil said:
Hi guys
I upgraded to stock Kit Kat today from stock 4.4. I used WugFresh's Nexus root toolkit to flash the factory image to my device as I had a bootloop on my first flash and I was too lazy to troubleshoot it
Anyway, after setting everything up I realized that Google search was not giving me the option of turning on Google Now for some reason.
I searched online and found one post: https://productforums.google.com/forum/#!msg/nexus/_kIWjcSg2vo/GM2mNVhl55IJ
It seems like the new Google Search app isn't allowing me to "opt in" on Google Now. I am in Iceland so that may be an issue, although it wasn't before...
What I did was revert back to 4.3, set up all as normal, turned on Google Now and then dirty flashed a stock(ish) 4.4 build with CWM. That worked, I've still got Google Now, but I'm wondering if anybody has the same issue and if there is a better solution. If I would like to wipe all and then flash a build I would be unable to use Google Now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=48666862#post48666862 Workinggggg
I just saw on the EVGA forum that 4.4.2 is live, and I'm currently waiting for it to download and install... SQUEEE!!
I see I'm not the first to notice this, hehe... didn't see everyone else's posts buried in other threads... oh well, it's such a momentous occasion that it deserved its own thread
No OTA Notification??
I haven't got anything, that sucks. I unrooted just to get it.
is anyone able to pull the update before rebooting?
Edit: i just found this on the EVGA forums from an employee.
"Important Update:
The new Tegra Note 7 OTA is being temporarily halted due to a bug found while upgrading from 4.2. We expect it to be resolved shortly. "
jon7701 said:
is anyone able to pull the update before rebooting?
Edit: i just found this on the EVGA forums from an employee.
"Important Update:
The new Tegra Note 7 OTA is being temporarily halted due to a bug found while upgrading from 4.2. We expect it to be resolved shortly. "
Click to expand...
Click to collapse
I have the ota pulled and am working on updating the super tool.
also you can get any of my new files from HERE
Rootjunkysdl.com
Tomsgt said:
I have the ota pulled and am working on updating the super tool.
also you can get any of my new files from HERE
Rootjunkysdl.com
Click to expand...
Click to collapse
Soo, how do we flash this? Put it in internal sd card and flash??
You need to have stock recovery installed and it needs to prompt you to update. Or go to about tablet and check for updates
sent from my Galaxy Note 3 running HyperDrive.
Tomsgt said:
I have the ota pulled and am working on updating the super tool.
also you can get any of my new files from HERE
Rootjunkysdl.com
Click to expand...
Click to collapse
Was there no bootloader update?
Have to look at that. But doesn't look like it according to the ota.
sent from my Galaxy Note 3 running HyperDrive.
Tomsgt said:
You need to have stock recovery installed and it needs to prompt you to update. Or go to about tablet and check for updates
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
Aw, so I can't copy it directly and flash it?
Nope stock recovery doesn't have a interface to work with. So that is no way to flash it even in stock. Must be prompted.
sent from my Galaxy Note 3 running HyperDrive.
Tomsgt said:
Nope stock recovery doesn't have a interface to work with. So that is no way to flash it even in stock. Must be prompted.
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
So what do I do exactly to make it prompt me?
You can wait another hour or so and I will have the super restore tool up and running and you can flash kitkat with it.
sent from my Galaxy Note 3 running HyperDrive.
Tomsgt said:
You can wait another hour or so and I will have the super restore tool up and running and you can flash kitkat with it.
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
Awww, okay lol I'll wait. Thanks for clearing it up for me. :3
UPDATE recovery does have a interface, I got to the android with a "!" point and did power+volume up and it took me to the menu lol
Yeah I just got mine into recovery also lol
sent from my Galaxy Note 3 running HyperDrive.
Tomsgt said:
Yeah I just got mine into recovery also lol
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
Huh? E: signature verification failed Installation aborted
[/COLOR]
Tomsgt said:
Yeah I just got mine into recovery also lol
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
You may have altered yours.... the one I
downloaded this morning and the file called
"tegra_note_7_-_ota2_android_4.4.2_update__4.4.2.zip" and is bigger then yours, It also contains blob,boot.img and file_contexts
Great job on version 2 of the super tool :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't believe it! Bravo Nvidia!
A very good news, indeed.
FYI, after update and initial reboot, my device was extremely unresponsive. Rebooted it a second time and it was fine. Perhaps this is the bug they are talking about...
So here is the link to the 4.4.4 file. Interesting......
If you install this let us know what you find new...prob just a quick bug fix I would imagine.
https://developers.google.com/android/nexus/images
Update:
Nexus 5 Software Update - KTU84P
Enhancements/Fixes
Security Fix
Important Notes
- Software version is KTU84P
- This update will be rolled out to device in batches.
- Refer to the Nexus 5 Software Update article in Support for install instructions
I just saw it . GOOGLE WHAT ARE YA DOIN.... haha was just about to create this thread.
Me right now. The third guy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seriously, Google. ... what's with the LTE hate?
This is probably plugging the towelroot exploit .
Sent from my Nexus 7 using xda premium
I hate that feeling when you JUST finish updating your Nexus 5 phone to Android 4.4.3 and literally two minutes later an update to 4.4.4 gets released! UGH! Still waiting for LTE for Nexus 7.
What in the world Google... Something musta been a big time fail in the code for them to release a full update like this that quick...
Sent from my Nexus 7 using Tapatalk
cokey77 said:
This is probably plugging the towelroot exploit .
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
nope, it's related to the heart bleed
Sent from my Nexus 7 using Tapatalk
Soldier 2.0 said:
nope, it's related to the heart bleed
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Nope, it is SSL related, but not heartbleed.
Well people, the OTA doesn't look like it affected very much. I usually just flash whatever image from the factory image that I need because of the changes I make in the system but I just now decided for grins to flash the OTA and see if I would get any errors and I was pleasantly surprised to not see the "unexpected contents error." It happens, rarely, but it does happen. Running ElementalX kernel, busybox installed, modified calculator app in system/app, 4.4 sounds in system/media/audio/ui, modified mixer_paths.xml in system/etc, Z2 bionic and dalvik, running xposed and the OTA flashed with no errors! Woop Woop! Did have to flash the supersu zip in recovery. All good!
changes on 4.4.4 http://www.xda-developers.com/android/heres-everything-thats-changed-in-android-4-4-4-ktu84p/
Whats wrong with you GOOGLE ? Why just Razorg ?
What is wrong with Google? Why is Deb being left out?
Sheesh... Feeling abandoned...
I don't understand why Deb is being left out either. Maybe we'll just jump into the new android version when it's announced at Google I/O.
Maverick-DBZ- said:
I don't understand why Deb is being left out either. Maybe we'll just jump into the new android version when it's announced at Google I/O.
Click to expand...
Click to collapse
Somehow I don't expect that'll be what happens.
Considering there had to be a 4.4.2_r2 for deb before, I suspect that whatever inspired that (which was Verizon compatibility) is the holdup now.
Does anyone have the OTA URL?
lotherius said:
Me right now. The third guy.
Seriously, Google. ... what's with the LTE hate?
Click to expand...
Click to collapse
My guess it's because of Verizon
I hope they've included the driver for the Logitech Unifying receiver...
Can some one grab the OTA file name, URL, or the OTA itself and upload it?
lotherius said:
Somehow I don't expect that'll be what happens.
Considering there had to be a 4.4.2_r2 for deb before, I suspect that whatever inspired that (which was Verizon compatibility) is the holdup now.
Click to expand...
Click to collapse
Well, 4.4.4 does put us 2 releases behind now.
I can imagine a *good* developer working out a DRY unified patch (verizon & others) for 4.4.3 and 4.4.4. But, along comes management and says either (a) verizon does not accept, or (b) others like att/t-mobile/etc do not accept. A drama ensues and we have big delays.
Anyway, "4.4.2 really?" is the perfect question to *pound* on google during IO. lol
There's a theory going around that it's Verizon that is to blame for the delay, but maybe it's not the reason