yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] RumoredNow:
Which device exactly???

Most here are waiting for grouper/nakasi: Nexus 7 (2012) WiFi only. Once again I've scoured the net and can find no OTA file posted for nakasi yet. It would be odd for an OTA to start rolling out to Eastern Europe first (no offence) and exclusively.

Random Phantsmagoria has now added the following footnote to KTU84L on the build reference table for nakasi:

http://www.randomphantasmagoria.com/firmware/nexus-7/nakasi/
[Nexus 7 General] oldblue910:
I added that to the website since that appears to be what's happening. If a nakasi OTA surfaces, I'll change it.
[Nexus 7 General] lukaslinux:
Nexus 7 32GB 3G [2012]

Hi @ all

i have the Nexus 7 32GB 3G [2012]

so if i want to go to the KTU84L from KOT49H i need - http://android.clients.google.com/pa...H.21863855.zip if i am right ....

i already got the update OTA bud i could not do it via the normal update procedure ,,,

my device is rootet an i use a custom Kernel (franco r.77)

the custom recovery TWRP 2.7.0.0 is also installed ...

after i hit "yes reboot and do the update" TWRP showed up and nothing happens. ..

so i downloaded the "21863855a5d1e8960003f841347313feab3c665b.signed-nakasig-KTU84L-from-KOT49H.21863855.zip" manualy and tried to install it via recovery ... bud i didn´t got a positive system verification so the update process did not started ...

could someone tell me if i have to install the stock Kernel again that i can do the update? or do i have to install the Stock recovery ? or both?

thx in advance

lukiluke
[Nexus 7 General] oldblue910:
That update is for the 3G model. We do not have an update for the wifi model, yet. Because of that, unless you have a 3G model, that update will not apply. If you have a wifi model, you either flash factory images, or you wait.
[Nexus 7 General] lukaslinux:
Like i wrote i have the 3G Model ... so it should be the update i postet right?
[Nexus 7 General] crazycaveman:
Yes, that is the right update. And yes, you do need to have the stock kernel in order to apply the update
[Nexus 7 General] deny_kei:
Tried with newest nexus root tool kit. Just follow the instruction. Ive did it on my n7 wifi to update to ktu84l. i think it also applies on n7 nakasig.

vs980
[Nexus 7 General] lukaslinux:
big thx crazy man :)

update ..

after going back to stock Kernel i tried again bud got the message system/vendor/lib/hw/power.grouper.so has unexpected contents E:Error in /tmp/update.zip

i installed the stock reckovery and got the same Error gain (did it via ADB + another try with Nexus Root Tolkit 1.8.3)

than i deactivated SuperSu (it says its hidden) same problem

is it possible to do the OTA update without erase all Data ? (i dont want to install all the apps again ...)

someone has a clou?

(i already used the search funktion bud i did not found a clear answer ..)

if its not possible to do it without a wipe i will install Paranoid

thx in advance
[Nexus 7 General] RumoredNow:
You don't need to loose data. :)

Did you use the Remove Root function in Super User settings? Do this if you have not yet. Remove the SU App (no worries you'll get it back later after the update process).

Did you save the stock kernel as a backup inside francoKernel? Restore it. If you didn't save it... Don't panic. Go to the next step.

Do you have the Wugfresh Nexus Root Toolkit? If not - get it and get it installed. http://www.wugfresh.com/nrt/ Make sure it is set up for your current model and OS version and that all files are current for the Toolkit. In the Toolkit click on Advanced Utilities - you can restore stock kernel from here if you need to and you will also restore stock recovery from here.

Download the proper Factory Image if you do not already have it. https://developers.google.com/android/nexus/images

Extract the KTU84L factory image > open folder > open second folder - this is where the bootloader-grouper-4.23.img is, you may need this.

Extract the image-nakasi-ktu84l.zip >open the image-nakasi-ktu84l folder - here are the bits you need to flash: boot.img & system.img

-----

Plug your nakasig into your PC

Open your command prompt.

adb devices

You should get a return if you are connected.

-----

adb reboot fastboot

wait for reboot

fastboot devices

You should get a return if you are in fastboot mode. Do a visual inspection to ensure you are at bootloader 4.23 in the text area of fastboot screen on your Nexus 7. If you are at 4.23, skip this next step, otherwise:

fastboot flash bootloader <filepath>\bootloader-grouper-4.23.img

Wait for it to finish.

-----

fastboot flash boot <filepath>\boot.img

Wait for it to finish.

fastboot flash system <filepath>\system.img

Wait for it to finish.

-----

fastboot reboot

-----

On the main panel for Nexus Root Toolkit, use the button for Root and check (enable) the Custom Recovery option.

You will be at Factory 4.4.3, have root access and TWRP custom recovery without loss of data. Use the francoKernel App to restore your kernel.

Hope this gets you sorted out so you can be up and running with the latest.
[Nexus 7 General] RusherDude:
I've already found some reports of people regarding that 4.4.3 (from the factory images) works really bad, its like lagg (like it lost that trim feature), a lot of input touch problems on the screen, and battery is the worst it ever seen on the tablet. And yes he did a pure wipe..

No doubts why they're holding this..
[Nexus 7 General] lukaslinux:
big thx

your howto worked like a charm big thx :)
[Nexus 7 General] RumoredNow:
That's Awesome Sauce!!! Glad you're back in business.
[Nexus 7 General] keneth_c:
Hey...

