yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] oldblue910:
OP changed: Added the 4.1.1/JRO03C update. The update is purely system files and apps, there is no new kernel or bootloader. In order to apply the OTA, you must be running the pure stock 4.1/JRN84D ROM. Factory images for it are available from Google (link in the first post) and a randomphantasmagoria.com. Enjoy!
[Nexus 7 General] andrewhansen86:
Cool. Thanks.
[Nexus 7 General] loonie01:
These are life savers
[Nexus 7 General] oldblue910:
First post updated with the new JRO03D update files to update both JRN84D and JRO03C. The OTAs are now mirrored at randomphantasmagoria.com as well.
[Nexus 7 General] fung58745:
eocd no find not zip

eocd no find not zip

what this mean and help
[Nexus 7 General] oldblue910:
First post updated with a link to the latest nakasi factory images JRO03D. I have also mirrored the files at randomphantasmagoria.com. You can find older images there as well.
[Nexus 7 General] oldblue910:
If someone gets the Android 4.1.2 update, can someone post the OTA filename here so I can update the first post? There are probably two OTA files...one for people on JRO03D and one for people on JRO03S. If you can help provide those filenames, it'd be greatly appreciated! Thanks!
[Nexus 7 General] Rican7:
adb logcat

I'm logcat'ing again, but obviously there are no guarantees to when I'll get the update. I'm on JRO03D, so I'll only be able to report the update from JRO03D.

https://plus.google.com/113932327271054112747/posts/cVsFFFi5tip
[Nexus 7 General] oldblue910:
Thank you sir! Please post when you have it!
[Nexus 7 General] rayfin:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip

Go go!
[Nexus 7 General] styckx:
nvm
[Nexus 7 General] oldblue910:
Thank you! First post updated! Also, if anyone gets the JZO54K from JRO03S update, please post that filename as well.

The OTA will be mirrored at randomphantasmagoria.com soon!
[Nexus 7 General] osm0sis:
Oh **** yes!
[Nexus 7 General] oldblue910:
For whatever it's worth, the JZO54K update also includes a new bootloader, version 3.41. Looks like it fixes the annoying "can't boot into recovery", and the bootloader freeze bugs.
[Nexus 7 General] osm0sis:
That's worth a lot! Those two bugs were driving me crazy.
[Nexus 7 General] gravyplaya:
how to update

How do I apply these updates? Im on stock, unrooted.
[Nexus 7 General] starskyrob:
Rename to update.zip . Place on root of SD. Boot to recovery.
[Nexus 7 General] osm0sis:
efrant wrote a great guide over on the GN forums. The method should be virtually identical.

http://xdaforums.com/showthread.php?t=1419170 (2nd post)
[Nexus 7 General] The Gingerbread Man:
Side load via adb
[Nexus 7 General] cortexA9:
Very strange.. I got an error..
[Nexus 7 General] deathpod:
Mine booted right up. Restored my old stock 4.2.1 and adb sideloaded. Make sure you're using stock recovery if you're using adb. Otherwise, just put it on your SD and flash in your custom recovery. Has to be over the stock 4.2.1 system though.
[Nexus 7 General] igerup:
Hmm, looks like I have to redownload the patch, got an error complaining about Chrome not being there, or something.
[Nexus 7 General] cortexA9:
Ok works now thanks :) I just updated my custom recovery..
[Nexus 7 General] tom1807:
Doesn't work for me:

