yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] originalnabisco:
I've been staying on Stock 4.2.2 for now, and have had a constant System Update Available notification to update to 4.3 but have been ignoring it. Just now I noticed the update notification disappeared, so I did a manual check for updates in Settings, and it tells me i'm on the latest version (4.2.2: JDQ39)

Do you think this is related to the new OTA update? I'm thinking they took the previous 4.3 off for now and are going to release the new one, but I could be wrong.
[Nexus 4 General] jlvlawrence:
Why wouldn't you want to update to 4.3?
[Nexus 4 General] Freshly_Snipes:
The new update fixes the random keyboard/system freeze issue and the bit coin issue.
[Nexus 4 General] xdatastic:
where did you get the info about bug fix for system freeze from?
[Nexus 4 General] immunityx:
Just received the update it was just under 2mb hardly notice anything different
[Nexus 4 General] xdatastic:
did you not grab the filename\url?
[Nexus 4 General] ceejay83:
Um where did you get that info? JWR isn't effected by the freezing bug in the first place so this doesn't make sense.
[Nexus 4 General] Freshly_Snipes:
bug tracker says solved

All devices aren't on JWR so it doesn't make sense because you don't want it to. New Nexus 7 is on JSS15J so this will bring them all on the same branch. The update isn't just for us.

I'm not claiming to know. But my assumption is that because the issue was marked resolved. So im only guessing. I'm not JBQ lulz
[Nexus 4 General] fernandezhjr:
And where are getting the info about which devices are getting the update?
[Nexus 4 General] Freshly_Snipes:
How about every Android news site. A build for the Nexus 10 "Y build" is in the chromium tracker today. Check Android Headlines, Android Police, Android Central. Google Plus. Do you guys only read on XDA? lol

The information is out there. Use search and you'll see it all like I did hours ago. No need to be snappy sirs.
[Nexus 4 General] fernandezhjr:
All the Android sites are making assumptions like you. I thought you might have some source more official or reliable.
[Nexus 4 General] bozzykid:
Hold power first, then hold volume up while holding power. It should start immediately.
[Nexus 4 General] hungnguyen490:
[MENTION=1566190]efrant[/MENTION] can i use this command "fastboot update update.zip" ?
[Nexus 4 General] sordna:
Interesting. However I will say that recovery.img has *changed* in the new build. I downloaded the full factory image, extracted everything, and compared to the older image, and while boot, bootloader, radio, userdata img's are identical recovery.img even though same filesize (and same old timestamp!!!) is different:

$ ls -l occam-jwr66[yv]/recovery.img

-rw-r--r-- 1 root root 6899712 Jan 1 2009 occam-jwr66v/recovery.img

-rw-r--r-- 1 root root 6899712 Jan 1 2009 occam-jwr66y/recovery.img

$ md5sum occam-jwr66[yv]/recovery.img

61fa4500776097aa903304786d8d1aae occam-jwr66v/recovery.img

fa268c687b52398213136ddedf651880 occam-jwr66y/recovery.img
[Nexus 4 General] hungnguyen490:
it doesn't happen. so strange!
[Nexus 4 General] efrant:
With the OTA update file? No.
[Nexus 4 General] efrant:
Your build.prop file is not stock. Replace it with the stock one.
[Nexus 4 General] spicediablo:
Efrant, I flashed stock system and boot.img following your guide. It seems to work. Not sure what has changed in my build.prop. Perhaps it's caused by Franco's kernel. Thanks!!
[Nexus 4 General] sordna:
efrant's zip is the best way to go

I can independently verify that your provided .zip does exactly what you say compared to the stock one, and does not miss or alter anything it shouldn't. You sir are a gentleman and a scholar!

$ diff -upr ota1 ota2
Only in ota1/META-INF: CERT.RSA
Only in ota1/META-INF: CERT.SF
Only in ota1/META-INF: MANIFEST.MF
diff -upr ota1/META-INF/com/google/android/updater-script ota2/META-INF/com/google/android/updater-script
--- ota1/META-INF/com/google/android/updater-script	2012-09-28 16:20:32.000000000 -0700
+++ ota2/META-INF/com/google/android/updater-script	2013-08-22 16:20:54.000000000 -0700
@@ -463,8 +463,6 @@ assert(apply_patch_space(17916839));