I was having the same issue...

I deactivated all Xposed modules, uninstalled them and uninstalled Xposed as well... Still same issue.

I ended up using WugFresh's Nexus Root Toolkit and flashed the 4.4.3 factory image via "Flash + Unroot". Long process but it's done at last :)

You can read the NRT FAQ for the different methods you can use to update... Will most definitely be of great help

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk

---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------

Where were u earlier when I was having trouble with my device (nakasig).... Grrr...

[emoji13]

I had to use NRT and do a "Flash + Unroot" :(

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 General] FormerSlacker:
So is there no 2012 Wi-Fi OTA available yet?
[Nexus 7 General] oldblue910:
As of right now, no. :/
[Nexus 7 General] RumoredNow:
And the longer it becomes since the release of Factory Images, the less likely that an OTA will show up... I've stopped looking for one even as a reference point for others.
[Nexus 7 General] Cooljb:
So are you saying the Nexus 7 2012 Wi-Fi model won't EVER officially be updated to 4.4.3?
[Nexus 7 General] oldblue910:
It'll probably skip 4.4.3 and get the next one.
[Nexus 7 General] RumoredNow:
I'm not official...

But if an OTA was coming, why isn't it out yet???

I just can't see one coming by this point. What the heck could be so wrong with the OTA mechanism that they could not fix it before now. The Factory Image works. All other Nexus and Google Editions got their OTA. The only reason it would not be out if one was prepared would be a broken Updater... Would they not fix that ASAP and roll it out???
[Nexus 7 General] Acill:
I dont get why it hasnt come through yet myself. I got sick of waiting and just restored using the factory image. If anyone know for sure why its the only Nexus device that didnt get the update I would love to hear it. The Nexus 4 even got one so I dont think its a past the life cycle thing.
[Nexus 7 General] oldblue910:
Uh... It's not the only one. The 2013 N7 LTE didn't get it either. On the GPE side, the LG G Pad 8.3 and Moto G are also MIA.
[Nexus 7 General] ariesgodofwar:
I have 2 Groupers, and flashed both with Bshiznits Stock 4.4.3 http://xdaforums.com/showthread.php?t=2533035 and then flashed Franco's kernel (r79) over top of it, and I have not seen any adverse issues. In fact, the intermittent wifi drop outs are fixed, and to be honest, has been very smooth. I have not seen any of the above.While YMMV, I do not regret updating.
[Nexus 7 General] oldblue910:
This thread isn't about custom ROMs. It's about OTAs for the stock ROM. Thanks.
[Nexus 7 General] ALD3:
I have 2 Nexus 7 wifi 2012 and stock 4.4.2 just rooted, never had any problem with wifi dropping out or an other problems.
[Nexus 7 General] nyusika:
i got the ota for Nexus 2012 Wifi today
[Nexus 7 General] markoajda:
OTA is here.

Poslano z mojega Nexus 7 z uporabo Tapatalk
[Nexus 7 General] oldblue910:
First post has been updated. Thanks to XDA member ewm.
[Nexus 7 General] elfacki20:
Hi I just got the update too.. But I'm root and don't wanna loose my data .. How can I proceed? Can someone explain to me or is there a video somewhere ? Thanks
[Nexus 7 General] ALD3:
Edit; Received OTA today 4/17/2014
[Nexus 7 General] RusherDude:
Finally!!

It was only ce921efc1fa9197e9b336ce3f89cbfa2275ea4bb, how couldn't we guess that :(.

Everyone enjoy the last OTA for our device.

EDIT:

The very fact that now everyone (100% of the ppl) is getting the OTA at once confirms that all this time it was testing with an small group of user and fixing problems.