Error message: assert failed apply_patch_check ("system/bin/debuggerd",6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

Error in /sdcard/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (Status 7)

Google was not really a help for me, debuggerd is my problem.

Tried with sideload and with TWRP 2.4.0.0
[Nexus 7 General] EAK128:
Get the same message

edit:

Found my problem, I had stock browser installed in system that I had to take out, also someone said in this thread to not wipe cache or dalvik before applying the update.
[Nexus 7 General] hotsync100:
I'm having the same error. Tried with TWRP
[Nexus 7 General] ALD3:
Installed OK with TWRP, just flashed as always. Worked great. Thanks
[Nexus 7 General] igerup:
I guess this applies to a lot of us this time around too. I'm editing now, the set_progress lines should go too?
[Nexus 7 General] JavaJunkay:
Yup, can't flash either on TWRP
[Nexus 7 General] Johnassel:
I got this error, too.

I fixed it by downloading the factory image from here https://developers.google.com/android/nexus/images#nakasi and extracted the file with this tool: http://xdaforums.com/showthread.php?t=1921399

Then I copied it with RootExplorer to /sytem/bin, chmodded it with 755 and after that the update worked.

I've attached the extracted debuggerd - so only the last step is necessary.
[Nexus 7 General] igerup:
Hmm, I just flashed the update but it still shows as JOP40D ?½???

Ah, the files are indeed 4.2.2, it just doesn't say so in the Settings/About window. Probably because I edited the updater-script....
[Nexus 7 General] jenskristian:
I flashed in ClockworkMod 6.0.2.3 without any problems. I did however make sure that no system apps were frozen/disabled in Titanium Backup before flashing as I have had trouble with that before.
[Nexus 7 General] revmra:
Flashing the OTA update via CWM worked fine for me from stock but rooted 4.2.1.
[Nexus 7 General] Polarfuchs:
I succesfully updated my unlocked,rooted stock 4.2.1 to JDQ39 4.2.2 through CWM-touch 6.0.2.3

Do you know what that new circle on the bottom of the unlock screen is used for?

EDIT: ah that's google now on the lock screen
[Nexus 7 General] TopSOUL:
The circle on the bottom of the lock screen was there on 4.2.1 also and i think it is for Google now (as far as I remember that's what it did before I froze Google now).
[Nexus 7 General] ALD3:
USB

So I flashed with tarp and all went OK but now I can't connect to a computer. I did a factory reset and still never see the Nexus7. It's not a driver problem cause my computer never even recognizes it but it does on my phone and Galaxy tab. Anyone else have this problem or a thought on what my problem could be, also tried 3 computers with same results. :confused::confused::confused:

EDITED! !!!!!

Well after several days, I finally found the problem. Seems something was wrong with micro usb connection on nexus 7. Still under warranty so returned it and a day after I have the new 1, 4.2.2 stock ota popped up and installed. All good again. What a headache, charged fine just wouldn't connect to computer.
[Nexus 7 General] Chaosek:
My still says that 4.2.1 is up to date . :(
[Nexus 7 General] tdizzle404:
What are you guys flashing to get 422?

Im away from my computer and can adb right now so a flashable zip would be great :)
[Nexus 7 General] JavaJunkay:
Btw, what Is new?
[Nexus 7 General] ALD3:
Check OP first post, he has moved the 4.2.2 zip there and you can flash in recovery.
[Nexus 7 General] tdizzle404:
So its the link for JPQ39 and the zip is a bunch of letters and #'s starting with 6ece
[Nexus 7 General] Polarfuchs:
Yes, that's the OTA update to 4.2.2

6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
[Nexus 7 General] tdizzle404:
And its safe to flash in recovery? Just don't want to brick nothing lol

Factory reset and wipe caches?
[Nexus 7 General] Polarfuchs:
Since i didn't have stock recovery installed. I flashed the zip via CWM touch recovery.
[Nexus 7 General] Leonhan:
How do u flash it via custom recovery?
[Nexus 7 General] tdizzle404:
Root your tablet, flash twrp through goo, download the zip then boot into recovery and flash it.
[Nexus 7 General] Polarfuchs:
Just transfer the zip files from your PC to the nexus7

Boot into CWM recovery mode

just choose "install zip from sd card"

and selected the zip file
[Nexus 7 General] iamcarl4ever:
Having a similar issue with 4.2.2, can you tell me show me how you did it/provide a fix? :)
[Nexus 7 General] hotsync100:
It works.. thanks!!
[Nexus 7 General] ALD3:
I flashed it in recovery with no problems. I do have a problwm since flashinb, I can't connect usb to my computer. I must be the only 1 with that problem.
[Nexus 7 General] tdizzle404:
Well I tried to flash the zip from the link in the op and
[Nexus 7 General] oldblue910:
Anyone with a 3G Nexus 7 get the update yet?
[Nexus 7 General] tdizzle404:
I guess ill just wait untill someone uses it as a base or somthing .

If anyone has a build built off this ota will you please pm me thanks guys for all your help
[Nexus 7 General] AssailantLF@gmail.com:
Ok, so I want to try out this 4.2.2 thing even if it might be premature. I understand that I need to have a certain previous version (JOP40D) in order to install this new one over it correctly, but my current build number (JOP40G) isn't even listed anywhere around there.

I'm using SmoothROM 4.4 which is a Cyanogenmod 10.1 based rom with the franco kernel. Basically, what do I do to install this 4.2.2 over what I'm using and still be able to switch back, OR is there any additional info available anywhere? Thanks you.
[Nexus 7 General] osm0sis:
The thing that failed, an "assert" also tells you what file you need to fix for the OTA to price proceed.

---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------

OTAs are only for stock ROM. You'll have to flash the nakasi factory image if you want the OTA.
[Nexus 7 General] K0v4L:
Flashing via cwm gives a status 7 error.

Caused by this file: /system/vendor/lib/hw/power.grouper.so

Any ideas what to do guys?
[Nexus 7 General] osm0sis:
You or your kernel flashed a custom PowerHAL somewhere down the line. You need to check that directory to see if the script that did so backed up stock. Then replace your patched one with it. If there is no backup you'll have to download the 4.2.1 factory image and extract the file from system.img then do the same.
[Nexus 7 General] TurboFool:
Going from JOP40D to JDQ39, I get this error during the flash process before it fails and gives up:

set_perm: some changes failed

Any idea what might be giving me that? I'm on stock, rooted.
[Nexus 7 General] oldblue910:
My guess would be you had a root app that made some kind of change top the system partition. Download the JOP40D factory image, flash system.img then try again.
[Nexus 7 General] vboyz103:
working on CM 10.1 or AOKP?
[Nexus 7 General] oldblue910:
OTAs are for stock ROMs only.
[Nexus 7 General] vboyz103:
Thanks!
[Nexus 7 General] Benjoy Ericsson:
I have some questions:

1. My N7 (JOP40D - wifi only) has been unlocked bootloader and rooted. I'm using stock rom and stock kernel. Can I update OTA without bricking my N7? As I know, Sony Xperia devices which is unlocked bootloader will be bricked if updating OTA. In this case, they must be relocked in order to update OTA. Sorry, I just got my N7 last month, everything about N7 is a little bit difference to me :confused:

2. My apps & games will be lost if i install zip from sideload in CWM to update my N7 to 4.2.2? Does it keep root or not? :eek:

Tks in advance and sorry for my bad English. :rolleyes:
[Nexus 7 General] akash3656:
I have a tilapia, but u haven't got the OTA yet. Been clearing Google Service Framework many many times and still no update yet.....

---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------

1. On a nexus, its okay to do OTA even if you have unlocked bootloader. It just works. Man that is nasty on xperias, sounds a lot like HTC phones where u can't update the hboot once bootloader is unlocked.

2. Data/apps/games shouldn't be lost. You may loose root, use voodoo OTA rootkeeper to protect root before you flash. But even if you let's say loose root, you just got to flash supersu zip in recovery like cwm or twrp.

http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
[Nexus 7 General] TurboFool:
I considered that, but it passed verification without any trouble. I went ahead and followed your suggestion anyway, though, just in case, and that did the trick. Thanks.
[Nexus 7 General] oldblue910:
My pleasure.
[Nexus 7 General] uncleswoop:
Why doesn't the server just notice that I need an update? It doesn't make any sense.... Any other program checks for an update against their server, and immediately tells you if you need the update. Why is it such a crap shoot with mobile OS? How many times do I have to force close and clear my google framework service before the server registers my out of date software? Cheap little 5¢ apps and games do it no sweat... But a multi-billion dollar corporation? Forget about it....
[Nexus 7 General] tom1807:
Worked for me, just had to set the permission to 757.

But just out of curiosity:

What caused that, that the "debuggerd" was changed.

I had no stock browser installed, I patched wallet but this I exchanged with the original wallet after getting the first time the error message.

Odd part was, when I check /system/bin, there was a file called "debuggerd.backup", which out of curiosity tried first to rename to "debuggerd" and tested to flash again, but also failed.

With your file, all worked smooth.

thanks again for helping out
[Nexus 7 General] oldblue910:
It's so they can manage server load and also possible damage control... They are releasing a grand total of six updates for six different devices. They roll out in stages so that their servers don't get brought to their knees with an obscene amount of traffic. Also, if there is some kind of major problem with the OTA, they can pull it before it reaches everyone... in other words damage control.
[Nexus 7 General] ALD3:
Ever since I flashed the ota in twrp, I have been unable to connect my Nexus 7 to any computer???? I can connect any other android device to them. Its not a driver problem, it just is not seen in USB? Any thoughts on this? Also I lost root and twrp recovery, so now I can't get root back. Thanks
[Nexus 7 General] oldblue910:
Turn off USB debugging and it will see it. 4.2.2 broke adb on both my N7 and N10.
[Nexus 7 General] akash3656:
I've heard from the Galaxy Nexus thread that you need newer revision of adb for it to work with 4.2.2
[Nexus 7 General] ALD3:
Thanks for the quick response but unchecking USB made no difference. Dang. At least I'm not the only 1 with adb problems.
[Nexus 7 General] Benjoy Ericsson:
Have you updated SDK tools to latest? Maybe it'll solve this problem.
[Nexus 7 General] rayford85:
Update your sdk tools.
[Nexus 7 General] ElectronikBrain:
This fixed my debuggerd problem like a charm. Have to unzip the download file and place it in system/bin. I made a renamed the old debuggerd to debuggerdold just in case. Changed permissions using Solid Explorer.

MANY THANKS!!
[Nexus 7 General] xtcme:
I just flashed the update after reflashing to stock. If you are on stock kernel and ROM just flash the 4.2.2 zip floating around here somewhere. I have no problems, runs faster then before and smooth ROM is not needed by me as of right now. 4.2.2 is very nice indeed
[Nexus 7 General] ALD3:
No I hadn't, read a post about them 3 posts back. So I'm doing it now. Thanks

---------- Post added at 11:29 PM ---------- Previous post was at 11:24 PM ----------

Thanks, doing it now. Understand it affecting adb but not sure it will help usb not see it at all. Just nothing when I plug the Nexus 7 in. I also unchecked debugging too. I lost root which maybe a problem as I would go back and try from there. I've also did a factory reset 2 times, just incase.
[Nexus 7 General] tdizzle404:
Thanks guys finally got 4.2.2 running rooted and custom recovery running. Don't really feel like messing with the adb issue right now but this thing is flying!
[Nexus 7 General] Russ77:
I'm trying to update my WiFi model from JOP40D to JDQ39. Its rooted with the latest CWM recovery. I'm getting the following status 7 error

Assert failed: apply_patch_check("/system/lib/libjni_latinime.so"

Presumable this is because this files exists in the update but not in my system/lib folder. I've never done anything with the keyboard other than play around with swift key. Any in put is greatly appreciated.
[Nexus 7 General] akash3656:
Just reflash system.img from the factory image using fastboot.
[Nexus 7 General] Joiis:
I have JOP4D and I installed cmw but now I want to get rid of it so I have stock recovery and I don't want to wipe the system, so how should I do?
[Nexus 7 General] akash3656:
Guys just got the OTA on my Nexus 7 3G tilapia. Here's the logcat with the link. I'm outside so I can't type it down manually for you.

The update file name is

357318e165a8.signed-nakasig-JDQ39-from-JOP40D.357318e1.zip

PS: Here's the love for the 3G tilapia variant guys.
[Nexus 7 General] akash3656:
Just got it XD
[Nexus 7 General] xdatastic:
Good work. Here's the full link for you nakasig owners...

http://android.clients.google.com/p...signed-nakasig-JDQ39-from-JOP40D.357318e1.zip
[Nexus 7 General] svs57:
N7 3g 32Gb

Flash failed

assert failed

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

getprop("ro.build.product") == "tilapia");
[Nexus 7 General] xdatastic:
did use 'adb sideload' to flash it? is your system completely stock?
[Nexus 7 General] svs57:
I flash using custom recovery. Do I need flash stock recovery first?
[Nexus 7 General] Ydnaroo:
JDQ39 Update on 3G

JB 4.2.2/JDQ39 update installed fine via 'adb sideload' and all working on stock 3G N7 here. :)
[Nexus 7 General] osm0sis:
Nope, but for some reason your build.prop didn't have the correct device name (tilapia) for nakasig. Flash system.img from the 4.2.1 factory image, then try again.
[Nexus 7 General] svs57:
Can you write full description how to flash?