# ---- start making changes here ----

-ui_print("Removing unneeded files...");
-delete("/system/recovery.img");
show_progress(0.800000, 0);
ui_print("Patching system files...");
apply_patch("/system/app/ApplicationsProvider.apk", "-",
@@ -1371,11 +1369,7 @@ apply_patch("/system/vendor/lib/mediadrm
6713bc8134b88289bf2fd5c17bf30d0d174d6eb0, 374184,
9d87d330c5490fec0fca02ba3d7ba17fa7d65e8c, package_extract_file("patch/system/vendor/lib/mediadrm/libwvdrmengine.so.p"));
set_progress(0.999987);
-delete("/system/recovery-from-boot.p",
- "/system/etc/install-recovery.sh");
show_progress(0.100000, 10);
-ui_print("Unpacking new recovery...");
-package_extract_dir("recovery", "/system");
ui_print("Symlinks and permissions...");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
@@ -1383,7 +1377,6 @@ set_perm(0, 3003, 02750, "/system/bin/ne
set_perm(0, 0, 0755, "/system/bin/ping");
set_perm(0, 2000, 0750, "/system/bin/run-as");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
-set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm(0, 2000, 0755, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
Only in ota1: recovery
[Nexus 4 General] lazer155:
I tried flashing this just now (I had stock rom, odexed, stock kernel, cwm recovery) and got the error 7/installation failed message. Do you know why that might have happened?

After flashing it and about to exit recovery, it did the usual asking if I wanted to prevent stock recovery. I pressed yes to keep cwm. After rebooting, it then detected the 4.3 ota update. It tried installing and got the same error 7. However before it installed cwm asked if I wanted to allow an untrusted zip to install because it couldn't verify.

Now it seems like it actually did install at some point because my build number ends in V now.
[Nexus 4 General] spicediablo:
It should end with a Y.

Sent from Mako⁴
[Nexus 4 General] qtekker:
I got error "assert_failed" when flashing the zip file, like lots of you guys. I was on stock rom, but with custom kernel. And I think that's the cause. This is what I did:

Reinstall stock image without wipe (dirty flash). This will put back stock kernel. Restart and update OTA. After that I flashed TWRP to get recovery back. From recovery flash superSU to get root back. Then flash semaphore kernel to get custom kernel back. Now I'm upgraded to Y.

Good luck!
[Nexus 4 General] Sailor Jerry:
I was able to adb sideload the update without issue. Was previously running bone stock JWR66V.

If going back to the stock kernel is all you need to do, just extract the boot.img from the factory image and flash that instead of the entire image.
[Nexus 4 General] sordna:
when you say "reinstall stock image" you mean stock boot.img or all of stock: boot.img + recovery.img + system.img ?
[Nexus 4 General] qtekker:
Yes I know, but I never took the time to read how to extract boot.img from the factory image. It's time to find out, because I expect that it's very basic to extract. Thanks.
[Nexus 4 General] gianton:
This worked like a charm even with Faux kernel, thanks!
[Nexus 4 General] cooljeba:
The update seem to have screwed my Gallery App! :( anyone else facing the issue?
[Nexus 4 General] xdatastic:
in what way is it screwed? mine seems fine.
[Nexus 4 General] carlosmg2:
The zip (CWM-OTAupdate-occam-JWR66Y-from-JWR66V.zip) didn't work for me:

Stock Rom, TWRP recovery, franco kernel, modified system ui for battery mod. :(

Who is the culprit? the root? the kernel? the mod?
[Nexus 4 General] sordna:
that zip saves you from putting stock kernel/recovery, but won't save you if your system apps aren't stock.

Do you have a backup of the stock system ui ? Otherwise you would need to flash the stock JWR66V system.img
[Nexus 4 General] Rondock:
soooo, does this update now remove the app ops thingy?
[Nexus 4 General] sordna:
Couple of people said no, they can still access than menu, however it's not clear if the actual app ops settings do anything :)
[Nexus 4 General] carlosmg2:
yeah, that was it! restored backed system ui, and flashed the .zip and worked. Thanks!!
[Nexus 4 General] sordna:
then hit the thanks button :)

So, what does your modified System UI do exactly, do you have a pointer ? I might want to try it!
[Nexus 4 General] carlosmg2:
It was just a battery mod but as it points out it's for JWR66V so I'll wait for new version

here: http://xdaforums.com/showthread.php?t=2384877
[Nexus 4 General] mariosraptor:
Losing network with the new OTA and cannot reaquire it.
[Nexus 4 General] sordna:
Ok, thanks. I use Power Toggles, which includes a nice numeric battery indicator and avoid messing my /system

https://play.google.com/store/apps/details?id=com.painless.pc&hl=en
[Nexus 4 General] cooljeba:
I have attached the screenshots.. Sometimes it loads fine after a while, sometime this happens..
[Nexus 4 General] papachango:
May I flash it with TWRP?
[Nexus 4 General] Drmol:
Is it safe (not just for this update but in general) to download factory images and fastboot flash system.img and boot.img instead of OTA update? This should keep all my apps (apart from system ones) and data?
[Nexus 4 General] Rusty!:
Clear data for it and let it regenerate the thumbnails?
[Nexus 4 General] Gzaw:
I'm asking myself the same thing... ?
[Nexus 4 General] aleks_:
I'm getting an error at patch check in system/app/ browser provider proxy.apk while flashing the update.....what's the problem?

---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------

How did you fix this?
[Nexus 4 General] Blockberd:
You may want to flash the stock system.img first to replace this APK with the proper stock one. It seems that this APK was altered by some things you may have flashed.

Can you provide more details about the error?

Edit: You also may want to flash boot.img along with the system.img to restore the proper browser provider proxy.apk.
[Nexus 4 General] aleks_:
Assert failed: apply_patch_check ("system/app/browser provider proxy.apk", 0b66314f1bcf2a181a0c3d2d0c53c6b5714571f5", "e65c55fcbed3ea8922be94ad759173ffc678b43")

E: Error in /sdcard/0/download/cwm-otaupdate-occam-jwr66y-from-jwr66v.zip

(status 7) installation aborted.

That's what it says. I've been looking around and it seems I may have to flash system.img from before I flashed the aosp browser. Unless there has been a workaround?
[Nexus 4 General] Blockberd:
You won't be able to install the OTA with the AOSP browser. You have to restore your system back to full stock in order to flash the OTA. It can't verify this APK while trying to flash it.

To restore the proper one you could try to extract it from the factory image or you basically flash system.img + boot.img. That should help you.

Edit:

You may also refer to http://xdaforums.com/showthread.php?t=2145848&page=179 and see that other people have the same issue and every time it is suggested to flash the system.img before OTA.
[Nexus 4 General] aleks_:
Thanks. That makes perfect sense. I know exactly what I need to do. Thank you.
[Nexus 4 General] Blockberd:
I am glad I could help. :)

Let us know if it was working. :)
[Nexus 4 General] bartiki:
Hello guys,

My situation is a bit different cause I have rooted phone, but I left stock recovery. So I have stock recovery, stock ROM, and stock kernel. Phone is rooted however and SuperSU is installed.

I know that the previous OTAs couldn't be installed because of the custom recovery (this is why I left stock one).

I got the OTA yesterday but didn't try to install yet. What will happen? Is this that SuperSU itself breaks this OTA? Or if the recovery is stock everything should go fine and only root will be gone?

Should I unroot it from SuperSU before I try to apply OTA and then get root again usual way? I mean get to bootloader, boot custom recovery:

fastboot boot customrecovery.img

and install SuperSU?
[Nexus 4 General] calyxim:
Is it just me or the colour rendering has changed with this update?

I got it over the air by the way.
[Nexus 4 General] SmXtrem:
Got the update now :D

But i needet wifi for 2 MB :\ why can't I download whit 3G data?
[Nexus 4 General] Blockberd:
Yes, you have to unroot in SuperSU, flash the OTA and flash the SuperSU again. SuperSU sets some permissions to a specific file. This file will be changed(overwritten) by the OTA. This fails due to the changed permission. In order to fix that you simply have to unroot to restore the proper permission.

And yes, your suggested way should work just fine. Good luck!
[Nexus 4 General] bartiki:
Thanks man :). Last question by "flash the OTA" you mean do it from android not adb? I mean "touch to install" from the notification bar?

and after I unroot SuperSU do I have to reboot?
[Nexus 4 General] Blockberd:
I don't know much about stock recovery. What I did to apply the OTA:

- unroot through app

- boot into recovery (I use latest CWM)

- flash required updates

- while still in recovery, flash SuperSU

- reboot

- grant all apps which require su root access again
[Nexus 4 General] oSandmaNo:
Losing network here as well but it comes back after a few minutes
[Nexus 4 General] gianton:
Working fine here.
[Nexus 4 General] menaceinc:
Can you tell me where I can find the proper system.img & boot.img?

I'm in the same situation.

Thanks.
[Nexus 4 General] dejan16v:
TWRP keep root

download Google JWR66Y image file from

https://dl.google.com/dl/android/aosp/occam-jwr66y-factory-74b1deab.tgz

.

Download SuperSU file UPDATE-SuperSU-v1.51.zip find link on XDA forum http://xdaforums.com/showthread.php?t=1538053 and put it on root of SD.

.

Create ADB Fastboot with needed files. Find link on XDA forum http://xdaforums.com/showthread.php?t=1626895 attached as platform-tools-v16.zip

.

Unpack downloaded google image to some folder

(unpack image-occam-jwr66y.zip too)

.

Move all files DIRECTLY to ADB folder (WITHOUT subfolders, just directly)

.

List of files should be like this

.

Volume in drive C is SSD_C

Directory of c:\adb

23.08.2013 12:05 <DIR> .

23.08.2013 12:05 <DIR> ..

12.02.2013 08:08 815,104 adb.exe

12.02.2013 08:08 96,256 AdbWinApi.dll

12.02.2013 08:08 60,928 AdbWinUsbApi.dll

13.08.2013 15:52 108 android-info.txt

01.01.2009 00:00 6,342,656 boot.img

12.07.2013 00:58 2,254,256 bootloader-mako-makoz20i.img

12.02.2013 08:08 157,184 fastboot.exe

12.07.2013 00:58 968 flash-all.bat

12.07.2013 00:58 839 flash-all.sh

12.07.2013 00:58 797 flash-base.sh

12.07.2013 00:58 55,625,216 radio-mako-m9615a-cefwmazm-2.0.1700.84.img

01.01.2009 00:00 6,899,712 recovery.img

01.01.2009 00:00 584,366,700 system.img

13.08.2013 17:43 100,775,392 userdata.img

.

NOTE: recovery.img and userdata.img are going to be skipped to keep your data and root !

.

Open CMD and navigate to ADB folder (C:\ADB)

.

Follow the command sequence below:

adb reboot bootloader

fastboot flash bootloader bootloader-mako-makoz20i.img

fastboot reboot-bootloader

fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img

fastboot reboot-bootloader

fastboot flash system system.img

fastboot flash boot boot.img

fastboot format cache

fastboot reboot

.

To keep root:

.

boot into TWRP recovery

.

choose Install

.

find SuperSU zip file on your SD card (should be UPDATE-SuperSU-v1.51.zip) and

.

install it

.

reboot

.
[Nexus 4 General] Blockberd:
You can optain/extract it from the factory image of JWR66V which you can download here: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz

In that you can find the required files in "occam-jwr66v-factory-08d2b697.tgz\occam-jwr66v-factory-08d2b697.tar\occam-jwr66v\image-occam-jwr66v.zip\"

You may need to download 7-ZIP or equivalent to get to the files. I will also try to just supply the boot.img and system.img from that archive.

Also:

By following [MENTION=4465384]dejan16v[/MENTION] 's guide above you could be able to get JWR66Y running, too. It just seems a bit of a "mess" for this small update. :)
[Nexus 4 General] hp420:
here is the page where all nexus factory images are updated. You'll want the one labeled 'occam'

https://developers.google.com/android/nexus/images
[Nexus 4 General] gercen:
Is it possible to forget about the ota update and flash the whole jwr66y package? I don't care about losing data and root. My bootloader is unlock
[Nexus 4 General] Blockberd:
Yes. You can always just install factory image if there is a new update. That is no difference except it sets the phone back to factory and flashs really every single thing on it.

Would always be the cleanest way to update.
[Nexus 4 General] menaceinc:
Thanks a lot dejan. It worked out beautifully. Now I am going to do it on my Nexus 7 (2013).
[Nexus 4 General] looppingz:
Even though I like to install the .img files, this time I did it all on my phone with the 7 point tutorial. No issue on a nexus 4 4.3V with root.
[Nexus 4 General] sabcik:
Just got it.
[Nexus 4 General] tmkinger:
Unable to flash update

I keep getting -

Warning: No file_contextsVerifying current system..

assert failed: apply_patch_check("/.../SystemUI.apk")

Installation aborted.

I tried reverting the icons pack that i was using with Winterboard, and then tried flashing it, but it still fails.

Any ideas?
[Nexus 4 General] Blockberd:
Try these steps mentioned here:

http://xdaforums.com/showpost.php?p=44903174&postcount=227

Or basically just manually flash the system.img and maybe the boot.img.

I assume you are running stock with just an icon pack, right? Then this should help you out...
[Nexus 4 General] tawfiqmp:
Thanks for this. Made it easy to update.
[Nexus 4 General] aaatoel:
It worked perfectly for me too. I am stock, rooted and with custom recovery twrp. I installed the zip with the recovery and at the it asked me if I wanted to fix root permissions,I clicked yes and everything works great. Thanks!
[Nexus 4 General] ImbaWind:
Filed removed due to application flaw, sorry I neglected the below verification part
[Nexus 4 General] atcchris:
This totally worked! It took about .2 seconds. Thank you!
[Nexus 4 General] tmkinger:
I was going to flash the entire system.img but then I figured I'll just replace the systemUI.apk with the stock JWR66V version.

So I did that and tried flashing the update again...it worked!! :D

Running JWR66Y now!! :D
[Nexus 4 General] mastewman:
Replace build.prop

If you have only modified your build.prop, all you need to do is replace your customized build.prop with the Stock build.prop. Make sure you set the file permissions to rw-r-r as well...
[Nexus 4 General] matze0611:
OTA Problem

This solution worked for me fine, too. Thanks alot :)
[Nexus 4 General] sordna:
Yes, if you fastboot flash the system, boot, and recovery (don't forget recovery) the OTA should work, however you will loose root, recovery (easy to put back afterwards), and any things you may have installed in system like rc scripts, busybox binaries, extra system apps you may have converted with titanium or whatever, etc.

But your regular apps, data, photos, etc will be there, so I'd call it a safe approach, especially if you don't remember what you may have changed in your /system while trying out stuff !
[Nexus 4 General] gercen:
Done! Another question, does the android.policy.jar and odex in v is the same as in y? I have a modded android.policy.jar and odex from v that enables volume wake and I want to apply it in this build.
[Nexus 4 General] Blockberd:
Can you tell me where to find the files? Once I know I will create MD5 checksums and post them here.
[Nexus 4 General] Pokley:
I only converted one user app to a system app. I just converted it back and tried to flash the zip but it failed citing build.prop. I modified that as well for LTE and imagine I need to change that back as well, but used a flash enabler zip found here on xda and am not sure what other obscure changes it might have made and just want to start fresh. Anyone have, or can point me to a stock 4.3 build prop? Or am I oversimplifying and need to just go home and flash the system.img?

---------- Post added at 08:54 AM ---------- Previous post was at 08:48 AM ----------

Can you point me to this please?
[Nexus 4 General] Blockberd:
Nevermind. I found them already in the framework folder.

So here it goes...

JWR66V:

File: android.policy.jar

CRC-32: 4ce28c13

MD4: 9a678024909fc18b0db4d04d3520812e

MD5: 29d855a187380cf69d8965f7512b5ec8

SHA-1: 08e4d88542a6f259b0d825c5e4131817ba72bdd2

File: android.policy.odex

CRC-32: 9cc37f84

MD4: 41439f790e5a5f9fa3f0bd4d0a2d7ff4

MD5: 17e430e06623d41ac0a276c208b1d025

SHA-1: 1799651ab093a3a28e4c47a4d90d8ecd24aa664f

JWR66Y:

File: android.policy.jar

CRC-32: 18a32744

MD4: 796e5050b61f79854f6adf94dff5a967

MD5: 871598de15c8a42e9b4951ae235dabe2

SHA-1: d88037b93a1a6aacdc73e683cbecfb190d1fe9eb

File: android.policy.odex

CRC-32: da428420

MD4: 896c4a680ce31df5d859d6149e69b377

MD5: 98b9d21f81727c417556f909c23486c9

SHA-1: 53a1ca0fca35a65b4e137e2d1f93dedd7350d1d5

So it seems some changes have happen as the hashs are not the same at all. Looks like you have to use the new files and do the changes accordingly. :(

But as I already extracted them... I attached both versions (V and Y).
[Nexus 4 General] Blockberd:
If you want to start fresh you may consider a flash of the factory image. If you want to keep your settings and all you just need to follow this guide (basically download the factory image of Y and flash all image files manually):

http://xdaforums.com/showpost.php?p=44903174&postcount=227
[Nexus 4 General] gercen:
Oh, that's sad. Anyway,thanks!
[Nexus 4 General] akhan47:
I tried to update using the official zip via a custom recovery. It failed (something about failed to update binary) then said I need to fix permissions. Now I noticed a strange change in Gallery, when I'm viewing a single picture I don't have a settings button (just share options). Weird.
[Nexus 4 General] Blockberd:
Try again and post the exact error. What is your configuration anyway?

You can also try to flash the system.img from the factory image of JWR66V:

https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz

The factory image of JWR66Y is located here:

https://dl.google.com/dl/android/aosp/occam-jwr66y-factory-74b1deab.tgz
[Nexus 4 General] efrant:
Yes.

Not only safe, it is the easiest way to update.

Not quite true. You could always install OTA updates using custom recoveries... just place the update file in /sdcard and update (in TWRP, I think you don't even have to put it in /sdcard, you can leave it in /cache if I'm not mistaken.

Yes. And if you skip flashing the userdata image, you will get to keep your data as well...

The only problem with your zip file is that you still do not have the stock SystemUI file. You are using an old SystemUI while all the other files are newer. Next OTA update will still fail for you, because that file is not stock.
[Nexus 4 General] Xoib:
That what I was thinking too.

But also [MENTION=1566190]efrant[/MENTION], in your zip file from 102, there is some CERT. files missing, is it because since you modded it -> It can only be flashed by custom recovery ? The stock recovery will fail because it miss the signed part from google right ? Just trying to make it clear.
[Nexus 4 General] efrant:
Yes, I removed those files because they become useless once you modify the file. Those files do NOT get flashed to your device - they only make up the signature of the file so that it can be flashed in a stock recovery.
[Nexus 4 General] Xoib:
Ok thanks for the confirmation ! :good:

sha1: 640c4d8....c92ee630
[Nexus 4 General] efrant:
No unless you provide more detail. ;) You need to tells us the complete error message it gives you when you try to flash it.