EDIT 2:

Great, with 4.4.3 I'm having again the problem that stopped with 4.4.2: Nexus 7 won't "normal boot" ever, need to hold the button 20-25s to turn it on. Since 4.4.2, it worked good and wake up in like 3-5s like normal, but now it's back to 20-25s. More regression from Google, great.
[Nexus 7 General] Gryphie:
If you just have root and not changed anything else. Download the ota, link in the first post, copy it to the nexus 7, reboot into CWM/TWRP and flash it, then flash supersu/superuser and after that reboot and you are done.
[Nexus 7 General] funtomi:
System is bit faster in 4.4.3
[Nexus 7 General] theinfamous2:
how about battery life after updating to 4.4.3?
[Nexus 7 General] AuroEdge:
I would say too soon to tell. Need a couple charge cycles first
[Nexus 7 General] deny_kei:
Still have lagging play some game. Especially shadowgun dz

vs980
[Nexus 7 General] elfacki20:
Did it and works fine ? thank u
[Nexus 7 General] Nik-Barbour:
Just taken the OTA, then re-rooted.

4.4.3 seems to have a nice performance boost.
[Nexus 7 General] havensed:
Very nice.. Very smooth... Nexus 7 2012... After 4.4.3 update seems to work great... Have had no issue or lag problems
[Nexus 7 General] Nik-Barbour:
It seems to have fixed the launcher problem with apps disappearing out of personal folders on Play Store update too.
[Nexus 7 General] keneth_c:
It's funny you should say that. I've never had this issue with 4.4.2

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 General] phonic:
Not true.

In order for an OTA update to work, every file that the update checks for and patches needs to be there and unmodified. If any of the files it looks at are missing or different (it checks the checksum) then the install script aborts.

In this update's case, it only checks about 200 files. It doesn't even look at the kernel, so that can be custom if you want.

While, generally speaking, custom ROMs will not support OTA updates, making minor changes or removing some apks can be ok. Worst case scenario, it will warn you when it aborts what needs to be fixed. When it does, you can either flash the full image (when it's available) to system, or fix the issue preventing the update from starting.
[Nexus 7 General] osm0sis:
I think oldblue was just talking in a "as a general rule" way since an OTA could have asserts for pretty much any file down the line.

Easier to recommend running complete stock than to have to explain to a thousand people why they are failing OTA asserts. ;)
[Nexus 7 General] phonic:
I assume he was as well, but I prefer to give more complete information so it doesn't confuse people.

While I am running about 95% stock on mine, I always check to see what the updater script does before installing it - this way I'm not surprised if it fails. In theory, you could always just modify the script to get around any issues, but that's not usually a good method since it is likely to break all future updates as well.
[Nexus 7 General] osm0sis:
Yeah modifying the script to get around the asserts is probably the worst idea, yet I see it brought up again and again. If you apply a patch to a modified file you're likely to patch the wrong sections of code, breaking the files. My personal method is to make sure I have stock revert flashable zips for all the mods I use, so when an OTA rolls out, flash my reverts so I am stock and will pass all the asserts, flash OTA, then reapply my mods provided they don't need updating themselves. :)

Thanks for the info about it not having an assert for the kernel though, that'll save me the trouble flashing that back to stock from Franco in a little while when I apply the OTA. :good:
[Nexus 7 General] phonic:
Yeah, you definitely do NOT want to remove an assert and leave the patch line in for any file. That would almost certainly cause the file to be unusable and likely create severe system issues (possibly even a soft brick) - assuming the patch would even be able to be applied anyway. What I meant was that, technically, you could remove the assert and the patch line for a specific file giving you issues. Again, it's not advisable since there are other options, but if you just wanted to get it updated and fix things manually later, it would work. I wouldn't recommend doing it for anything other than inconsequential items, since major things like the framework probably need the patch for the other patched items to work properly.
[Nexus 7 General] oldblue910:
Thank you! Plus, anyone who can actually follow what phonic said wouldn't be coming onto XDA asking why the OTA failed. When dealing with most people who don't know about that stuff, it's much easier to be general and provide a scenario that works for all, rather than being overly specific and confusing more people than you help. :)
[Nexus 7 General] Haul:
I'm a newly registered user and can't post full URLs, but the nakasig OTA is at android.clients.google.com/packages/ota/google_nakasig/65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
[Nexus 7 General] phonic:
THANK YOU!!!!!
[Nexus 7 General] osm0sis:
Great job! Welcome to XDA! You're off to a great start. :)
[Nexus 7 General] phonic:
Hrmmm. I'm getting a very weird error when trying to flash the nagasig update.