I don't see 'adb sideload' command.

# adb

....

no sideload command...
[Nexus 7 General] radziop:
Probably you have wrong CWM recovery mode. Check if you CWM for tilalapia and not grouper. ;]

Btw can someone post here iWinnIME.apk for Nexus 7? I can't install OTA because i deleted this :/
[Nexus 7 General] phonic:
/\ This.
[Nexus 7 General] osm0sis:
No. That doesn't make sense. The assert mounts /system and checks build.prop. That should have absolutely nothing to do with CWM.

Only ways that could happen is if he doesn't actually have a 3G N7 (tilapia), is running a custom ROM that idiotically changes that value for whatever reason (wouldn't work with the OTA anyway...), or is on stock but edited his build.prop and somehow messed up those values. Provided he is actually running stock and really has a tilapia then he should just flash system.img from the 4.2.1 factory image to fix up the build.prop and any other changes to his system he may have inadvertently made.

Same advice goes to you people with the various keyboard apk problems. Either flash the system.img or extract the files you need from it.
[Nexus 7 General] g.lamprou:
adb update ...

i get this error ..

assert faild: apply_patch_check /system/framework/framework-res.apk

anyone?
[Nexus 7 General] osm0sis:
Read the post above yours. Same advice applies. There is no need for people to continue asking about every single different file.

