yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] agent00f:
apply_patch_check fails

Does anyone know where the OTA downloads to? I got the update, it booted into TWRP recovery, some text scrolled by and system wasn't updated when I rebooted (and now settings->update says "up to date" even though still on 4.2.2).

So I tried to manually download and install the zip here, but it fails on apply_patch_check for /system/etc/recovery-resource.dat. No idea what that is or how that managed to change (can that be safely skipped?). Can someone post their original or where to find stock 4.2.2 one?

Damn this 4.3 ota/update business is hella finicky.
[Samsung Galaxy Nexus] jcsww:
From what I've read, a lot of the issues are with TWRP users. Have you tried CWM?
[Samsung Galaxy Nexus] agent00f:
I would if I could for the stock ota, and I don't think it matter for the zip downloaded here since the failure is a check that every recovery should be doing.

---------- Post added at 06:04 PM ---------- Previous post was at 05:55 PM ----------

WTF, I even extracted recovery-resource.dat from 4.2.2 system.img for yakju, and it still says assert failed apply_patch_check. Piece of ****.
[Samsung Galaxy Nexus] The Gingerbread Man:
Just fast boot all imgs from Google factory image part from user data. Nothing will be lost and it has the exact same end result
[Samsung Galaxy Nexus] agent00f:
How do I do that? I see in flash-all.sh:

fastboot -w update image-yakju-jdq39.zip

(example from 4.2.2)

Do I extract the imgs except userdata from the zip and install them individually or what? Thanks.
[Samsung Galaxy Nexus] osm0sis:
-w = wipe, so don't do that.

---------- Post added at 11:52 PM ---------- Previous post was at 11:23 PM ----------

Complete wipe and flash of the stock JWR66V Factory Image and Most Visited is still blank in Browser. Is anyone else seeing this problem?

Edit: Downgraded to the apk from stock JDQ39 and it's the same.. must be some of the new security features backfiring.
[Samsung Galaxy Nexus] agent00f:
Ok, I'm sure this suggestion works, too, but I went with fixing the files for update instead (extracted from 4.2.2 img). Warning to be careful about recovery, as update broke it and I had to install it again manually (goomanager doesn't work w/o root, and cannot flash root w/o recovery, it's catch 22). Sigh, terrible testing from goog, I can imagine average user would just be stuck on 4.2.2.
[Samsung Galaxy Nexus] Juhler:
Thanks, worked like a charm! :highfive: Now with 4.3 with root.. :laugh:
[Samsung Galaxy Nexus] efrant:
Yes, OTA updates are finicky business. Easiest way to update is to download the 4.3 factory image from Google's developer site, extract the system and boot images from within, and flash them using fastboot. (You may have to boot into TWRP and wipe cache.) Done.
[Samsung Galaxy Nexus] shakalaca:
Tried every version only got this :P

http://android.clients.google.com/p....signed-yakju-JWR66V-from-JOP40D.83c30f87.zip

---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------

BTW, the device goes into boot loop after I upload the modified build.prop, something's wrong with opengl I guess. Anyway I managed to flash the factory image and got the OTA.. :P
[Samsung Galaxy Nexus] TheManii:
Does every version include both yakju and takju?

Hmm surprising that at least JOP40D -> JWR66V for takju doesnt exist then if that's the case.

How are you modifying the build.prop? are you editing it on a pc or directly on the device?

If you do it on a pc and adb push it back, remember to do a

chmod 755 /system/build.prop

either from adb shell or a terminal emulator on the device.

If you push it and dont reset the permissions it will likely bootloop like you've seen.

Edit: i will also add mictacea to that list for anyone with a toro (VZW GN).

I dont know if you can check toro otas on maguro or vice versa.
[Samsung Galaxy Nexus] shakalaca:
Oh you're right I set the wrong permission :P

and yes, I've tested on both yakju & takju, I'm wondering if this method can get the OTAs for toro on maguro .. ;)
[Samsung Galaxy Nexus] efrant:
Not that it would make a difference, but the default permissions on build.prop are 644.
[Samsung Galaxy Nexus] TheManii:
Apparently I am able to check for N4/2013 N7 wifi/2013 N7 LTE otas on my 2013 N7 wifi with extended build.prop edits.

