yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] armada786:
KOT49H from KRT16S:

http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip

I'm assuming this be the link?
[Nexus 7 General] therealbroxy:
I think I just got offered 4.4.2, it downloaded a t 39mb file, booted into recovery and then dispkayed the little android guy on his back with the word error.

I didn't imagine it,but now when i check it says my system is up to date and am still on 4.4.

does 4.4.2 even exist?
[Nexus 7 General] lbrfabio:
Yes, recent news. I guess that's why we didn't receive the 4.4.1.
[Nexus 7 General] therealbroxy:
Very annoying, i guess i cannot get the ota link now i have rebooted?
[Nexus 7 General] EthanFirst:
nakasig-KOT49H-from-KRT16S
[Nexus 7 General] bgrimm:
OK, here is the filname for nexus 7 3G (2012):

11dca0a521765a2f98248410216c393d69971e01.signed-nakasig-KOT49H-from-KRT16S.11dca0a5.zip

Bernd

EDIT: oh, sorry did not see the EthanFirst posting...
[Nexus 7 General] oldblue910:
Thanks everyone. First post has been updated to contain KOT49H from KRT16S for both nakasi and nakasig.
[Nexus 7 General] jb0ne:
Yes but it's good to stay up to date so that when the next update comes out your device is ready.
[Nexus 7 General] EthanFirst:
nakasig-KOT49H-from-KRT16O
[Nexus 7 General] rhyang:
KRT16S nakasi debuggerd

Preemptive debuggerd post :) from KRT16S / nakasi (Wifi 2012).

This time the OTA went fine, as I'd updated TWRP to 2.6.3.1. Lost root + recovery but a couple minutes with Nexus Root Toolkit solved that.
[Nexus 7 General] BradleyR2010:
could anyone post KoreanIme from KRT16S ota is failing on it for me please
[Nexus 7 General] Freshgeardude:
Its been a while since I've kept up with updating roms and such, what does this mean?

I am on 4.4 looking to update it to 4.4.2 and it wont let me because I am rooted. How does this file help? thank you
[Nexus 7 General] EthanFirst:
nakasi-KOT49H-from-KRT16O
[Nexus 7 General] rtiangha:
If you're running SuperSU as your superuser app of choice, sometimes Chainfire clobbers this file in order to keep persistent root after an OTA. However, if an official OTA needs to patch this file, it'll fail if SuperSU modified it. Hence a copy here of the default debuggerd file in case anyone needs to copy it over.

Anyways, just did the OTA myself and it went fine. If you ensure that you have a flashable zip of TWRP 2.6.3.1 and the latest flashable zip version of SuperSU on your device before attempting the upgrade (or any upgrade really, assuming you're doing the OTA upgrades through TWRP), then you can keep root and custom recovery by flashing them immediately after flashing the OTA but before you reboot the machine. That way, you can save yourself a step of having to connect to a PC afterwards to re-root your device (which is handy if you have a device like mine with a busted USB port).
[Nexus 7 General] 3andala:
i tried to flash this for Talipia have stock rom for tilapia using TWRP recovery but i got this error

This package is for "tilapia" devices: this is "grouper".

E:Error exectuing updater bainary in zip ...etc

Any help please
[Nexus 7 General] ol@fson:
I also got this error using TWRP 2.3.6.1 with every tilapia ROM. Downgraded to 2.3.6.0 where it works. Seems to be a 2.3.6.1 bug? I reported this like 3 weeks ago but got no response yet.

---------- Post added at 11:23 AM ---------- Previous post was at 10:37 AM ----------

Just curious, how do I create a flashable zip of the TWRP img file?
[Nexus 7 General] keneth_c:
Awesome... I am now on 4.4.2 (tilapia)

Great work..

I'm now on 4.4.2 on my Nexus 7 (2012) GSM / tilapia. Did it all on CWM recovery :)

For users (Rooted + custom recovery) who are not sure on how to do it...

1. Copy the OTA zip file & SuperSU zip file to your internal sd card

2. Install the necessary zip file for your device via custom recovery (CWM or TWRP).

3. Then mount /system (just in case!)

4. Install UPDATE-SuperSU-v1.80.zip (better safer than sorry!)

5. Reboot device from recovery

6. Enjoy KitKat 4.4.2 ;)