I'm going to make this really simple because somehow the obvious seems to escape a lot of people whenever OTAs roll out:

Whatever the assert failed on is what you need to fix.

Eg. If it's framework-res.apk then you must have removed/modified/patched it somehow and you need to revert to stock.

2 ways to do that:

1- Extract the files you're failing on from the system.img of the Factory Image of the version you're currently running. In this case 4.2.1.

Here are instructions from the GN OTA thread: http://xdaforums.com/showpost.php?p=28181832&postcount=2

2- Fastboot flash the Factory Image system.img entirely. It will accomplish the same thing in one easy step, you'll just need to reroot afterward since su will be removed.
[Nexus 7 General] g.lamprou:
thanx anyway ..
[Nexus 7 General] svs57:
root@android:/ # getprop ro.build.product

tilapia

root@android:/ # getprop ro.product.device

tilapia

TWRP 2.3.2.1 touch recovery

adb sideload didn't solve. The same error
[Nexus 7 General] osm0sis:
Looks good. SHOULD work. But if you're running stock then follow my advice anyway, since like I said, SOMEHOW it's messed up and the OTA doesn't like it. Double check you have the correct OTA as well.
[Nexus 7 General] Ydnaroo:
I just followed this and it worked fine.
[Nexus 7 General] oldblue910:
Can someone who has updated a 3G Nexus 7 to 4.2.2 do me a favor? I need to know the new baseband version (under Settings | About Tablet) and also I need someone to reboot into the bootloader and verify that the new version is 4.18.

