Just receive message of OTA. It is a small update and file size is 3.4MB. Since I have flashed the latest TWRP that support the OTA update.
I can not see any different version change.
taitony said:
Just receive message of OTA. It is a small update and file size is 3.4MB. Since I have flashed the latest TWRP that support the OTA update.
I can not see any different version change.
Click to expand...
Click to collapse
i just recieved it myself on my Android 4.4, it says "fixes bugs" which i haven't felt there was, but i guess it's not everyone that finds the bugs they fix, and maybe the performance will go up a little more, i will bench a little later, depending on how much i have to do at work
Yeah it's mostly under the hood bug fixes. There's no change log but one new 'feature' they found is that it will remind you to set up a backup account if you have multiple Google accounts on the device.
Sent from my Nexus 7 using XDA Premium 4 mobile app
puma99dk| said:
i just recieved it myself on my Android 4.4, it says "fixes bugs" which i haven't felt there was, but i guess it's not everyone that finds the bugs they fix, and maybe the performance will go up a little more, i will bench a little later, depending on how much i have to do at work
Click to expand...
Click to collapse
Great to see your investgation what will be updated. But my Nexus 4 has no such update, so it is not for all KitKat devices.
Yeah I checked if it was also up for Nexus 4, sadly its just the N7 up for grabs, Just got the OTA notification, 3MB file.
Also there's this, new build, KRT16S
Sorry is this a jelly bean update or kit kat?
Sent from my SM-N9005 using XDA Premium HD app
protoism said:
Sorry is this a jelly bean update or kit kat?
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
we talk about "Kitty kat"
but so far Benchmarks haven't improved to me, but it don't get as hot as with JB rom around the cam when it's in use so that's fine with me
puma99dk| said:
we talk about "Kitty kat"
but so far Benchmarks haven't improved to me, but it don't get as hot as with JB rom around the cam when it's in use so that's fine with me
Click to expand...
Click to collapse
Maybe I have missed something, but are people receiving a small kitty kat bug fix OTA, even though 4.4 has not actually gone out over the air, but is just being sideloaded?
Sent from my SM-N9005 using XDA Premium HD app
protoism said:
Maybe I have missed something, but are people receiving a small kitty kat bug fix OTA, even though 4.4 has not actually gone out over the air, but is just being sideloaded?
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
i read some has gotten OTA but not everyone, i used adb yesterday at work to "sideload" 4.4 on to my Nexus 7 2013 16gb tablet and it just is nice running smooth, no heat around my cam anymore in use.
i normally game a little and use it for Teamviewer. I brought my tablet bcs i was tired of dragging a laptop with me around, bcs i drag it to work everyday.
I basicly when at family, or friends house use my tablet for surfing, teamviewer and all what i used the laptop for it's nice
puma99dk| said:
i read some has gotten OTA but not everyone, i used adb yesterday at work to "sideload" 4.4 on to my Nexus 7 2013 16gb tablet and it just is nice running smooth, no heat around my cam anymore in use.
i normally game a little and use it for Teamviewer. I brought my tablet bcs i was tired of dragging a laptop with me around, bcs i drag it to work everyday.
I basicly when at family, or friends house use my tablet for surfing, teamviewer and all what i used the laptop for it's nice
Click to expand...
Click to collapse
Nice, just in this forum only one person claims to have received 4.4 OTA. It does seem they are sending out a patch for something that is only available as a factory image that is being sideloaded. Curious.
Sent from my SM-N9005 using XDA Premium HD app
protoism said:
Nice, just in this forum only one person claims to have received 4.4 OTA. It does seem they are sending out a patch for something that is only available as a factory image that is being sideloaded. Curious.
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
the factory image and the one that comes on OTA should be the same as far as i know.
but it was pretty easy to flash my tablet, it took a little bcs i had a problem but when i fixed that one it went smoothly and no issues at all.
anyone else's touchscreen get ridiculous after this small OTA? I never had issues, then we got that jellybean OTA to "fix" touch screen issues for certain people, which then proceeded to break my touch screen. then I got kitkat, and it's perfect again, no touch issues anymore.. now I got this OTA and this morning I had to press everything 5 times before it registered! I did a reboot and it went away, but seriously, if they broke touch again, I'm giving up on this tablet.
Sent from my Verizon LG G2 using Tapatalk Pro
Where is the update located once it is downloaded, I'm trying to install it with TWRP.
Just got it via OTA (had side loaded KitKat before that). Made me lose root but that should be easily fixed.
I had side loaded 4.4, unlocked and rooted. I got the OTA notification and there was an error installing and now I'm stuck in a bootloop. When it comes up it has dead android with red exclamation point and says "No command."
embhorn said:
I had side loaded 4.4, unlocked and rooted. I got the OTA notification and there was an error installing and now I'm stuck in a bootloop. When it comes up it has dead android with red exclamation point and says "No command."
Click to expand...
Click to collapse
Same thing happened to me. I got the OTA notification but stoopidly I had SuperSU in OTA survival mode. The update failed and I ended up at the 'No Command' recovery thing you are talking about.
I was able to fix it by manually flashing the /boot, /recovery, and /system partitions (NOT /userdata ) in fastboot using the KRT16S system image that can be found here (https://developers.google.com/android/nexus/images#razorkrt16s). Everything was okay after that - all of my user data was intact and I was updated to KRT16S :good:
paddycr said:
Same thing happened to me. I got the OTA notification but stoopidly I had SuperSU in OTA survival mode. The update failed and I ended up at the 'No Command' recovery thing you are talking about.
I was able to fix it by manually flashing the /boot, /recovery, and /system partitions (NOT /userdata ) in fastboot using the KRT16S system image that can be found here (https://developers.google.com/android/nexus/images#razorkrt16s). Everything was okay after that - all of my user data was intact and I was updated to KRT16S :good:
Click to expand...
Click to collapse
Ah well. I win the noob award. I panicked and re-flashed stock. But my saving grace is that I have a backup from not too long ago.
airmaxx23 said:
Where is the update located once it is downloaded, I'm trying to install it with TWRP.
Click to expand...
Click to collapse
I was on stock, unlocked, rooted with TWRP. I ran the KRT16S OTA normally. TWRP installed it. I lost root and TWRP. Easy enough fix.
Sent from my Nexus 7 using Tapatalk 4
Lost root, tried reflashing the SU 1.43 binary in TWRP and still don't have root. Any advice?
nchopp said:
Lost root, tried reflashing the SU 1.43 binary in TWRP and still don't have root. Any advice?
Click to expand...
Click to collapse
This: http://autoroot.chainfire.eu/
You need to do this in fastboot. The instructions are at the bottom of the page
Related
Basically is this possible, to go from 4.2 to 4.1.2? Mine is fine but my friend's Nexus 7 keeps shutting down.
Will a factory reset restore 4.1.2? Is there another way? Been googling for an hour, & I'm thinking it mustn't be possible with unrooted devices.
Thanks for any help
Mrs Hedgehog
P.S Please don't yell.
Not that I am aware of--I think you'll need to unlock the boot loader to then push the 4.1.2 image to it, but don't worry, its pretty straightforward with a little reading. Check the stickies for guides.
did the move to 4.2 occur via ota update?
Sent from my Nexus 7 using xda app-developers app
kboya said:
Not that I am aware of--I think you'll need to unlock the boot loader to then push the 4.1.2 image to it, but don't worry, its pretty straightforward with a little reading. Check the stickies for guides.
did the move to 4.2 occur via ota update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it was via OTA update. Bottom, she isn't going to want to unlock her device. Is there no way to put it back to how it was when she pulled it out of the box brand new? Even if she loses everything she would prefer that.
P.S Thanks for answering, appreciated.
Maybe she needs to think again. You can relock it as if nothing had happened!
Sent from my Nexus 7 using xda app-developers app
Ok would Google know if she did that. Would it be like it was when she first got it? Say if she had to send it back under the guarantee? I'm shocked actually. I thought a factory reset would take it back to basics. I don't think she'll agree somehow.
Nope, it is like nothing ever happened. No-one shall know (nor care,quite frankly).
Factory reset is more like delete data and settings (and also all your photos etc, if you choose SD card) and return to factory state (I.e. the base OS, which is now 4.2 after the update). It does not roll back to the original OS from the factory, which could be several iterations back.
Sent from my Nexus 7 using xda app-developers app
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Spannaa said:
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Click to expand...
Click to collapse
Think I may just do this. But, will it keep trying to force the update on me?
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
Think I may just do this. But, will it keep trying to force the update on me?
Click to expand...
Click to collapse
It's Google that pushes the updates.
I've had no problems with 4.2 but if I do, I'll roll back to 4.1.2 and wait...
Spannaa said:
It's Google that pushes the updates.
I've had no problems with 4.2 but if I do, I'll roll back to 4.1.2 and wait...
Click to expand...
Click to collapse
So I'd still get the notification to update to 4.2 if I reverted back.
But yeah, 4.2 isn't that bad. I do notice some unresponsiveness when clicking icons but other than that, pretty good.
Sent from my SCH-I535 using xda app-developers app
Install the FOTAKill app to stop OTA Notifications
tu3218 said:
Think I may just do this. But, will it keep trying to force the update on me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I had to roll back to 4.1.2 on my Nexus 7. The tablet would not charge (didn't recognize the high-current charger) under 4.2. To stop the update notifications I installed FOTAKill (tablet must be rooted). .doc file with FOTAKill installation instructions is attached.
Really wish that Google would have an option for "Never" when it asks for permission to install an update.
Spannaa said:
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Click to expand...
Click to collapse
Hi, I have a question, If I flash back to stock with Wug's toolkit would I receive the 4.1.2 update OTA or would I have to flash it manually?
Sent from my Nexus 7 using XDA Premium HD app
Cee_Pee_Three said:
Hi, I have a question, If I flash back to stock with Wug's toolkit would I receive the 4.1.2 update OTA or would I have to flash it manually?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
If "stock" is before 4.1.2 then yes, you'd get the OTA update notification (which would unroot the tablet. You might as well manually flash 4.1.2.
My Nexus 7 "bricked" when I allowed the update from 4.1.2 to 4.2, requiring a complicated procedure to unbrick it. I suspect that the problem was caused by a "rootkeeper" app.
SMS888 said:
If "stock" is before 4.1.2 then yes, you'd get the OTA update notification (which would unroot the tablet. You might as well manually flash 4.1.2.
My Nexus 7 "bricked" when I allowed the update from 4.1.2 to 4.2, requiring a complicated procedure to unbrick it. I suspect that the problem was caused by a "rootkeeper" app.
Click to expand...
Click to collapse
I wrote that wrong, I meant if I'm on 4.2 and flash back to the 4.1 original that first came with the device, would the 4.1.2 update come up OTA or would I have to flash 4.1.2 manually?
Sent from my Nexus 7 using XDA Premium HD app
I think you have to update manually. OTA will offer 4.2.
telexer said:
I think you have to update manually. OTA will offer 4.2.
Click to expand...
Click to collapse
Correct. The FOTA update would offer only the latest version.
On my new Nexus two separate updates were sent in sequence. First an update to 4.1.2 then another update (declined) to 4.2 a few minutes later. It was not a single update from 4.1.1 to 4.2.
Thank u for sharing this info, this saves me the trouble from updating to 4.1.2 manually.
UPDATE: So I went back to the initial ROM the device came with (JB 4.1.1) and Google quickly prompted to update to 4.1.2 (which is what I wanted) and now it asks me to update to 4.2 but I ignore that
Long story short, my Nexus 7 is back up and working flawlessly again!!
Sent from my Nexus 7 using XDA Premium HD app
SMS888 said:
I had to roll back to 4.1.2 on my Nexus 7. The tablet would not charge (didn't recognize the high-current charger) under 4.2. To stop the update notifications I installed FOTAKill (tablet must be rooted). .doc file with FOTAKill installation instructions is attached.
Really wish that Google would have an option for "Never" when it asks for permission to install an update.
Click to expand...
Click to collapse
What if I want to update my Nexus 7 later, how do I take off the fotakill.apk?
Sent from my Nexus 7 using XDA Premium HD app
4.2..> 4.1.2 Without rooting
Have Nexus 7, stock, has been upgraded OTA to 4.2.1. Have an $80 app (Anywhere Map) which company is working on a fix to operate with 4.2. I use Linux and it appears you can upgrade manually with 'adb reboot recovery' then Power & Vol to get recovery menu. Posts have said simply use 'adb sidload upgrade_img.zip' or 'adb install upgrade_img.zip'. Simple enough. I've only gotten to the menu from which I can choose 'apply update from adb', but have done nothing. Posts have said simply issue the command and select reboot from menu after it installs. This should install new os version without removing apps nor sdcard info. (I have backed up the whole sdcard with 'adb pull' to my computer.)
I have 4.1.2, 4.2, and 4.2.1 images. What I would like to do is put the 4.1.2 on to use until Anywhere Map gets their act together for 4.2. But 4.1.2 seems like a minor update to 4.1 and I can't find that image at Google nor anywhere else.
So the question is as to whether updating with the 4.1.2 image will work or not. I have the material to root the machine manually but would prefer not to do it. This all looks rather straightforward from the many posts I've read, except with my reservations on the 4.1.2 update. Thanks for any comments.
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
andyabc said:
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
Click to expand...
Click to collapse
You have to be stock to get the google updates. No custom recovery at all.
zelendel said:
You have to be stock to get the google updates. No custom recovery at all.
Click to expand...
Click to collapse
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
zelendel said:
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
Click to expand...
Click to collapse
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
zelendel said:
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
Click to expand...
Click to collapse
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
To be honest I have no idea as I never do OTA updates. No real point.
zelendel said:
To be honest I have no idea as I never do OTA updates. No real point.
Click to expand...
Click to collapse
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
zelendel said:
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
Click to expand...
Click to collapse
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
zelendel said:
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
Click to expand...
Click to collapse
Awesome, I am just going to flash the stock recovery so when the update is available the data will not get wiped.
Sent from my Nexus 4 using xda app-developers app
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
spaceman860 said:
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
Click to expand...
Click to collapse
So the OTA update would just work?, all well I have the stock recovery flashed at the moment anyway so when the OTA updates stop I will flash the recovery back and then install a custom rom with 4G and USB Host supported also having all the good tweaks like the camera tweak.
Sent from my Nexus 4 using xda app-developers app
I had CWM on my rooted Nexus 4, and the OTA for android 4.3 came along, and worked fine! Android asked to reboot to install the update, so I agreed, and the reboot loaded CWM which flashed the update. I lost root however, but it was easy to put back.
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
sordna said:
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
Click to expand...
Click to collapse
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
pjc123 said:
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
Click to expand...
Click to collapse
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
sordna said:
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
Click to expand...
Click to collapse
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
pjc123 said:
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
Click to expand...
Click to collapse
No need to wait, you can switch back to SuperSU, the latest version (1.51) has been working perfectly with 4.3 for me.
BTW I just installed BootUnlocker for nexus devices, a great app that can lock/unlock your boot loader from within android without wiping your data!
My N10 is rooted but with a stock ROM. Earlier on it said that there was an update (4.3) and it downloaded it, re booted and then came up with an error saying 'no command' while displaying the small pic of the Android. It sat there for 10 mins and then eventually booted back into the OS. When I checked the version, it was back to 4.2.2.
Now when I check for an update, it says that there's no update available.
What do I do?
Sent from my Nexus 10 using Tapatalk 4 Beta
Are you on stock recovery? Barring that, clear Google Framework data and try again maybe?
Sent from my MB855 using xda app-developers app
That message is okay. Nothing is wrong with your tablet, other than the fact that the update didn't take. Do as the above poster said, or manually install the OTA.
Sent from my Nexus 4 using xda premium
Homey said:
My N10 is rooted but with a stock ROM. Earlier on it said that there was an update (4.3) and it downloaded it, re booted and then came up with an error saying 'no command' while displaying the small pic of the Android. It sat there for 10 mins and then eventually booted back into the OS. When I checked the version, it was back to 4.2.2.
Now when I check for an update, it says that there's no update available.
What do I do?
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Why not try to check again for the OTA? No worries dude... That's not an unusual thing to happen . Also you can try doing what the other two said ,)
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Thanks guys. I cleared Google Framework Data and the download started again and failed again. This time, all it said was "error"!
I really don't want to zero the tablet again and lose all my data by doing the update manually. Is there any way to avoid that?
Also is there anything great about 4.3 that makes the update worth doing?
Sent from my Nexus 10 using Tapatalk 4 Beta
Homey said:
Thanks guys. I cleared Google Framework Data and the download started again and failed again. This time, all it said was "error"!
I really don't want to zero the tablet again and lose all my data by doing the update manually. Is there any way to avoid that?
Also is there anything great about 4.3 that makes the update worth doing?
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Its probably because your tablet is rooted. Try unrooting and then doing the update.
bortak said:
Its probably because your tablet is rooted. Try unrooting and then doing the update.
Click to expand...
Click to collapse
Yeah, I thought that was it too so I unrooted and tried again. It's still the same.
I really don't want to do a factory reset and manually update the bloody thing - I'll lose all my stuff!
Called Google support and sent them pictures of the Android screen (they asked for them!) and apparently they're investigating...
Yeah maybe you just need to wait a little more so you won't be like me. I just bricked mine today trying to do a factory reset .
Sent from my SGH-M919 using xda premium
Same problem
I have the same problem. Await Googles response..............
Same problem !!
Homey said:
Yeah, I thought that was it too so I unrooted and tried again. It's still the same.
I really don't want to do a factory reset and manually update the bloody thing - I'll lose all my stuff!
Called Google support and sent them pictures of the Android screen (they asked for them!) and apparently they're investigating...
Click to expand...
Click to collapse
You can manually update without performing a factory reset by just pushing boot and system, although you need to know what can go wrong before you try.
Same issue, rooted and custom recovery.
But if they are investigation, maybe I won't remove the custom recovery, too much work.
I got the 'error' screen too. pressed power and volume and it told me that build.prop failed the file check, pulled an fresh copy out of the old factory image, copied it to my n10 and tried the OTA again. All went ok, now on 4.3
Same error!!
Already did a factory reset and still have the error
Same problem here. Rooted on stock. Keep going to Recovery, then errors when trying to apply the 'untrusted' update, as it states.
Same problem here....rooted with stock recovery, tried three times clearing the data from Google framework but no luck so far...
Sent from my Nexus 10 using xda premium
Same here too
Unlocked boot loader
Rooted
Stock ROM
Stock recovery
Sent from my Nexus 10 using Tapatalk HD
Do you happen to have stickmount installed?
http://forum.xda-developers.com/showthread.php?t=2380620
I have this problem too, now trying to find the original file and try again.
Anyone know where can get that file for nexus 10?
boolim said:
Do you happen to have stickmount installed?
http://forum.xda-developers.com/showthread.php?t=2380620
I have this problem too, now trying to find the original file and try again.
Anyone know where can get that file for nexus 10?
Click to expand...
Click to collapse
I need that too. :crying:
For those with unlocked bootloader who want to update:
https://dl.google.com/dl/android/aosp/mantaray-jwr66v-factory-888d124e.tgz
This is the stock Android 4.3 from Google! If you know how to flash just do it .
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
seriously. is this rollout still rolling? did i screw myself by doing the clear data from framework trick? (i can still download from play store)
on the contrary I have yet to hear a report from anyone that has got the OTA. Everyone seems to be sideloading it. After spending over three hours trying to get my version of ADB to update to one that can sideload (I have even deleted ALL the Ade.exe files and it still runs the old one (which I cant find) ) I have decided to wait... and wait... and wait.
So heres the question. Has ANYONE had the OTA update. Not the sideload, I know we can sideload. Has anyone had pure OTA update?
No OTA here either. I'm stuck with out a computer so I have to wait. It sucks because I know how to flash the factory image but I just can't. I'm not one to complain, but damn this is a slow role out.
Sent from my Nexus 7 using XDA Premium 4 mobile app
kmmxracer said:
No OTA here either. I'm stuck with out a computer so I have to wait. It sucks because I know how to flash the factory image but I just can't. I'm not one to complain, but damn this is a slow role out.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You don't need a computer. Grab the OTA zip from Google's servers and flash in recovery.
Sent from my Nexus 7 using Tapatalk
Well my update is that I am now running KitKat. I never did get the OTA but did find a copy of ADB.exe in the windows directory. One quick addition of a .bak suffix (just in case) and i happily sideloaded it.
Maybe its googles strategy to reduce server load!
im also waiting for my update
People, you are in XDA. Just sideload KitKat.
tatazeuz said:
People, you are in XDA. Just sideload KitKat.
Click to expand...
Click to collapse
I'm probably going to lose my geek card for this, but after I side load what do I do? I'm not rooted, my bootloader is locked, and I don't have my computer so I can't back up. Should I just wait for the OTA so that I don't lose all of the stuff on my tablet?
Sent from my Nexus 7 using xda app-developers app
geekygirl74 said:
I'm probably going to lose my geek card for this, but after I side load what do I do? I'm not rooted, my bootloader is locked, and I don't have my computer so I can't back up. Should I just wait for the OTA so that I don't lose all of the stuff on my tablet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You won't lose anything, side loading is the same as recieving an OTA, only flashing factory images wipe data. Sideloading won't wipe anything.
Hello fellow N10 owners,
Unfortunately, the OTA KitKat update for my N10 is still not available for download.
I have reset the Google Frameworks app, but that did not work.
I am running Android Version 4.3 build JWR66Y stock rooted.
If you guys have any suggestions I would really appreciate it. Also, If you would know
how I could keep root after the update that would be awesome!
Thank you
BosCeltics18 said:
Hello fellow N10 owners,
Unfortunately, the OTA KitKat update for my N10 is still not available for download.
I have reset the Google Frameworks app, but that did not work.
I am running Android Version 4.3 build JWR66Y stock rooted.
If you guys have any suggestions I would really appreciate it. Also, If you would know
how I could keep root after the update that would be awesome!
Thank you
Click to expand...
Click to collapse
Mine is still not showing either......kinda depressing.
oakbowery said:
Mine is still not showing either......kinda depressing.
Click to expand...
Click to collapse
USA?
BosCeltics18 said:
USA?
Click to expand...
Click to collapse
Yes, Mississippi to be exact. I've hit the check now button 1,000 times I think.
oakbowery said:
Yes, Mississippi to be exact. I've hit the check now button 1,000 times I think.
Click to expand...
Click to collapse
hahaha! same
Glad to know I'm not the only one. I was beginning to wonder if my tablet was screwed or something. I have a nexus 7 also and it has yet to get an OTA update either.
I from malaysia and also don't get any update message yet : \
Sent from my Nexus 10 using XDA Premium 4 mobile app
Perhaps Google is waiting for Kitkat to be released on the new Nexus 10 before updatring the original Nexus 10.
There is no new Google 10 and seriously once you get KitKat on your tablet you'll wish you hadn't, the OS is like a giant phone and isn't geared up for tablets.
Sent from my Nexus 10 using Tapatalk 4
BackDaws said:
There is no new Google 10 and seriously once you get KitKat on your tablet you'll wish you hadn't, the OS is like a giant phone and isn't geared up for tablets.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
I disagree. With the exception of the PhoneUI settings screen it's exactly the same thing we had before with much improved performance and reliability. I'm so glad to get rid of 4.3.. Nothing but problems.
Maybe it's been pulled.
Sent from my Nexus 10 using xda app-developers app
Use Adb to sideload the ota zip if you do not want to wait
And I think KitKat is great on the n10, especially with the new launcher installed
Sent from my Nexus 5 using Tapatalk
I'm still waiting too. I'm in London, UK.
Sent from my Nexus 10 using Tapatalk 4
The full image is available on the Nexus factory images site. If you can't wait for the OTA, just download and flash that. Just remember to edit the batch file so you don't wipe everything. Here is the link.
https://developers.google.com/android/nexus/images?csw=1#mantarayjwr66y
Taking advantage of the topic, I'm from Brazil and me has not yet come to update my tablet version is also JWR66Y rooted, I need to get the root to update via OTA? Because I remember the last update to 4.3, when restarted I had problem with the boot image and had to use a tool to change the boot image
I waited, and waited, but gave up a couple nights ago. Seems to me, it should be like a voting system. The more manual update checks you do, the sooner you get it versus those that don't manually check. Those that don't realize the update is even or won't miss it for another few days.
Editing the -w out of the batch file was troublesome for me. The flag would complete and the tablet would reboot, but it would then hang on the nexus boot screen. Tried twice, but waiting a half an hour each time, I deemed it failure. Unexpected too since I had done a full wipe, factory fresh 4.3 the week prior.
Running the unedited batch with wipe went without a hitch. No biggie since I had done it recently.
--OctOS Powered VZW GS4 Dev Edition
Bait-Fish said:
I waited, and waited, but gave up a couple nights ago. Seems to me, it should be like a voting system. The more manual update checks you do, the sooner you get it versus those that don't manually check. Those that don't realize the update is even or won't miss it for another few days.
Editing the -w out of the batch file was troublesome for me. The flag would complete and the tablet would reboot, but it would then hang on the nexus boot screen. Tried twice, but waiting a half an hour each time, I deemed it failure. Unexpected too since I had done a full wipe, factory fresh 4.3 the week prior.
Running the unedited batch with wipe went without a hitch. No biggie since I had done it recently.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
Yeah, I updated mine with the factory image several days ago...I decided to go ahead and let it do the full wipe since I was reading that folks were having issues after removing the "-w" flag. Full wipe is probably the way to go anyway if want to avoid bugs.
For anyone interested who hasn't done this before, I found the instructions here to be quite helpful:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
can i keep root with 4.4 OTA
Alright guys looks like I finally got the 4.4 OTA.
Anyone know how I can keep root???
Flash SuperSU from custom recovery. SuperSU v1.69 worked for me. The latest is 1.75.
--OctOS Powered VZW GS4 Dev Edition
Worked thanks bud