Link to SuperSU flashable zip below:

http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
[Nexus 7 General] blucmal:
The super su download is not working keep getting invalid zips.
[Nexus 7 General] ScanaX:
Open link with a browser...
[Nexus 7 General] Ben Ling:
Hi i tried using TWRP 2.3.6.0,same problem... :(
[Nexus 7 General] dexviajiboy:
did you unroot before reboot in twrp to apply ota.zip?

Sent from my Nexus 7
[Nexus 7 General] Ben Ling:
need to unroot ?
[Nexus 7 General] osm0sis:
Ah good to know, I was wondering how JZO54K could have come before JOP40C. :good:
[Nexus 7 General] oldblue910:
So to reiterate, I need someone who buys a new 3G Nexus 7 to get the bootloader version and the "JOP40C from JVP15S" OTA file name or URL right after taking it out of the box, before updating to JOP40C. Once I have that info I'll post the link to the OTA file in the first post and mirror it on my website for the community. Does anyone have a 3G Nexus 7 on the way and would be willing to help?
[Nexus 7 General] harrypotter222:
My 3G Nexus 7 is on JVP15S, unrooted.

I may have what you want? My notification bar has a system update of 34.7MB, not sure if it is JOP40C? I haven't applied this update yet, since I am fine with bluetooth right now and afraid this update may break my bluetooth issues?

Where do check this file and how to get the file you want? Please guide me.
[Nexus 7 General] oldblue910:
OK...first off thank you! Now for the instructions...

1. Turn the tablet off. Once it powers down, hold down the volume down button while powering on. That'll take you to the bootloader. Note the bootloader version and post it here.

2. Getting the OTA URL on an unrooted device requires use of ADB which is found in the Android SDK. Are you familiar with it at all? Sorry if that's an insulting question but I'm just trying to gauge how much detail I need to go into.

Thanks again!
[Nexus 7 General] harrypotter222:
1. bootloader version 4.11

2. should be ok, i used it before, but recently i had issue with android usb device issue on my windows7 x64 recognizing in adb using my samsung phone, not sure if i will get the same issue with nex7. Give me some URL / Info to follow, then I should able to figure it out.
[Nexus 7 General] oldblue910:
Thanks for the bootloader info.

For ADB, do these steps:

1. Go to Settings > About Tablet

2. Continuously tap on the Android build number until you see a little notification at the bottom of the screen that developer mode has been enabled.

3. Go top Settings > Developer Options

4. Turn on USB Debugging

5. Follow the tutorial at http://xdaforums.com/showthread.php?t=1830108 to get ADB working. The instructions are for a Galaxy Nexus, but they'll work fine for a Nexus 7.

6. Once ADB is working, with your tablet plugged into USB, go to your command prompt and run "adb logcat > logcat.txt" (without the quotes)

7. Let it just sit for about 2-3 minutes.

8. Press Control-C.

9. Open the logcat.txt file that ADB created.

10. Search the file for ".zip" (without the quotes)

11. Post what you find here. It'll be a filename that looks like 12345678abcd.signed-nakasig-JOP40C-from-JVP15S.12345678.zip

Let me know if you have any problems. Thanks again!
[Nexus 7 General] oldblue910:
Someone on another thread hooked me up with the link. First post has been updated!
[Nexus 7 General] oldblue910:
Yeah. So far no tangible proof though.
[Nexus 7 General] oldblue910:
OK people, I needs me some links! I can get nakasi myself since I have a WiFi-only N7, but I need someone with a 3G N7 to get the nakasig update URL for me when it comes! If anyone can help, it'd be greatly appreciated!
[Nexus 7 General] slysir:
trying install JOP40C from JVP15S assert failed Error in zip Status 7

Using TWRP to install this update it fails. So do i have the wrong zip file. Is there a checksum i can use.

513ad3dbbd6b.signed-nakasig-JOP40C-from-JVP15S.513ad3db.zip (34,7 MB)

This is a new Nexus 7C (3G).
[Nexus 7 General] oldblue910:
Thanks for that. That's the JVP15S -> JOP40C OTA that you get out of the box. The update we're now looking for will be JOP40C -> JOP40D. Please keep an eye out when you get that OTA, please post that filename here!
[Nexus 7 General] slysir:
I am still trying to go from JVP15S -> JOP40C. I installed TWRP and rooted, so will i get this OTA or will i have to sideload the zip.
[Nexus 7 General] xdatastic:
http://android.clients.google.com/p...signed-nakasi-JOP40D-from-JOP40C.659e6288.zip

JOP40D for nakasi
[Nexus 7 General] osm0sis:
Nice! Good man! :D
[Nexus 7 General] eak1080:
doesn't flash for me i get an error in recovery :crying:
[Nexus 7 General] xdatastic:
Worked for me. You need to be completely stock to apply it. Use "adb sideload".
[Nexus 7 General] jntdroid:
I flashed it through clockwork - worked like... clockwork :D

I'm completely stock, with root access...
[Nexus 7 General] oldblue910:
Thanks dude. First post updated.

If anyone with a 3G Nexus 7 gets the nakasig JOP40D from JOP40C update, please post the filename or URL here so I can update the first post there too!
[Nexus 7 General] eak1080:
Ok so i cant have used TB to uninstall anything? :/
[Nexus 7 General] oldblue910:
No. In order for an OTA to work, every single file that came on the tablet has to be there. You can't have modified or deleted anything off your /system partition.
[Nexus 7 General] dexviajiboy:
but you must keep supersu.zip in sdcard, after flash ota.zip, flash update supersu to reroot..

Sent from my Nexus 7
[Nexus 7 General] Ben Ling:
but how to unroot it and keep TWRP ?
[Nexus 7 General] dexviajiboy:
unroot in supersu setting & to keep twrp just flash twrp.img via fastboot

Sent from my Nexus 7
[Nexus 7 General] EthanFirst:
nakasi-KOT49H-from-JWR66Y
[Nexus 7 General] jb0ne:
When I tried to go to 4.4, I got an error about debuggerd has unexpected contents.

So I flashed the factory image of 4.4. Then I used the OTA file to go from KRT16O to KRT16S, no problems.

Now I'm trying to to the OTA to go from KRT16S to KOT49 -- and getting the same debuggerd error!!

what keeps messing with my debuggerd? Is there a workaround for this?

====================

Edit: and what's really annoying is that the debuggerd for KRT16S I downloaded from this thread is the exact same size as the one I have! I downloaded it and copied it in with same owner and permissions while in recovery (can't while system is live), and tried again - and it worked!
[Nexus 7 General] keneth_c:
Why the need to unroot?