One of the first asserts fails:

assert failed: getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia"

However, according to my build.prop file (which I never modified):

ro.product.device=tilapia

ro.build.product=tilapia

Not sure why it's failing since my device, outside of a custom kernel, custom recovery and root, is all stock.

I tried using TWRP and CWM (6.0.1.9), but both fail with that error....

Any ideas?

---------- Post added at 07:57 PM ---------- Previous post was at 07:45 PM ----------

Very weird indeed. I double checked everything but found nothing wrong with my build.prop. Plus, the first check succeeded.

SO, I edited the updater-script in the zip file (see, it does have it's uses ;) ) and removed this:

assert(getprop("ro.product.device") == "tilapia" ||

getprop("ro.build.product") == "tilapia");

Rezipped, pushed and applied it. No issues. The rest of the system checks passed and the patches were applied. I manually chmod'd su back to suid root and removed the recovery recovery files.

I'm not sure if my issue was a fluke or not, but something seems very unusual....
[Nexus 7 General] oldblue910:
It's because you're using the TWRP or CWM for grouper, not tilapia (probably because they don't have one yet). This was a common problem on Motorola Xoom devices where people would try to flash stingray OTAs on wingray recoveries or vice versa. It gets the device ID from the recovery, not from build.prop. Had you flashed that OTA in stock recovery, you wouldn't have had that problem. Until they release a TWRP or CWM specifically for talapia, you'll continue to have that problem.
[Nexus 7 General] oldblue910:
Thank you! The first post has been updated and the file is now mirrored at randomphantasmagoria.com. Welcome to XDA!
[Nexus 7 General] phonic:
Ahhh, thanks, I was not aware of that.

Do you want me to upload the non-stock-recovery-supported version of the OTA zip for others that you can provide a link to?

---------- Post added at 09:06 PM ---------- Previous post was at 09:00 PM ----------

Someone else was having the issue, so I uploaded it here:

http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip

Standard OTA but with the problematic assert removed.

Feel free to add it to your list. I imagine there will be many other people having this same issue.
[Nexus 7 General] mcsmart:
Thanks a lot for the update. I just flashed "JOP40D from JOP40C" on my N7 through CWM 6.0.1.9 and it's working great. For the reference, that's how I did it:

Flashed OTA-update.zip through CWM ("install ZIP file")

Reflashed CWM-SuperSU-v0.98.zip through CWM

Wiped cache and Dalvik-Cache

Mounted /system in CWM

Removed /system/etc/install-recovery.sh and /system/etc/recovery-resource.dat through an adb shell (in order to keep CWM)

Rebooted

There is just one request I have for the OP: Would it be possible to add the md5 sums of the images in the future? Thx.
[Nexus 7 General] phonic:
Your steps 2, 4 and 5 were not necessary. That version of CWM is smart enough to detect if root was lost or if a recovery-recovery file was present and fix it automagically for you. Also, worst case scenario and since you are familiar with adb shell, you could have just chmod'd /system/xbin/su (or wherever you keep su) as 6755 and restored root that way - you didn't need to reflash the SuperSU zip.
[Nexus 7 General] mcsmart:
Okay, thx. I did not know that. I'll keep that in mind for the next OTA update ;) I was reading so many misleading guides on how to apply updates that I figured I'll make sure I won't lose my important stuff.
[Nexus 7 General] phonic:
NP. It's not like you did anything wrong, and your manual changes worked fine.
[Nexus 7 General] Haul:
If you have a machine with shasum installed, the filenames as created by Google already contain the SHA checksum:

$ shasum 659e6288b87d.signed-nakasi-JOP40D-from-JOP40C.659e6288.zip

659e6288b87d896a06cf5fb3df373e22face3d73 659e6288b87d.signed-nakasi-JOP40D-from-JOP40C.659e6288.zip

$
[Nexus 7 General] mcsmart:
I know, but the stock ROM does not contain any tools to verify SHA checksums. However it ships with a md5 command, which would be quite useful if you download and flash the OTA updates without having a PC sitting around.
[Nexus 7 General] wilx:
HELP!

I seem to have somehow screwed up my ClockworkMod recovery, when I try and select it screen goes black ( with or without usb plugged in) and eventually reboots. I have tried reinstalling with nexus 7 toolkit and tried renaming /system/etc/install-recovery.sh and /system/etc/recovery-resource.dat, but still no luck

Any one HELP! Please

UPDATE:

I have n managed to get Clockwork Recovery back on by using ROM Manager from the Play Store. I tried all sorts of other methods, but this was the only thing that would get me any solution. I hope this post helps others. If there is an easier way that anyone knows, or a better method, please let me know.
[Nexus 7 General] Nik-Barbour:
It was a really annoying bug.

Although I did get regular launcher crashes (about 1 every 5 days or so) so maybe it was a dodgy install instead of a bug.

24hrs into 4.4.3 and no regrets so far!
[Nexus 7 General] keneth_c:
Dodgy install I would like to say!

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 General] iurnait:
Hold on to your butts, 4.4.4 images are out

https://developers.google.com/android/nexus/images#nakasiktu84p
[Nexus 7 General] Laugher19:
Woah. I wonder what it does maybe it has the 3.4 nvidia kernel
[Nexus 7 General] RusherDude:
HERE WE ARE AGAIN.

Let's bet: how late will we receive this OTA?

I bet 2 weeks (yes after I/O).

Also I RECKON MY FAIL for saying 4.4.3 was our last OTA.
[Nexus 7 General] Nik-Barbour:
On the bright side - 2012's being late for OTA means Wug has his toolkit up to date long before I use it.
[Nexus 7 General] RusherDude:
Why do you use a toolkit on a Nexus? :confused:
[Nexus 7 General] Nik-Barbour:
Laziness and convenience!
[Nexus 7 General] RusherDude:
Until some day he makes a mistake on the script and you're screwed on such an easy-to-proceed device :p
[Nexus 7 General] Nik-Barbour:
He knows far more than I do. :)

