There is no difference if installing it manually or over the air. The issue is that Google seems to have paused rolling out 4.0.4 for the time being.
Does anyone have the build img for this:
I'm trying to get my phone back to stock settings to return and so far I have this:
Baseband (Android 4.0.2):
I9250UGLA4
Kernel:
3.0.8-gaaa2611
android-build@apa28#1
Build Number:
ICL53F
I'm trying to get the Build Number to match the image I attached exactly by having the .I9250UGLA4 at the end.
Any help is greatly appreciated.
I'm trying to get my phone back to stock settings to return and so far I have this:
Baseband (Android 4.0.2):
I9250UGLA4
Kernel:
3.0.8-gaaa2611
android-build@apa28#1
Build Number:
ICL53F
I'm trying to get the Build Number to match the image I attached exactly by having the .I9250UGLA4 at the end.
Any help is greatly appreciated.
First post updated with link for IMM76I update. Thanks darkwhite2012: http://xdaforums.com/showpost.php?p=25109532&postcount=8 !!!!
Last edited:
Does this update feature a new radio? I think I've finally narrowed down my poor signal problem: crappy Samsung radio firmware.
Does this update have any positive effect on either poor signal or loss of signal in sleep mode?
Sent from my Galaxy Nexus using Tapatalk 2
Does this update have any positive effect on either poor signal or loss of signal in sleep mode?
Sent from my Galaxy Nexus using Tapatalk 2
So what does that update actually fix that was broken?
Sent from my Galaxy Nexus using Tapatalk 2
It's very difficult to tell. We get an updated kernel and a bunch of patches to various files.
Try it and see if it helps you with your issues. If you don't like it, flash back to your nandroid.
M
mudferret
Guest
Even at that, the boot.img is a patch, although maybe it's an essential tweak.
I may learn myself how to unpack boot.img's later, but that would require a high degree of boredom. http://xdaforums.com/showthread.php?t=443994
Hopefully someone figures out what, if anything, significant is different.
Not sure if it is the placebo effect, but it seems to have fixed a major issue I had prior to the update: when I swipe my finger across the screen, it seems like it now leaves less of a grease mark than before... or maybe that is just due to me washing my hands as my GNex was updating...
M
mudferret
Guest
Not sure if it is the placebo effect, but it seems to have fixed a major issue I had prior to the update: when I swipe my finger across the screen, it seems like it now leaves less of a grease mark than before... or maybe that is just due to me washing my hands as my GNex was updating...
That alone is worth me going back to stock
Not sure if it is the placebo effect, but it seems to have fixed a major issue I had prior to the update: when I swipe my finger across the screen, it seems like it now leaves less of a grease mark than before... or maybe that is just due to me washing my hands as my GNex was updating...
Epic!
I have added the info for IMM76I to the I9250 page at http://www.randomphantasmagoria.com.
Sent from my Xoom using Tapatalk 2
Sent from my Xoom using Tapatalk 2
Your site loads super fast on a mobile device. Awesome!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah I need to make it so the tables don't overlap the right side though. Only an issue in portrait mode. I'll get around to it one day lol
Sent from my Xoom using Tapatalk 2
Sent from my Xoom using Tapatalk 2
Radio?
I'm using a UGLA4 radio rather than the XXLA2 that comes with the Yakju 4.0.4 image. Would I need to change back to XXLA2 for the OTA update to apply properly, or can I stay with UGLA4?
I know that the OTA doesn't include a radio, but I was wondering if it checks each and every file in the system before applying an update...
I'm using a UGLA4 radio rather than the XXLA2 that comes with the Yakju 4.0.4 image. Would I need to change back to XXLA2 for the OTA update to apply properly, or can I stay with UGLA4?
I know that the OTA doesn't include a radio, but I was wondering if it checks each and every file in the system before applying an update...
Not sure if it is the placebo effect, but it seems to have fixed a major issue I had prior to the update: when I swipe my finger across the screen, it seems like it now leaves less of a grease mark than before... or maybe that is just due to me washing my hands as my GNex was updating...
I flashed it and I swear it made the textured back plate spikier!! We need a dev to give us a setting for back plate texture. After all, this code has to make it into AOSP eventually right??
Sent from my Xoom using Tapatalk 2
No, you will be fine. I went through the updater-script file, and this update does not check the radio. You do need to be on the stock kernel though.
Sorry for the Noob Question
Hi Guys
what is the difference between
IMM76D Vs ITL41F Vs ITL41D
my build is ICL53F so which one i should pick ?
P.S. i tried to search but no luck
Hi Guys
what is the difference between
IMM76D Vs ITL41F Vs ITL41D
my build is ICL53F so which one i should pick ?
P.S. i tried to search but no luck
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
253[REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JWR66Y / 4.3
Edit: As of 02 Apr 2012, this thread is applicable to both maguro (GSM/HSPA) and toro (Verizon CDMA/LTE) devices. Although I've also provided links for toroplus (Sprint CDMA/LTE) devices, I have not verified any of the flashing instructions for that device.
Ok, this post is a compilation of all the OTA update URLs that I have seen. (I'll add any other ones posted in this thread to the first post.) Latest are highlighted in green (JB) or red (ICS).
These are incremental updates, not full ROMs. They are EXACTLY the same files that get pushed to your device after you accept the OTA notification that you receive. The difference is, in 99% of the cases, they will be available here before you will get it pushed to your device.
In order for these updates to install, you need at least one of the following: an unlocked bootloader OR a custom recovery OR root.
For the n00bs, please read the entire second post before attempting to update.
The links below are the original update URLs. That said, in case some of them have been pulled and the link is not working, oldblue910 has provided a mirror on his site: Random Phantasmagoria for the yakju/takju/mysid/mysidspr updates.
HOW TO HELP OTHERS
If you have received the OTA update notification, help everyone else out by posting the link. Here is how to do it.*
Or you can trying looking in the log files in /cache to see if you can see a file name ending in .zip.
Here is the list:
(For an explanation of the build codes, see here.)
takju
- takju JWR66Y from JWR66V: http://android.clients.google.com/p....signed-takju-JWR66Y-from-JWR66V.8069c140.zip
- takju JWR66Y from JDQ39: http://android.clients.google.com/p...c.signed-takju-JWR66Y-from-JDQ39.a00dd838.zip
- takju JWR66V from JDQ39: http://android.clients.google.com/p...9.signed-takju-JWR66V-from-JDQ39.cda87c8b.zip
- takju JDQ39 from JOP40D: http://android.clients.google.com/p...3.signed-takju-JDQ39-from-JOP40D.472aafeb.zip
- takju JDQ39 from JOP40C: http://android.clients.google.com/p...4.signed-takju-JDQ39-from-JOP40C.2f05d8dc.zip
- takju JDQ39 from JZO54K: http://android.clients.google.com/p...a.signed-takju-JDQ39-from-JZO54K.bad0f705.zip
- takju JDQ39 from JRO03C: http://android.clients.google.com/p...7.signed-takju-JDQ39-from-JRO03C.444e0791.zip
- takju JOP40D from JOP40C: http://android.clients.google.com/p....signed-takju-JOP40D-from-JOP40C.1d62212b.zip
- takju JOP40C from JZO54K: http://android.clients.google.com/p....signed-takju-JOP40C-from-JZO54K.e587de13.zip
- takju JZO54K from JRO03C: http://android.clients.google.com/p....signed-takju-JZO54K-from-JRO03C.06fa1976.zip
- takju JRO03C from JRN84D: http://android.clients.google.com/p....signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
- takju JRO03C from IMM76I: http://android.clients.google.com/p....signed-takju-JRO03C-from-IMM76I.5c416e9c.zip
- takju JRO03C from IMM30D: http://android.clients.google.com/p....signed-takju-JRO03C-from-IMM30D.5417aa8f.zip
- takju JRN84D from IMM30D: http://android.clients.google.com/p....signed-takju-JRN84D-from-IMM30D.5a07884d.zip
- takju IMM76I from IMM30D: http://android.clients.google.com/p....signed-takju-IMM76I-from-IMM30D.ca99f23d.zip
yakju
- yakju JWR66Y from JWR66V: http://android.clients.google.com/p....signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip
- yakju JWR66Y from JDQ39: http://android.clients.google.com/p...1.signed-yakju-JWR66Y-from-JDQ39.0de35707.zip
- yakju JWR66Y from JOP40D: http://android.clients.google.com/p....signed-yakju-JWR66Y-from-JOP40D.0ad0b769.zip
- yakju JWR66V from JDQ39: http://android.clients.google.com/p...b.signed-yakju-JWR66V-from-JDQ39.6c7ff815.zip
- yakju JWR66V from JOP40D: http://android.clients.google.com/p....signed-yakju-JWR66V-from-JOP40D.83c30f87.zip
- yakju JDQ39 from JOP40D: http://android.clients.google.com/p...b.signed-yakju-JDQ39-from-JOP40D.07501b11.zip
- yakju JDQ39 from JOP40C: http://android.clients.google.com/p...f.signed-yakju-JDQ39-from-JOP40C.68b0bc9a.zip
- yakju JDQ39 from JZO54K: http://android.clients.google.com/p...f.signed-yakju-JDQ39-from-JZO54K.f0c08c6a.zip
- yakju JDQ39 from JRO03C: http://android.clients.google.com/p...d.signed-yakju-JDQ39-from-JRO03C.74c5d360.zip
- yakju JOP40D from JOP40C: http://android.clients.google.com/p....signed-yakju-JOP40D-from-JOP40C.5f67f5ca.zip
- yakju JOP40C from JZO54K: http://android.clients.google.com/p....signed-yakju-JOP40C-from-JZO54K.fdf06e8d.zip
- yakju JZO54K from JRO03C: http://android.clients.google.com/p....signed-yakju-JZO54K-from-JRO03C.24a9a760.zip
- yakju JRO03C from IMM76K: http://android.clients.google.com/p....signed-yakju-JRO03C-from-IMM76K.3d319cfe.zip
- yakju JRO03C from IMM76I: http://android.clients.google.com/p....signed-yakju-JRO03C-from-IMM76I.f946a412.zip
- yakju IMM76I from IMM76D: http://android.clients.google.com/p....signed-yakju-IMM76I-from-IMM76D.46cf01d3.zip
- yakju IMM76I from ICL53F: http://android.clients.google.com/p....signed-yakju-IMM76I-from-ICL53F.5a81769b.zip
- yakju IMM76D from ICL53F: http://android.clients.google.com/p....signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
- yakju ICL53F from ITL41F v3: http://android.clients.google.com/p....signed-yakju-ICL53F-from-ITL41F.0927b42c.zip
- yakju ICL53F from ITL41F v2: http://android.clients.google.com/p...b2abf3611.signed-yakju-ICL53F-from-ITL41F.zip EDIT: this does the same thing as the earlier update - see here.
- yakju ICL53F from ITL41F v1: http://android.clients.google.com/p....signed-yakju-ICL53F-from-ITL41F.1955a56d.zip
- yakju ICL53F from ITL41D: http://android.clients.google.com/p....signed-yakju-ICL53F-from-ITL41D.2c357cd3.zip
- yakju ITL41F from ITL41D: http://android.clients.google.com/p....signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
- yakju ITL41F from ITL35B: http://android.clients.google.com/p...b74c962e.signed-yakju-ota-228551.2ef5b74c.zip
mysid <== for toro (Verizon) devices only
- mysid JDQ39 from JRO03O: http://android.clients.google.com/p...6.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip.
- mysid JRO03O from IMM76Q: http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76Q.4a91da6c.zip.
- mysid JRO03O from IMM76K: http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76K.60fc8084.zip.
- mysid IMM76Q from IMM76K: http://android.clients.google.com/p....signed-mysid-IMM76Q-from-IMM76K.b91e5f74.zip. Note: From what we can tell, this update does nothing besides disable local search from the search bar. See here.
- mysid IMM76K from ICL53F: http://android.clients.google.com/p....signed-mysid-IMM76K-from-ICL53F.12f767e7.zip OR http://android.clients.google.com/packages/ota/verizon_prime/12f767e7a5d0.incremental.zip (both files are identical)
- mysid IMM30B from ICL53F: http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip Note: this is a leaked build.
- mysid ICL53F from ITL41D: http://android.clients.google.com/p....signed-mysid-ICL53F-from-ITL41D.5f0ed49e.zip
mysidspr <== for toroplus (Sprint) devices only
- mysidspr GJ04 from GA02: http://android.clients.google.com/p...c3a509d1ddd2.update_mysidspr_GA02_to_GJ04.zip
- mysidspr GA02 from FH05: http://android.clients.google.com/p...c5ea6e959840.update_mysidspr_FH05_to_GA02.zip
- mysidspr FH05 from FG01: http://android.clients.google.com/p...7ebe470d64e7.update_mysidspr_FG01_to_FH05.zip
- mysidspr FG01 from FD02: http://android.clients.google.com/p...d9492394aa43.update_mysidspr_FD02_to_FG01.zip
- mysidspr FD02 from FC12: http://android.clients.google.com/p...e54c8e4d8385.update_mysidspr_FC12_to_FD02.zip
yakjuux
- yakjuux JOP40D from JRO03C: http://android.clients.google.com/p...2567b0b3d.update_yakjuux_JRO03C_to_JOP40D.zip
- yakjuux JRO03C from ICL53F: http://android.clients.google.com/p...9f46c0589.update_yakjuux_ICL53F_to_JRO03C.zip
- yakjuux JRO03C from ITL41F: http://android.clients.google.com/p...7fbb476c7.update_yakjuux_ITL41F_to_JRO03C.zip
- yakjuux IMM48: http://android.clients.google.com/p...yakjuux/0ce2bc924e74.update_yakjuux_IMM48.zip. Note: this is a leaked build. As well, this is a full update, so it should update any yakjuux build to IMM48. (NFC features are disabled in this update.)
- yakjuux ICL53F from ITL41F: http://android.clients.google.com/p...160b66b23.update_yakjuux_ITL41F_to_ICL53F.zip. Note: Some users have indicated that this update causes some problems with the Market and with NFC.
- yakjuux ITL41F from ITL41D: http://android.clients.google.com/p...73ab08a37.yakjuux_update_ITL41D_to_ITL41F.zip
yakjuxw
- yakjuxw JOP40D from JRO03C: http://android.clients.google.com/p...xw_JRO03C_I9250XWLH2_to_JOP40D_I9250XWMA2.zip
- yakjuxw JRO03C from IMM76K: http://android.clients.google.com/p...ad6c75080.update_yakjuxw_IMM76K_to_JRO03C.zip
- yakjuxw IMM76K from ICL53F: http://android.clients.google.com/packages/ota/samsung_proxima_yakjuxw/541416aaf554.update_yakjuxw_I9250XWKL2_ICL53F_to_I 9250XWLD2_IMM76K.zip
- yakjuxw ICL53F from ITL41F: http://android.clients.google.com/p...26c617b15.update_yakjuxw_ITL41F_to_ICL53F.zip
yakjusc
- yakjusc JDQ39 from JRO03C: http://android.clients.google.com/p...269414c767.update_yakjusc_JRO03C_to_JDQ39.zip
- yakjusc JRO03C from IMM76K: http://android.clients.google.com/p...6.update_yakjusc_LE3_LK2_IMM76K_to_JRO03C.zip
- yakjusc IMM76K from ICL53F: http://android.clients.google.com/packages/ota/samsung_proxima_yakjusc/299ced9f31ad.update_yakjusc_LA1_LE3_ICL53F_to_IMM7 6K.zip
- yakjusc ICL53F from ITL41D: http://android.clients.google.com/p...c403ff247.update_yakjusc_ITL41D_to_ICL53F.zip
yakjuzs
- yakjuzs JOP40D from JRO03C: http://android.clients.google.com/p...149357f78.update_yakjuzs_JRO03C_to_JOP40D.zip
- yakjuzs JRO03C from IMM76K: http://android.clients.google.com/p...88f024193.update_yakjuzs_IMM76K_to_JRO03C.zip
- yakjuzs IMM76K.I9250ZSLE2 from ICL53F: http://android.clients.google.com/packages/ota/samsung_proxima_yakjuzs/6fcb7f53473a.update.zip
- yakjuzs IMM76K.I9250ZSLD1 from ICL53F: http://android.clients.google.com/packages/ota/samsung_proxima_yakjuzs/737637482ddd.update.zip
- yakjuzs ICL53F from ITL41F: http://android.clients.google.com/packages/ota/samsung_proxima_yakjuzs/ebde59914015.update.zip
yakjudv
- yakjudv JWR66Y from JZO54K.I9250TDVLK2: http://android.clients.google.com/p...30cb906cb.update_yakjudv_JZO54K_to_JWR66Y.zip
- yakjudv JZO54K.I9250TDVLK2 from IMM76K.I9250TDVLF2: http://android.clients.google.com/p...d8f7a2a78.update_yakjudv_IMM76K_to_JZO54K.zip
- yakjudv JZO54K.I9250TDVLK2 from IMM76K.I9250TDVLE1: http://android.clients.google.com/p...f57d222c5.update_yakjudv_IMM76K_to_JZO54K.zip
- yakjudv IMM76K.I9250TDVLF2 from ITL41F.I9250TDVKKB: http://android.clients.google.com/p...62fc521fd.update_yakjudv_ITL41F_to_IMM76K.zip
- yakjudv IMM76K.I9250TDVLE1 from ITL41F.I9250TDVKL1: http://android.clients.google.com/packages/ota/samsung_proxima_yakjudv/989a024b1581.update_yakjudv_ITL41F_to_IMM76K_after.zip
yakjukr
- yakjukr JRO03C from IMM76K: http://android.clients.google.com/p...1e0fc82a1.update_yakjukr_IMM76K_to_JRO03C.zip
- yakjukr IMM76K from ICL53F: http://android.clients.google.com/p...1c9a66208.update_yakjukr_ICL53F_to_IMM76K.zip
yakjujp
- yakjujp JRO03C from IMM76K: http://android.clients.google.com/p...0f217714f.update_yakjujp_IMM76K_to_JRO03C.zip
- yakjujp IMM76K from ICL53F: http://android.clients.google.com/p...ebea53bd4.update_yakjujp_ICL53F_to_IMM76K.zip
yakjuvs
- yakjuvs JRO03C from IMM76K: http://android.clients.google.com/p...fb0395674.update_yakjuvs_IMM76K_to_JRO03C.zip
- yakjuvs IMM76K from ICL53F: http://android.clients.google.com/p...uvs/bcb4d701d155.yakjuvs_ICL53F_to_IMM76K.zip
- yakjuxe JOP40D from JRO03C: http://android.clients.google.com/p...d7d4ef75e.update_yakjuxe_JRO03C_to_JOP40D.zip
- yakjuxe JRO03C from IMM76K: http://android.clients.google.com/p...34b6f4cac.update_yakjuxe_IMM76K_to_JRO03C.zip
- yakjuxe ICL53F from ITL41F: http://android.clients.google.com/p...0241630d6.update_yakjuxe_ITL41F_to_ICL53F.zip
mictacea <== for toro (Verizon) devices only
- mictacea IMM76K from IMM76F: http://android.clients.google.com/p...gned-mictacea-IMM76K-from-IMM76F.8ef309b8.zip.
34How to flash
Since there are people who are asking how to flash these, I've written a few step-by-steps on how to flash. (These are not full ROMs - they are OTA updates for specific builds, and will NOT wipe your data. Flashable in recovery. Not un-doable without wiping data.) Again, these are stock updates -- you need a stock ROM to flash these: it cannot be deodexed, it cannot have stock apps missing, it cannot have a modified build.prop file due to some app writing to it, etc. (although root is fine) Edit: as of JWR66N, if you have used Chainfire's SuperSU to root, you must unroot first before trying to update. If you've replaced stock files with custom ones, either replace the stock ones, or go into the update zip file, and remove the assert for the file (although I don't recommend the later, as the update may not patch your custom file properly). If you are missing stock yakju or mysid files, download the factory images from here, extract the system.img from within, convert it to an .ext4.img by using this and then (for Windows users) use this to mount the .ext4.img and extract the file. These files may work in non-yakju builds as well. [/COLOR]
Notes:
1) Methods 2 & 3 assume that you have the correct drivers installed on your computer and your computer recognizes your device.
2) Method 3b assumes that you have busybox already installed on your device.
3) I have not tried method 3a, but it should work (it certainly won't mess anything up).
4) Method 3 can also be done with a terminal emulator on your device instead of using ADB.
5) For those of you that don't know, every OTA update places two files on your system (that are not there on a non-update stock ROM) that re-flash the stock recovery on EVERY boot. The two files are /system/recovery-from-boot.p and /system/etc/install-recovery.sh. You need to make sure that these files are either deleted or renamed, or else CWM will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, if you've recently gotten an OTA and applied it, your CWM is gone... Use something like Root Explorer, delete them, and re-flash your CWM recovery.
6) As with all stock updates from Google, these updates will change the permissions on the su binary so, in effect, you will lose root (for those who have it). Install supercurio's OTA Rootkeeper BEFORE you do all this, or, for those with an unlocked bootloader or CWM installed, just re-flash Chainfire's SuperSU zip file found here in CWM, or manually change the permission via ADB (mount the system and chmod 4755 /system/bin/su) while booted in CWM.
7) For those that have flashed a different radio from what was supplied in the Google stock images, you either have to flash back the original radio before the update, or remove the assert and the patch/flash lines from the updater-script file in the update zip and remove the radio image or patch (if there is one). The later should only be done by advanced users who understand what I just said.
8) CDMA/LTE users: I have made note of the differences for any of the methods.
9) Non-yakju builds are updated MUCH later (i.e., weeks to months) than yakju, so if you are running a non-yakju build and are expecting an update shortly after the yakju build gets updated, you will be very disappointed.
10) For those methods below that require CWM (including Method 1), do NOT use a CWM 5-series touch version - use the one in the link provided (or use CWM 6.x or TWRP 2.2.x).
Method 1 - CWM 5.5.0.2 or 5.5.0.4 (i.e., NON-touch) recovery installed
EDIT: For those flashing a Jelly Bean update, in order to retain your CWM recovery, use the "revised" Method 1 here by Revoked instead of using the Method 1 below. (The method 1 below will work just fine for JB -- but you will need to re-flash CWM, and rename /system/etc/install-recovery.sh once you are booted.)
1) Download the correct update for your build on to your computer;
2) Open the archive and delete the recovery folder; EDIT: Do NOT do this step if it you are using any Jelly Bean update, i.e., JRN84D or newer.
3) Copy the file to /sdcard on your device;
4) Reboot into CWM;
5) Select "install zip from sdcard";
6) Select "choose zip from sdcard";
7) Select the update the you just copied to your device;
8) Wait until it completes. Reboot. Done.
Method 2 - Stock recovery installed, Unlocked bootloader
1) Download the correct update for your build on to your computer;
2) Copy the file to /sdcard on your device;
3) Download CWM from here and place it on your computer in the same directory as your fastboot binary. For CDMA/LTE devices, use this version;
4) Rename the CWM image to cwm.img
5) Reboot into fastboot mode;
6) Open a command prompt in the same directory;
7) Type fastboot devices to make sure your device is recognized;
8) Type fastboot boot cwm.img
9) Select "install zip from sdcard";
10) Select "choose zip from sdcard";
11) Select the update the you just copied to your device;
12) Wait until it completes. Reboot. Done.
Method 3a - Stock recovery installed, Locked bootloader, with root; -- No longer works if you are updating from JRN84D or newer.
1) Download the correct update for your build and place it in /sdcard;
2) Open a command prompt in the same directory as your ADB binary;
3) Type adb devices to make sure that your device is recognized;
4) Type adb shell
5) Type su
6) Type cat /sdcard/name-of-zip-here.zip > /cache/name-of-zip-here.zip
7) Type exit
8) Type exit
9) Reboot into recovery;
10) Briefly hold the power button and then quickly press volume up;
11) Select apply update or whatever the menu item is (I don't have a stock recovery installed, but it should be easy to identify);
12) Wait until it completes. Reboot. Done.
Method 3b - Stock recovery installed, Locked bootloader, with root (use this method only if you have to -- use 3a or 3c first);
1) Download the correct update for your build and place it in /sdcard;
2) Download CWM from here (CDMA/LTE devices, use this version) and place it in /sdcard;
3) Rename the CWM image to cwm.img;
4) Open a command prompt in the same directory as your ADB binary;
5) Type adb devices to make sure that your device is recognized;
6) Type adb shell
8) Type su
9) Type dd if=/data/media/cwm.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
10) Type exit
11) Type exit
12) Reboot into recovery;
13) Select "install zip from sdcard";
14) Select "choose zip from sdcard";
15) Select the update the you just copied to your device;
16) Wait until it completes. Reboot. Done.
Method 3c - Stock recovery installed, Locked bootloader, with root;
1) Install ROM Manager from the market;
2) Flash CWM using ROM Manager;
3) Reboot into CWM;
4) Select "install zip from sdcard";
5) Select "choose zip from sdcard";
6) Select the update the you just copied to your device;
7) Wait until it completes. Reboot. Done.
Method 4a - Stock recovery installed, Locked bootloader, no root;
On JRN84D and newer ONLY: walkamake has confirmed that you can apply updates with a locked bootloader, no root and no custom recovery. (See his post here.) This is due to a new, updated stock recovery in JRN84D and newer builds.
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the "!";
2) Access the stock recovery menu by pressing power and volume up;
3) Select "Apply update from ADB";
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Method 4b - Stock recovery installed, Locked bootloader, no root;
On JRN84D and newer ONLY: kupuguy has confirmed that you can apply updates with a locked bootloader, no root, no custom recovery and no ADB, assuming you have an OTG cable. (See his post here.) This is due to a new, updated stock recovery in JRN84D and newer builds.
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the "!");
2) Access the stock recovery menu by pressing power and volume up;
3) Copy the update onto the root folder of a USB stick.
4) Connect the USB stick to the phone using a USB OTG cable
5) Select "Apply update from USB"
6) Reboot. Done.
On builds older than JRN84D: You need to either: 1) root or 2) unlock your bootloader or 3) wait until you get the update pushed to you OTA.
Follow the steps here to root without unlocking your bootloader. Then you can follow method 3a or 3c above.
Method 5 -- unlocked bootloader required
We've recently uncovered that, if the factory images are available, an easy way to update is to flash all the images EXCEPT the userdata image. All of your data will still be intact, including all installed apps and settings, and everything in /sdcard. Essentially, it is identical to upgrading via an OTA update. Follow the instructions here.21OTA 4.1.2 yakju JZO54K-from-JRO03C
http://android.clients.google.com/p....signed-yakju-JZO54K-from-JRO03C.24a9a760.zip
14Succesfull patch instructions
I just succesfully updated my gnex using Touch CWM (5.8.0.2) without losing recovery!
Please note this requires stock IMM76I except for recovery. You can achieve this by flashing the 4.0.4 factory image (don't forget to remove the recovery).
Here is my edited Method 1 install procedure:
Method 1 - CWM recovery installed
1) Download the correct update for your build on to your computer;
2) Open the archive;
3) Delete recovery folder;
4) Go to folder - META-INF/com/google/android
5) Extract updater-script with Winzip
6) Open the extracted updater-script with Notepad++ (NOT regular notepad or wordpad)
7) Remove the line saying: set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
8) Save and move the new updater-script to the folder in the zip file (META-INF/com/google/android)
9) Copy the zip file to /sdcard on your device;
10) Reboot into CWM;
11) Select "install zip from sdcard";
12) Select "choose zip from sdcard";
13) Select the update the you just copied to your device;
14) Wait until it completes. Reboot. Done.
