4.1.2 >>> 4.2 unable to update - Nexus 7 Q&A, Help & Troubleshooting

Okey so yesterday I couldn't wait anymore and wanted to update my Nexus 7 to 4.2 but couldn't.
After restarting it did initiate the update but right after it gave me a red triangle with a (!)
And now I can't see any updates anymore. I yet I'm on 4.1.2 still
Dang it..
Sent from my Nexus 7

Download the 4.2 factory images from google and flash via fastboot.

Consider yourself lucky and stay with 4.1.2

I have the same problem as well. When I first tried to get the update, the Android had a red ! And failed the update. Now, it says no update available....
I'm not sure if I should wait until a more stable version is out, however.
Sent from my Nexus 7 using xda app-developers app

Meh rootbrain is right. Jag ive been reading upp on 4.2 and i better stay on 4.1.2
Sent from my Nexus 7

It's all subjective. Some like it, while others don't. Neither opinion is the end all, be all gospel truth.
Sent from my Nexus 7 using Tapatalk 2

rootbrain said:
Consider yourself lucky and stay with 4.1.2
Click to expand...
Click to collapse
Aren't there enough 4.2 bashing threads that you feel the need to take this one off-topic?
The OP asked for help not for your opinion.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x

Any help would be appreciated...I want to have the latest update, not be stuck...
Sent from my Nexus 7 using xda app-developers app

yanksrock1000 said:
Any help would be appreciated...I want to have the latest update, not be stuck...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you modified, frozen, or deleted any of the stock system files? The update checks for approximately 200 files and if any aren't stock, will fail. Your best bet, as someone else said, is going to be to fastboot flashing the stock image. Be forewarned that you'd be essentially starting from scratch as it would wipe your tablet, but I'd personally find that preferable since you'd be circumventing some of the issues that are irking the most vocal of 4.2's critics.
Sent from my Nexus 7 using Tapatalk 2

I actually just purchased the tablet, and out of the box the first thing I tried to do was update, and it failed.
I'm not very knowlegable about flashing the factory image myself, but I've heard about updating using a "toolkit"? Is this easier?
Sent from my Nexus 7 using xda app-developers app

yanksrock1000 said:
I actually just purchased the tablet, and out of the box the first thing I tried to do was update, and it failed.
I'm not very knowlegable about flashing the factory image myself, but I've heard about updating using a "toolkit"? Is this easier?
Click to expand...
Click to collapse
Yup, easier. But using a command line and the android SDK/fastboot isn't all that hard... maybe your issue is just the universes way of saying you should go learn a new trick. :cyclops:
However I doubt the universe will waste any energy punishing you if you choose to go the easy route. Plus, you can always read the thorough directions for both routes and make an educated decision before you get your hands even the least bit dirty.
using Fastboot: http://forum.xda-developers.com/showthread.php?t=1907796
Wugs Windows toolkit: http://forum.xda-developers.com/showthread.php?t=1766475

najaboy said:
Have you modified, frozen, or deleted any of the stock system files? The update checks for approximately 200 files and if any aren't stock, will fail. Your best bet, as someone else said, is going to be to fastboot flashing the stock image.
Click to expand...
Click to collapse
i have the same issue, but i dont want to fastboot it, what should i do? i havent rooted or anything yet. i have a 32gb no 3g version...

PenguinDroid said:
i have the same issue, but i dont want to fastboot it, what should i do? i havent rooted or anything yet. i have a 32gb no 3g version...
Click to expand...
Click to collapse
Why not, it's a safe operation.
If you're completely stock, and update fails, either try again (and again, and again), or send it to repair (slowest). Or fastboot (fastest).

issak42 said:
Why not, it's a safe operation.
If you're completely stock, and update fails, either try again (and again, and again), or send it to repair (slowest). Or fastboot (fastest).
Click to expand...
Click to collapse
well, in that case, id rather root it and flash a custom rom, and thats probably what i am gonna end up doing... ill see, thanks for the answer

Related

[Q] best way to root 4.1.2?