Plus I always let a few try it out before I go myself anways.

The kit saved me another time the tab got softbricked going up to KK

Great toolkit.

My age - I appreciate convenience more and more.
[Nexus 7 General] RusherDude:
"Saved me on softbrick".. on a Nexus.

Mate its just 3 manual comands to fix that in the worst of the cases... and those won't fail lol.

Anyway, it's ur decision hehe. for me, I appreciate having the (minor) skills necessary to get out of any trouble and do the job manually :)
[Nexus 7 General] TheManii:
It's highly unlike the 2012 N7 will ever see an official kernel newer then 3.0, goog simply does not do that. (it's a policy thing, there's no technical reason they cant make the effort if they tried).

Even if they did, linux 3.10 is likely what's gonna be on this year's launched devices.
[Nexus 7 General] brizey:
Well, a little newer. Its 3.1.10
[Nexus 7 General] TheManii:
Yea I ment to say 3.1, that's what the 2012 N7 always had.
[Nexus 7 General] razielpr:
Which one is for the Nexus 7 wifi 2012 im coming from Samsung's TW this is my firs Nexus device
[Nexus 7 General] oldblue910:
The ones at the top. Nakasi.
[Nexus 7 General] estape11:
Hey hey! I update by factory image !

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 General] tcardozo:
Does anyone have a link to a flashable zip for 4.4.4?
[Nexus 7 General] topet2k12001:
Hi, I have the Nexus 2012 wi-fi only model. I did receive an OTA (to 4.4.3) and updated my tablet successfully. From the Philippines here...not sure if location matters since it's wi-fi only.
[Nexus 7 General] ironmaskusa:
Yes, I was also looking for a 4.4.4 zip to flash. I'm sure there will be one around by sunset (EST).
[Nexus 7 General] brizey:
Just extract the boot, system, and userdata images and fastboot flash them.

Ex:

fastboot flash system system.img

Just make sure you back up your internal sdcard.
[Nexus 7 General] oldblue910:
Guys, this thread is for discussion of OTAs, not factory images. If you need help with that stuff, please move it to a more appropriate thread. Thanks!
[Nexus 7 General] RusherDude:
This threads needs so much "factory images" spam cleaning :(
[Nexus 7 General] oldblue910:
I agree. Mods?
[Nexus 7 General] coolestboyz:
Guys,

I m from INDIA. My N7 Wifi 32GB version (KOT49H) getting update notification for v4.4.3. But i have already rooted and have TWRP recovery. Now how to UPDATE my N7? :confused::confused:

sent from XOLO Q800 using TapaTalk2
[Nexus 7 General] dexviajiboy:
I just update like normally from notification OTA 4.4.3, its automatically reboot to TWRP flash update lastnite,

after update,

just flash update supersu to reroot & update supersu binaries back (fastboot custom recovery first eg. TWRP/CWM)...