I dont think I can check beyond that with just my N4/2013 N7, so it still requires someone with a GN. (unless someone wants to donate a GN so I can check every branch :) )

If someone with maguro (GSM GN) is willing to check for mictacea otas, I will update Post #2159 very soon with the values to change.

At the moment 4.3 isnt available for mysid yet, but when it eventually comes out someone with a maguro/toro (ie GSM or VZW GNs) device could check, regardless of the fact it's for a different device (in the case of maguro at least).

Edit: mictacea / mysid / glass_1 have been added to Post #2159
[Samsung Galaxy Nexus] switch85:
New Build JWR66Y

New Build JWR66Y

Yakju JWR66Y from JWR66V: http://android.clients.google.com/p....signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip

To apply this update I had some trouble...

A full unroot is needed ..than we are able to apply the update and flash superSU again..but I don't know why, after the suspersu flash, the Su binary is installed but not the app..installed from the playstore..
[Samsung Galaxy Nexus] osm0sis:
Nice! Hopefully it fixes Most Visited in stock browser.
[Samsung Galaxy Nexus] r.albu:
I've a rooted JWR66V yakju GN and just removed a line from buid.prop (the one for removing navbar)before trying this, rebooted and rebooted again to bootloader. I've used Method 2 - Stock recovery installed, Unlocked bootloader.

But I get this:

Why would this happen? Any tips or solution?

Thanks
[Samsung Galaxy Nexus] switch85:
Full unroot than flash the update and SuperSu
[Samsung Galaxy Nexus] r.albu:
Thanks!

I had misread your previous post: that did the trick ;)

SuperSu was there after flashing though: good.

Cheers, ra
[Samsung Galaxy Nexus] osm0sis:
Took a nandroid and am trying the Framework trick to get takju.. still nothing though.
[Samsung Galaxy Nexus] Shuvo_bd:
not working here. i was messed with my previous rom so this morning flashed the stock 4.3 takju again. then flashed TWRP recovery(latest) and rooted the device by flashing superSU. just after that, noticed that New OTA update is already out. :D, downloaded the OTA.zip. then i full unroot my device using superSU full unroot option. after that tried to flash the OTA.zip from TWRP. but it failed. :mad: What exactly do i need to do??
[Samsung Galaxy Nexus] gialakias:
It is very simple, you have to wait for the takju OTA to come out to flash. If you flash the wrong OTA to a phone I don't think it is ever gonna work!
[Samsung Galaxy Nexus] Shuvo_bd:
It means i m pretty messed up right??:D According to u this OTA is only for Yakju right??
[Samsung Galaxy Nexus] gialakias:
No it's not according to me, I read the OP and wrote my answer. Wait and it will be out soon for your takju. Or make it yakju ;)
[Samsung Galaxy Nexus] Shuvo_bd:
Yes, actually i was a bit more excited. :o, that Yakju part skipped my eye. thanks btw.
[Samsung Galaxy Nexus] Hotshot205:
Let me get this correct, go to supersu app in settings click full unroot, reboot into recovery and flash update and supersu zip and reboot phone?
[Samsung Galaxy Nexus] bigfoot1942:
Got the V to Y Takyu OTA update.

Can you guys use it?

https://www.dropbox.com/s/7lqsyir8g....signed-takju-JWR66Y-from-JWR66V.8069c140.zip
[Samsung Galaxy Nexus] Shuvo_bd:
Full unroot in superuser, reboot to recovery, flash OTA update and then reboot phone. After rebooting, go to recovery again and flash the super SU. it should work. I did exactly like this and now its working.
[Samsung Galaxy Nexus] oldblue910:
Thank you!