Without unrooting, I flashed OTA zip and SuperSU zip via CWM recovery.

And then rebooted the device.

All went well and my device remains rooted with CWM recovery.

Is the method different for TWRP?

--
[Nexus 7 General] yusopa:
Nexus 7 tilapia never get 4.4.1. But go further to 4.4.2. All news and image file can get at androidpolice
[Nexus 7 General] dexviajiboy:
ok nvm if workfine without unroot..

Sent from my Nexus 7
[Nexus 7 General] oldblue910:
Thanks. FIrst post updated.
[Nexus 7 General] rhyang:
Good to know. FYI the OTA update script checks your existing file against a known hash (MD5 I think). You can get this value in various file browsers, usually called checksum.

You can also get the original factory image and extract /system/bin/debuggerd using a variety of methods, depending on your PC OS (Google it). Be careful to get the factory image for your specific device and the version you are upgrading *from*.
[Nexus 7 General] rtiangha:
People make them in the grouper TWRP thread (note: this file in the link below is only for grouper devices):

http://xdaforums.com/showthread.php?p=48271108
[Nexus 7 General] jimbobtexas:
Sideloaded 4.4.2 using the Nexus Root Toolkit v1.7.9. Worked flawlessly. Thanks for the ZIP file!
[Nexus 7 General] dgattenb:
Just got 4.4.2 on my stock 8gb 2012 n7
[Nexus 7 General] Antrobot200:
Just updated from KRT16S stock rom(rooted) to Android 4.4.2 (KOT49H) using TWRP 2.6.3.0 to sideload the zip file.