Hello, my girlfriends new Nexus 7 for some reason wont update to 4.2, its stuck on 4.1.2. So whats the best way to root it on 4.1.2? And afterwards, its possible to flash 4.2 on it, correct? Ive rooted a couple of different phones and customized them, but I want to make 100% sure I dont screw up her second love lol. Thanks for the help!:cyclops:
What is 4.3?
Sent from my Nexus 7 using xda app-developers app
dparrothead1 said:
What is 4.3?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sorry, meant 4.2 LOL
Try Wug's Nexus Root Toolkit. It does a great job and walks you through each step.
thats the one I was looking at! I wasnt sure if I should use that one, or the other Toolkit, but the other one seemed a little more confusing. Thanks!
Wugfresh worked great for me this weekend.
The only unexpected headache was having to deal with device driver issues since I was rooting the n7 on a laptop that I used to root my Galaxy tab a year ago. There were 6-7 Samsung drivers that I had to remove and then reboot the laptop.
Still an easy process but the driver situation made the process take longer than expected (maybe an hour total).
Still, a lot faster and more newb friendly than rooting in 2009
Sent from my HTC Sensation using XDA Premium App
Toolkits are fail. Learn to use adb and fastboot. That way you can be sure of exactly what your doing to your phone and fix it if necessary. It may sound daunting at first but in the long run it's much better.
Sent from my Nexus 4 using Tapatalk 2
zidane1341 said:
Hello, my girlfriends new Nexus 7 for some reason wont update to 4.2, its stuck on 4.1.2. So whats the best way to root it on 4.1.2? And afterwards, its possible to flash 4.2 on it, correct? Ive rooted a couple of different phones and customized them, but I want to make 100% sure I dont screw up her second love lol. Thanks for the help!:cyclops:
Click to expand...
Click to collapse
dr.m0x said:
Toolkits are fail. Learn to use adb and fastboot. That way you can be sure of exactly what your doing to your phone and fix it if necessary. It may sound daunting at first but in the long run it's much better.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Completely agree with this...
-----------
Hi, zidane1341...
Rooting is really simple.
(You will need an unlocked bootloader for this).
Get a custom recovery .img for your device...
Either CWM - http://www.clockworkmod.com/rommanager
...or TWRP - http://www.teamw.in/project/twrp2/103
...it matters little which.
-----------
fastboot flash it.
-----------
Get Chainfires SU .zip package here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Flash it using the custom recovery you've just fastboot flashed...
Reboot... and you're rooted.
-----------
Having said all that though, I don't see how root will facilitate an upgrade of your girlfriends N7 from 4.1.2 to 4.2...
For that you will need the factory stock image for your device, available here http://developers.google.com/android/nexus/images.
There is a thread here http://forum.xda-developers.com/showthread.php?t=1907796, that details how to flash factory stock images.
-----------
On a final note... it's kind of puzzling why your girlfriends N7 isn't being automatically upgraded to 4.2.
When I flash back to stock, (as I do, from time to time), I use JOP40C (4.2) and as soon as I get a WiFi connection, I get 'nagged' about upgrading to JOP40D (4.2.1), which I always allow. And it does so without problems.
If your girlfriends N7 is running (even at the slightest level) a modified version of JellyBean, then the automated update procedure from Google's servers will fail.
Rgrds,
Ged.
Well I know from personal experience, after I rooted my optimus I could upgrade to a newer version of android, I can just flash 4.2 after rooting correct? I called Asus and they said to send it in, but they didn't know what was wrong. My girlfriend is pretty mad about that, so I was thinking I could bypass that by doing it myself.

[Q] Updating via OTA works with TWRP?

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!

What a freakin mess....

So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. I did it, then had trouble rooting it. I decided to just say screw it and then restore my Nandroid backup (which I made like a good boy). Then I got a failed message on the restore. Booted back up to a fresh boot. Brand new "please select your language" .. Wtf? So then I went back to TWRP wiped everything tried to restore again. Now... Fail. So now I can't boot up because I wiped my ROM and I'm freaking stuck all over this 4.3 update. Really?
So now I will try to wait until WUGS toolkit gets updated and see if I can use it to flash a stock 4.3 image to the device then root it. I don't know if i can even use that toolkit if I don't have a ROM on the device. Anyone had experience with such a cluster and have advice? Any thoughts on why the nandroid didn't restore?
:banghead:
Sent from my Nexus 7 using xda app-developers app
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
EddyOS said:
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
Click to expand...
Click to collapse
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
italia0101 said:
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Federico_96 said:
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Click to expand...
Click to collapse
Yep anything you want. Doesn't matter, I was on pa and matrix
Sent from my Nexus 4 using Tapatalk 4 Beta
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
jcnbama said:
So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. ...
Click to expand...
Click to collapse
I could tell this was going downhill after reading this first sentence. Why would you install a custom recovery in order to flash an OTA? I don't mean to offend you but you have a lot of reading to do before you continue flashing anything.
I was in the same boat and confused as hell back in my Nexus One/Galaxy Nexus days. What I've discovered after a lot of trial and error as well as A LOT of reading, is that once you become extremely familiar with using ADB and Fastboot commands you realize how unbelievably simple this stuff really is. Even soft bricks are just small hiccups that won't stress you out anymore.
Learn how to properly use ADB/Fastboot commands through terminal (in OSX) or command prompt (n Windows) and you will realize that the toolkits are silly and do exactly the same thing.
Again, I mean this in the least offensive way possible. This is coming from someone who thought he bricked his Nexus 7 and let it sit in a drawer for 5 months before finally understanding ADB/Fastboot, pulling it out of the drawer and having it back up and running within 10 minutes...
jcnbama said:
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is completely OK. Follow THIS guide (just one of many) to learn how to setup your computer for ADB/Fastboot. Then follow THIS guide to learn how to flash back to completely stock. No current ROM is required on your phone to do any of this.
I swear this is a nightmare. I don't have TBU or anything. I literally have to start over. I am always VERY careful to read and make back ups that's why I use TWRP it's why I make Nandroids and this just sucks. Ugh. I have to piss and moan I don't know where to start lol. Thanks for letting me vent..
Sent from my Nexus 7 using xda app-developers app
jcnbama said:
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
simms22 said:
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
Click to expand...
Click to collapse
Well I do understand that point. It's a good one. I honestly don't know how to use ADB like I should. But at the same time it's a lot easier and if used properly can prevent mistakes. And good Devs make good money in donations so everyone is happy.. Lol :beer:
Sent from my Nexus 7 using xda app-developers app

Stupid 4.3 ota failed!

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

[Q] Am i the only one still waiting for 4.4 OTA?

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.

Categories

Resources