Thanks!
[Nexus 7 General] oldblue910:
That has EVERYTHING to do with CWM. He's running CWM for grouper, not tilapia. That's a flag within the recovery. When it does that assert, it asks the recovery what device it's on, and the recovery is telling the script that it's "grouper", not "tilapia" because grouper is what it was made for. That assert is going to fail every time until there's an actual CWM image for tilapia.
[Nexus 7 General] osm0sis:
Really? Sh*t didn't know that. Stupid issue since it shouldn't affect the OTA reading the build.prop but somehow it does, eh? Apologies folks. :)

My advice still stands for all file asserts, however. If it's failing on a file, use the methods I posted above. And please don't post until you've at least tried.

Yeah that's really weird because that's not how getprop in edify is supposed to work. You mount system first and it's supposed to grab those from the build.prop.

As for having an actual image for tilapia. Shouldn't 6.0.2.3 work?

download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.2.3-tilapia.img

and he's using TWRP, so same difference?

techerrata.com/file/twrp2/tilapia/openrecovery-twrp-2.4.1.0-tilapia.img
[Nexus 7 General] oldblue910:
Yes those should work. People ran into that same issue back when JOP40D rolled out 3 months ago. People were using grouper recoveries and the asserts were failing when checking device. I'll bet you dollars to donuts his recovery was designed for Grouper. All he should need to do is flash a tilapia recovery and he should be all set.
[Nexus 7 General] osm0sis:
Again, frigging weird if you know how getprop works. Thanks for the info! :)