The link on Google's server is: http://android.clients.google.com/p....signed-takju-JWR66Y-from-JWR66V.8069c140.zip
[Samsung Galaxy Nexus] efrant:
Maybe. Flash the normal CWM and try again.
[Samsung Galaxy Nexus] mikeydangerous:
The MD5 is correct, and I'm using CWM 5.5.0.2. No idea what's going on. Maybe I'll just do a full wipe this weekend and start from scratch. I've been having some odd problems with my Nexus anyway.
[Samsung Galaxy Nexus] Tbbo514:
when i type >> cp /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip /cache/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip

it always says

sh: cp: not found

forgive me if im doing something wrong lol definitely my first time applying an ota like this
[Samsung Galaxy Nexus] efrant:
Did I tell you to do that? If so, I apologize. If you don't have root, chances are you won't have busybox installed, so you won't be able to use cp. Use this instead:

cat /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip > /cache/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip

EDIT: I did mention in the first post that methods 3a and 3b assume you have busybox installed :) but anyway, I changed it to use cat instead of cp.
[Samsung Galaxy Nexus] lasentenza:
Just install after rooting, nice work! Thanks.

Will test now ICS 4.0.4 :p
[Samsung Galaxy Nexus] EspadaKiller:
Sorry guys, kinda noob on this but, after reading the instructions it seems that if my phone has a custom ROM built in I can't flash the 4.0.4 update? I would need to make it back to stock before doing so?
[Samsung Galaxy Nexus] efrant:
Correct. The update is to update a stock 4.0.2 ROM only.

No. If you have to flash anyway, you can flash the 4.0.4 stock image directly. There is no need to flash 4.0.2 and update to 4.0.4 with the file in this thread.

You need to follow the directions here.
[Samsung Galaxy Nexus] EspadaKiller:
Ah I see, thanks. So I would have to wipe everything and revert back to normal mode without any ROMs/Kernels in order to install the 4.0.4 update?

But the link that stated shows that I should flash IMM76D, but mine is ITL41F, is it okay to download that? Or which one should I download?
[Samsung Galaxy Nexus] efrant:
IMM76D is 4.0.4. ITL41F is 4.0.1. What are you trying to do? If you want stock 4.0.4 (which is IMM76D), follow the instructions in the link I gave you.
[Samsung Galaxy Nexus] EspadaKiller:
Alright, I got it. Thanks!
[Samsung Galaxy Nexus] Tiggerbits:
I have tried normal and touch CWM, and both are showing the same issues. I am unable to flash 4.0.4 ( IMM76D) from the link you have posted
[Samsung Galaxy Nexus] efrant:
Just to confirm: you are running STOCK yakju ICL53F, correct? And when I say stock, I mean stock (i.e., a build signed with Google's platform keys), not an AOSP build, not a deodexed build. The update zip will NOT work if your ROM is built from AOSP or if it is deodexed, regardless if it says yakju ICL53F.
[Samsung Galaxy Nexus] Tiggerbits:
Hey,

I can confirm that it is Stock Yakju ICL53F, It is rooted, with unlocked bootloader and customer recovery (CWM Normal) It is not AOSP or Deodexed.

I had changed the mediaprofiles.xml to improve the camera quality but have put that back to stock

I have followed you instruction in the first post,

download the zip file. Delete the recovery folder, placed into /sdcard rebotted to recovery, selected install zip from sdcard and choose zip from /sdcard.

I get to the point -

Verifying Current system...

assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4171776:f112025cd60ee4de1c2fea2e472719a3680e3e4c:4247552:ac129e5b2f4a36106eaa586d5aa2174db4040fd4")

E:Error in /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip

(status 7)

Any possible ideas?

and i appreciate the help
[Samsung Galaxy Nexus] adrynalyne:
non-stock kernel.
[Samsung Galaxy Nexus] efrant:
Like adrynalyne said, you have a custom kernel. Download the ICL53F stock images and flash the boot.img file in fastboot, then apply the update.
[Samsung Galaxy Nexus] Tiggerbits:
Thank you to the both of you.

It appears to be working.

Did not think I had a custom kernel... is it the same as an insecure boot.img?
[Samsung Galaxy Nexus] efrant:
The kernel is part of the boot.img file. So yes, if you modified the boot.img file, it is certainly not stock. An insecure boot.img is a modified boot.img...
[Samsung Galaxy Nexus] td00:
I dunno, it keeps saying installation aborted for me even after I "flashbooted" that boot.img file from 4.0.2 as mentioned above.
[Samsung Galaxy Nexus] efrant:
What is the error when it aborts?
[Samsung Galaxy Nexus] BobbyTheNinja:
Very nice post. Thanks for this. I ended up rooting using the method without unlocking the bootloader and then using Method 3a to get 4.0.4 on my phone and it worked perfectly. So I am unrooted now with locked bootloader and stock recovery just like I wanted.
[Samsung Galaxy Nexus] oldblue910:
mysid JWR66Y from JDQ39...

....

....

....

BWAHAHAHAHAAHAHAHAHA just kidding. :D
[Samsung Galaxy Nexus] efrant:
:) It's not 2014 yet.
[Samsung Galaxy Nexus] Hotshot205:
Used your method and everything updated with a problem.
[Samsung Galaxy Nexus] -Dante-:
The update zip file works but i lost root and now the chainfire supersu zip file doesnt work. Waiting for a fix.