Thank you.
[Nexus 7 General] lekhwani:
Updated. Was stock 32 gb.
[Nexus 7 General] EthanFirst:
nakasig-KOT49H-from-JWR66Y
[Nexus 7 General] pjmarkert:
4.4.2 Problems

4.4.2 update broke MX Player and Joe-VLC.

Also noticed that wifi doesn't always connect, sometimes have to reboot then wifi works fine. This happened at several locations.
[Nexus 7 General] ALD3:
Yes my MX player too. Will have to wait for developer to add support for 4.2.2
[Nexus 7 General] osm0sis:
The factory images are uploaded, Google just messed up the links so they all give 404 errors.

e.g. for nakasi:

4.4 (KRT16S)
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
da7dee497bc343fb8ed15995ccb0692123ee2eab

4.4.2 (KOT49H)
https://dl.google.com/dl/android/aosp/nakasi-kot49h-factory-da7dee49.tgz
5e9db5e1c396e2d1161e428ba28e356e125ecff6

As you can see from the working 4.4 download (and all others before it), the end of the filename is supposed to be the first 8 characters of the SHA1 sum, but for the 4.4.2 links they just incorrectly kept the SHA1 from 4.4. Changing the 8 characters from da7dee49 to 5e9db5e1 results in a working download:

https://dl.google.com/dl/android/aosp/nakasi-kot49h-factory-5e9db5e1.tgz

[MENTION=3423169]oldblue910[/MENTION] Hmm any ideas why the bootloader didn't change in version number, but basically doubled in size?
[Nexus 7 General] oldblue910:
Yeah, the bootloader is probably named after an older version while actually being the correct version. That's been happening ever since JBQ left and someone else picked up doing the factory images.
[Nexus 7 General] osm0sis:
The version number didn't change with the OTA though.. Also check it out:

7b28b45a035efb9aad9e61ad09b1906eb5508721 *jwr66v-bootloader-grouper-4.23.img - 2101kB

ce2951e59da64fa57d281f47031364050c83f49c *jwr66y-bootloader-grouper-4.23.img - 2101kB

7b28b45a035efb9aad9e61ad09b1906eb5508721 *krt16o-bootloader-grouper-4.23.img - 2101kB

7b28b45a035efb9aad9e61ad09b1906eb5508721 *krt16s-bootloader-grouper-4.23.img - 2101kB

1c25b3a40d47b8681b84761efb0750eb84d63f06 *kot49h-bootloader-grouper-4.23.img - 3912kB

Seems to me that "the real" 4.23 is the one that came with 66v (the initial version to contain it) and then again in KK up to krt16s, and these other 2 are anomalies, one for having a different checksum right in the middle of the other 3 which are the same, and the other for being big and possibly completely wrong. I'm going to check them out in HxD and see if I even want to venture flashing it.

Edit: 66y had a weird "msm-radio-update" header tacked on which is the only difference there, but still probably shouldn't be trusted over the other matching 3.

And kot49h is looking completely different, to the point where I think they f*cked up and included the flo-deb bootloader by mistake. It mentions partitions grouper-tilapia doesn't have like sbl1-3 and aboot. Downloading razor to be sure.

Edit 2: Confirmed. It's actually bootloader-flo-deb-04.02.img; That's a pretty gross oversight since it would likely brick our devices to flash it. :mad:

I checked everything else in the nakasi one and it all seems to be correct except for the bootloader, but still, it's sad that we can't trust the factory images anymore. :(
[Nexus 7 General] oldblue910:
Holy crap! It's really amazing how sloppy the factory images have become since JBQ left.
[Nexus 7 General] tylercarter:
Tell me about it. lol. How embarrassing posting broken links like that.
[Nexus 7 General] TheManii:
Out of all the KOT49H factory images, so far the only ones with issues are the nakasi/nakasig bootloader files.

Everything (for all devices) else seems to both be correctly named and the correct contents.

Currently all the links on developers.google.com/android/nexus/images are correct (as in they point to actual files)

But yes since JBQ left the vast majority of factory images either have:

incorrect names

incorrect contents

both

missing files, in one case: missing everything except the script to flash them

There have been more errors in the factory images in the past quarter then there have been for the entire history of android,

though we didnt formally start getting factory images until the NS.

There may be reporting bias as #1 isnt really that big of a deal

At least not from goog itself, some previous devices did get some form of factory image from the original manufacturer, but they dont really count.

Nor were they always as complete as the current ones (ie generally a factory image every release with some exceptions)
[Nexus 7 General] Vyom:
Well, it looks like Kitkat update hates me. I am unable to flash latest OTA KOT49H update.

I have TWRP Recovery installed with MultiROM and triple boot. (Stock Kitkat, CyanogenMod Jelly Bean and Ubuntu Touch). And now I am not able to flash the zip file for KOT49H update. I faced the same problem while updating from JB to KK, when I just had to reformat everything and start from scratch. But it doesn't seem right to flash *everything* as soon as an update comes (specially a 0.0.2 update). :P

So please help me out here! Following screenshot maybe helpful:
[Nexus 7 General] chi_heng:
Sorry, misread your message earlier. Had no experience with Multi-boot, so can't tell that may be the cause of your failed OTA update. The updater script in KOT49H does contain a section to check the integrity of the stock Rom before writing them over with the updates, so I wonder if it may have looked wrongly at the other roms you have in your machine and halted the update process as it couldn't find what it expected.
[Nexus 7 General] Vyom:
Thanks for the reply, and as much as I want to find the solution for this problem, I decided I won't be installing this particular update (4.2.2).

The reason for this decision being the fact that Google have decided to remove a very useful feature or rather the ability to turn off the privacy settings for individual apps. (Refer this article: https://www.eff.org/deeplinks/2013/...cy-features-android-shortly-after-adding-them)

So, until Google decides to re-enable the same, I am going to choose privacy over security. :(
[Nexus 7 General] Imoseyon:
You're failing this check:

apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35") || abort("\"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35\" has unexpected contents.");

If you're brave enough you can flash this zip that I just put together:

http://www.box.com/shared/zbntry3ihffuliqp5f2z

Do a full backup first though. :D
[Nexus 7 General] fozzie:
The LNX partition is the kernel partition iirc, do just needs the stock boot.img flashing.
[Nexus 7 General] Imoseyon:
yup the zip i posted skips the kernel partition check along with others. Just flashing stock kernel may work but another check may fail.
[Nexus 7 General] RusherDude:
No 4.4.1 OTA URL for Nexus 7 (grouper/tilapia)?

I find this strange, since Nexus 4,5,7 (flo/deb) and 10 got it before 4.4.2..
[Nexus 7 General] oldblue910:
Yep, but grouper and tilapia didn't. It's happened before. The only device that ever saw 4.3.1 was the 2013 N7 LTE. There's plenty of historical precedent for it.
[Nexus 7 General] keneth_c:
No 4.4.1 for tilapia. 4.4.1 was skipped. We straight on 4.4.2 from 4.4

--
[Nexus 7 General] Vyom:
I successfully updated to 4.2.2 after flashing your zip file. :good: :D

Thanks so much man!

PS: And as expected, AppsOrb stopped working after this update. Well, Google I hope you will bring it back in later updates.
[Nexus 7 General] osm0sis:
There's a great Xposed module that re-enables native App Ops. :)
[Nexus 7 General] RusherDude:
Yeah but.. 4.3.1 was only for N7 (flo/deb) and 4.4.1 was for EVERYONE but N7 (grouper/tilapia), is a completely different situation :(

Ok. Thank you both!
[Nexus 7 General] osm0sis:
Just another note about the factory images:

I was recently wondering why it seemed like my 16gb grouper was low on space, and of course assumed that it was because I had two user accounts on it. Recently I removed the second and still noticed it reported storage at 6gb total. Pretty much half of what it should be.

I did some tests and if you ever flashed the factory image userdata.img, even after erasing, it may reduce your usable data to that of the 8gb grouper device. JBQ basically confirms this in an unrelated topic here: https://groups.google.com/d/topic/android-building/Z6aUmEH9P4U/discussion

So the answer was to fastboot format userdata and let Android set it up again itself on boot, now I'm back to 13gb reported total storage and restoring my nandroid to see if it holds. :good:

[MENTION=3423169]oldblue910[/MENTION] could you make notes about these issues on your factory images pages? I think the one about the incorrect bootloader being included is especially note-worthy to avoid people bricking.
[Nexus 7 General] bftb0:
[MENTION=4544860]osm0sis[/MENTION]

thanks for that link. I always wondered what the point of that userdata.img file was, given that:

- a factory flash should create a "blank" (empty) /data filesystem

- there are N7 devices of 3 different capacities, so what is the point of a given sparse file size?

- it is obvious from the speed (of that specific fastboot operation) that a file of that size is NOT being transferred.
[Nexus 7 General] etxeide:
Thanks
[Nexus 7 General] aknorts:
Awesome, thanks.
[Nexus 7 General] Ruche:
Quote:

Originally Posted by gravyplaya View Post

Thanks. When I try to go to recovery it gets stuck at the Google logo screen. Any ideas?

install cwm or rom toolbox rom market and go to recovery through those.
[Nexus 7 General] troger01:
Thanks man! :)
[Nexus 7 General] ironmaskusa:
Looks like 4.4.3 will be rolling out soon! :D
[Nexus 7 General] oldblue910:
Yeah. Unfortunately, it'll probably be the last update for the 2012 Nexus 7. By the time the next OTA drops, the N7 will probably be two generations behind and that, of course, means the end of software updates.
[Nexus 7 General] ironmaskusa:
Yeah maybe, but I'm sure someone will be bringing us a taste of some Lollipop after it is rolled out for the others. Especially the CyanogenMod, although I may be jumping yo conclusions. But I've seen the galaxy tab 2 get 4.4.2 rolled from The CM team,. So who knows?! :confused:
[Nexus 7 General] coolestboyz:
can i install these OTA updates.zip file via twrp/cwm recovery on rooted N7 ?
[Nexus 7 General] keneth_c:
Yes sir.

--
[Nexus 7 General] oldblue910:
All,

Android 4.4.3/KTU48F is rolling out starting today. If anyone gets the OTA link for either the WiFI-only (nakasi) or 3G (nakasig) model, please post the filename here. You guys know the drill by now.

Thanks!
[Nexus 7 General] keneth_c:
Sure will.

Download OTA and then don't install...

Where to find the OTA file in btw...? Path?

--
[Nexus 7 General] oldblue910:
If you're rooted, the file will be in /cache. If you're not rooted, you'll want to enable USB Debugging in developer settings, then tap "Take Bug Report". That'll email a big bug report to your gmail account. Open the text file that's attached to that email and search for ".zip". Post what you find.
[Nexus 7 General] Netero Pito:
Good job :good::good:
[Nexus 7 General] keneth_c:
I believe release of 4.4.3 has been postponed.

--
[Nexus 7 General] getnrdone:
Thanks for the links. Good info.
[Nexus 7 General] mik3see:
+1
[Nexus 7 General] TheManii:
Factory images for KTU84L are already out for nakasi/nakasig: Factory Images "nakasi" for Nexus 7 (Wi-Fi)

We still need someone to find the ota files for them though
[Nexus 7 General] brizey:
Always amazes me that people that frequent XDA do OTAs on Nexus devices. Or for that matter, OTAs on any device.
[Nexus 7 General] jb0ne:
What android version is that? No need to ota it if it's a full OS factory image...
[Nexus 7 General] brizey:
Its 4.4.3.
[Nexus 7 General] TheManii:
It's 4.4.3 for everyone, KTU84M for the n5, KTU84L for everyone else
[Nexus 7 General] jb0ne:
Yeah total derp...I should have just clicked the link.

Can't wait to update my N5! Gonna download the images...then see if I can remember how to install it with fastboot and not wipe my system (I won't get the OTA, not using stock kernel)