Oh, about the nakasig bootloader, I can pretty much guarantee it will also be 4.18, since I checksummed 4.13 for both devices when I was writing my BootUnlocker Script guide and they were exactly the same. :good:

Edit: There we go! :p
[Nexus 7 General] Ydnaroo:
Baseband 1231_0.17.0_1205

Bootloader 4.18
[Nexus 7 General] oldblue910:
Thanks buddy!
[Nexus 7 General] xtcme:
If anyone is curious and it may have been mentioned, but I used the tool ( not wugs) in development thread to flash stock then downloaded the 4.2.2 patch and ran it and am running 4.2.2 just fine. Though o was willing to flatten my device completely with tool, I had all my pics and music in cloud. Hope this helps. 4.2.2 runs quite a bit faster then 4.2.1 and faster then I remember 4.1.2. Happy flashing.
[Nexus 7 General] jaysus145:
Thank you sir! I appreciate the leg work.
[Nexus 7 General] tdizzle404:
I had the error and the easiest way I found to get 4.2.2 to flash was to use wugs toolbox from his sticky in development and just flashed the stock image.

You can also back your device up with his program So DO THAT and I also backed up my internal storage because this method wipes every thing, But any ways flash stock then root. Boot phone ,set up phone update super su app and busy box installer then flash twrp via goo then download ota keeper and remove root. Boot into recovery and flash the update zip that is posted in the op. Reboot and your good.

You will have to update sdk if you want to use adb.

Stock 4.2.2 is really amazing so far.

And thanks for the help guys
[Nexus 7 General] ALD3:
Updated SDK and still unable to see device......not just adb, I mean the computer does not see my nexus 7. 3 desktops, 1 laptop all with win7 32 or win7 64. They all see all my other android devices, I know its weird. Does anyone one know how I could get back to another version, so I could start over? Tablet works fine, its just with no USB and no micro sdcard is hard but I do use several cloud devices.:confused::confused::confused:

Even having trouble using xda on nexus
[Nexus 7 General] mustbepbs:
Anybody get ApplicationsProvider.apk Status 7?

I'm on JOP40D stock deodex with root, stock kernel. Is the deodex causing issues? Flashing with CWM. Grouper.