Enviado desde mi Galaxy Nexus usando Tapatalk 4 Beta
[Samsung Galaxy Nexus] efrant:
You need to use this version of SuperSU.
[Samsung Galaxy Nexus] JuggaloDroid:
I got the ota but it didn't change anything and I was still at jwr66v. So I came here and got the zip but when I went to flash it in cwm it was aborted and I got a red triangle. System rebooted fine but not sure what happened. Should I just flash the system.img from the factory image or does anyone have any other thoughts? Thanks in advance :good:
[Samsung Galaxy Nexus] efrant:
Flashing the stock boot and system images will work just fine.

If you want to use the OTA update file, you'll need to "unroot" if you have root. (I need to update the instructions in the second post.
[Samsung Galaxy Nexus] JuggaloDroid:
Thanks for the reply. I'll check it out for the instructions :highfive:
[Samsung Galaxy Nexus] osm0sis:
Worth noting this isn't because of Google, it's because of the way Superuser and SuperSU are locking install-recovery.sh from tampering since they use it to run their daemons on stock.

Provided you've got root through a native service in your kernel's ramdisk you can safely delete install-recovery.sh after running:

busybox chattr -i /system/etc/install-recovery.sh

You can also run that command before applying an OTA and that will allow it to do what it wants. You just may need to flash the rooting zip again afterwards if your kernel's ramdisk isn't setup as I said above.
[Samsung Galaxy Nexus] :
I'm on deodexed ROM ... can i use this to update ?

is it possible to create flashable zip for deodexed?
[Samsung Galaxy Nexus] -Dante-:
Now it works. Thanks

Enviado desde mi Galaxy Nexus usando Tapatalk 4 Beta
[Samsung Galaxy Nexus] Sh0k:
I removed root to update with adb sideload or OTA update but the installation fail, I solved this issue removing some checks in updater-script and removing some files then I flashed it with TWRP and it works.

This is the file for takju ROM stock updated:

https://mega.co.nz/#!iYc0Ga7J!JuFj6A86UDU6ss1_rXraCVCRDtYWVHQICotrWM3pvMc
[Samsung Galaxy Nexus] shakalaca:
Got new OTA ..

http://android.clients.google.com/p...c.signed-takju-JWR66Y-from-JDQ39.a00dd838.zip

http://android.clients.google.com/p...1.signed-yakju-JWR66Y-from-JDQ39.0de35707.zip
[Samsung Galaxy Nexus] :
big... now i will try to make it working on deodexed... ;)
[Samsung Galaxy Nexus] osm0sis:
Deodexed won't work; it changes all the apks so it'll fail all over the place. Just flash the system.img.
[Samsung Galaxy Nexus] TheManii:
Since JWR66Y is out, can anyone grab the other ota links for it?

Post #2159

Directions are the same, just remember that you must be able to get JWR66V -> JWR66Y before being able to get the rest, it's all or nothing.
[Samsung Galaxy Nexus] adam.eno:
Anyone know what this update fixes?
[Samsung Galaxy Nexus] gmahomarf:
I had the same problem. My device is a yakju, but apparently, during the last OTA (JWR66V from JDQ39), my build.prop file changed:

ro.build.id=JWR66V
ro.build.display.id=JWR66V
ro.build.version.incremental=737497
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Thu Jul 11 02:12:21 UTC 2013
ro.build.date.utc=1373508741
ro.build.type=user
ro.build.user=android-build
ro.build.host=wpee26.hot.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=takju
ro.product.device=maguro
ro.product.board=tuna
...
ro.build.description=takju-user 4.3 JWR66V 737497 release-keys
ro.build.fingerprint=google/takju/maguro:4.3/JWR66V/737497:user/release-keys
...

So the OTA update that I got this morning was for takju, which is why I assume it failed to apply some of the changes. I'm going to try manually changing the ro.product.name to yakju, try to install the yakju JWR66Y update (which is what I should've gotten in the first place), and see how that goes. If not, I'll have to flash factory img.

EDIT: Stupidity is infinite. I forgot I'd flashed a takju factory image a few months bacl. Still, I'm getting some errors updating to JWR66Y...
[Samsung Galaxy Nexus] laithmurad:
I'm having the same issue, did you manage to fix it?
[Samsung Galaxy Nexus] gmahomarf:
Yeah, sorry for not posting sooner. There's two ways to do this (You need root for both). Using adb shell normally:

su
mount -o remount,rw /system
cd /system/etc
chattr -i install-recovery.sh
mount -o remount,ro /system

Using adb shell from Clockwork Recovery (the mount command isn't needed here, because CW mounts /system as rw already):

su
cd /system/etc
chattr -i install-recovery.sh

That should allow you to install. Good luck!
[Samsung Galaxy Nexus] laithmurad:
Thanks man, worked like a charm :cool:
[Samsung Galaxy Nexus] Xenograph:
Had problems applying the

update from JWR66V to JWR66Y

on my galaxy nexus running YAKJU build.

I always received a Status 7 error even with supersu removed.

So I found this interesting post:

http://xdaforums.com/showpost.php?p=44862564&postcount=24

Thanks to myvijay, this is how I resolved the Status 7 error when using CWM on my rooted device:

!!! WARNING: THIS IS FOR

YAKJU

ONLY !!!

1) in SuperSU, go to Settings, and choose 'Full Unroot'

2) copy the attached zip file to the phone.

-> according to myvijay, I removed all the recovery-stuff and checksum-stuff from the updater-script.

3) copy UPDATE-SuperSU-v1.51.zip to the phone

4) now restart phone into recovery mode (power off; then press both volume-keys and power-button)

5) apply the attached zip

6) apply the UPDATE-SuperSU-v1.51.zip

7) restart, and you're done!

File Links:

download modified JWR66Y OTA update zip from here:

http://ul.to/8x5nkwwl

( modified.1b0ac7dfb2907e5981f1af24b9e5b005712bd4ee.signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip )

download supersu 1.51 from here:

http://download.chainfire.eu/345/

Hope, this helps!
[Samsung Galaxy Nexus] alanbrenton:
Thanks for confirming.

I had exactly the same problem with the JWR66Y update with the Android Character in the background and a red triangle in the foreground.

I've flashed the stock boot and system images from the JWR66Y ROM I got directly from Google:

https://developers.google.com/android/nexus/images?hl=pt-BR#yakjujwr66y

After flashing both, I checked and the build number is now JWR66Y. I actually though that I had to check for the OTA update but since I'm such a newbie, I never though that flashing both will give me the JWR66Y build. :)

Going forward, if Google still supports the Galaxy Nexus, will I be able to receive future OTA updates?
[Samsung Galaxy Nexus] NCguy:
I had the same problem and the same result with the 4.3Y update. After the OTA failed I was just getting ready to do the manual update and I noticed that the OTA showed up again automatically and so did an update to superSU. I believe the superSU is version 1.55. SuperSU said that it was updated for 4.3 and OTA survival mode.

So I backed everything up, ran the superSU update, turned on OTA survival mode in superSU, and then ran the 4.3 update OTA that was once again queued on the phone. This time it seemed to update without a glitch and I retained root after the update.

So if you have a stock, rooted with superSU galaxy nexus, at this point it certainly does look like future OTAs will work just fine:)
[Samsung Galaxy Nexus] efrant:
Yes. However, you may want to flash the stock recovery from JWR66Y if you are using an older stock recovery just to be sure. If you use a custom recovery, just leave it.
[Samsung Galaxy Nexus] alanbrenton:
Sweet. I'll do that (flash the recovery.img). It won't wipe out my apps or data, will it?

Thanks so much efrant! :)
[Samsung Galaxy Nexus] efrant:
Nope, won't wipe anything.
[Samsung Galaxy Nexus] pilotn:
recovery missing

i got 66y ota but i missed key to avoid system recovery flash and now i have this problem.

phone works fine i've keep root with supersu survivor mode, but if i try to go into recovery i got only robot with red triangle and the only way to go on is pull out battery.

bootloader is unlocked (thanks bootunloader)

It seems is missing recovery, how to push it again?

thanks
[Samsung Galaxy Nexus] -Jesco-:
just flash your custom recovery again
[Samsung Galaxy Nexus] gialakias:
Well if you have root just use rommanager or goomanager to flash cwm or twrp automatically or download the recovery you want from their sites in image format and flash them with flashify or recovery tools from play store .
[Samsung Galaxy Nexus] pilotn:
I see

But i don't know how without have possibility to go into recovery

May you please give me instructions how to do it?
[Samsung Galaxy Nexus] efrant:
Either:

1) reboot into the bootloader, plug into pc, and use: fastboot flash recovery name-of-recovery.img

Or

2) download ROM Manager (CWM) or Goo Manager (TWRP) from the Play store and use them to flash recovery.
[Samsung Galaxy Nexus] pilotn:
i tried both but did not work

when i boot into recovery comes red triangle and with double click power and volume up comes stock recovery.

Both method gives no error answer is ok but no customer recovery.

i tried nandroid manager too with the same result.

any suggestion?
[Samsung Galaxy Nexus] efrant:
Flash CWM or TWRP in fastboot. Do NOT boot into Android, just boot directly into recovery right after flashing. Then flash a superuser zip if you want. Reason why you are booting into the stock recovery has been explained before (maybe read the 101 stickied thread).
[Samsung Galaxy Nexus] pilotn:
got it!!

thanks again and sorry for my noob question
[Samsung Galaxy Nexus] Psycho_TwM:
Still doesn't work for me. The zip is installed OK, but I still view the info has JWR66V
[Samsung Galaxy Nexus] Xenograph:
That's strange!

Shouldn't have happened, as it worked for me. Otherwise I wouldn't have posted here.

In the other thread ( http://xdaforums.com/showthread.php?t=2414147&page=10 ) people suggest a reload right after applying the update, and before installing superSu again.

Maybe this helps?

Because of the Checks removed from the updater-script, you should be able to re-run the update. This shouldn't do any harm, but I suggest to do a full backup first.
[Samsung Galaxy Nexus] vikdal:
Worked like a charm :)

Thanks !

---------- Post added at 10:03 AM ---------- Previous post was at 09:55 AM ----------

Did you clear /cache before installing. I had to do it' otherwise the update wouldn't apply.

I did this:

1. reboot into recovery

2. clear /cache

3. flash modified .zip

4. flash superSU .zip

5. reboot
[Samsung Galaxy Nexus] Psycho_TwM:
Guess I'll be without JWR66Y unless I do a full wipe. I did it in that order and still nothing, the update it's installed, but I still see it as JWR66V. I tried clearing dalvik cache, even reboot without installing supersu and nothing happend. I only have CWM, SuperSU and XLouder.

Thanks anyway for the help!
[Samsung Galaxy Nexus] efrant:
Boot into fastboot and flash the JWR66Y system image. Reboot. Done.

P.S. I believe the reason it's failing is XLouder