Develop Bugs

[REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JWR66Y / 4.3

[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
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.

How 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.

FAQs
I'm temporarily placing THE Frequently Asked Question here:
Question: I got the update OTA update notification, I accepted it and it started to install. But then it stopped, and all I see is the android laying on its back with the red triangle and exclamation point. Whaz wit dat???
Answer:
1) First of all, this thread is not about having the OTA install automatically when you receive it. It is about manually applying it from one of the files posted in this thread. (In order for the update to install automatically OTA, you need to have the stock recovery installed. Not CWM. Not the stock recovery from any build -- the stock recovery from the ROM you are currently running.)
2) The android laying on its back with the red triangle and exclamation point IS NOT AN ERROR. It is the main screen of the stock recovery. (If you want to see the menu, when you are on that screen press power and volume up.)
3) If you are not stock, don't bother asking why the update didn't install. I think I've covered that enough. You need the stock kernel (boot image), the stock radio and ALL the stock system files (yes, all the ringtones, all the wallpapers, etc., ALL THE FILES) UNMODIFIED, otherwise the update will not work. (Having extra files will not make a difference, like having root files).
4) If you have installed busybox in /system/bin, then it over wrote some stock files. This has been covered in this thread. Read and fix it.
5) If you want to use a CWM touch-based recovery instead of a non-touch recovery, then don't bother asking any questions as to why the update won't install. I will not provide support any longer for those using touch recoveries. All non-touch CWM (5.5 and newer) recoveries, and all TWRP (2.2.x and newer) recoveries should work fine.
6) If you've flashed your device to stock using a toolkit, flash it using a manual method (like this one or one of the many others). I will not provide support if you have used a toolkit -- ask in the toolkit thread.

Thanks
EthanFirst
diffra & oldblue910
shakalaca
bigfoot1942
switch85
burnedx420
TheManii
PitBeast
osm0sis
cyclonemon
motopig
El Madhatter & oldblue910
Dolphin Trainer
ogre_x
gokpog
dmapr
Snowknight26
tochiba
tienhn
X1iser
kibmcz
Rican7
wallyg8r
cyclonemon
dark vertical
oldblue910
ffosilva
iil
TWiTCommander
foxgalaxy
lostinbeta
mbirth
hallerlaller
ladios
dnlsmy
t2dc
phone_user
cj10488
id2
krazie1
hoodred
chris5582
darkwhite2012
adrynalyne
roriii
cgrunner
phazerorg
g.kohei
k_myk
bfroehlich
jei13
jeff72k

Thank you
Sent from my Galaxy Nexus using xda premium

Hi efrant,
Thank you for the info. Let me ask you: can we say, if all three urls are from google.com, that yakjuux and yakju come directly from Google?
Thank you in advance.
Obs. English is not my native language.

tigajr said:
Hi efrant,
Thank you for the info. Let me ask you: can we say, if all three urls are from google.com, that yakjuux and yakju come directly from Google?
Thank you in advance.
Obs. English is not my native language.
Click to expand...
Click to collapse
OTA updates for all builds are pushed from Google's servers. Period. Having said that, the non-yakju builds will likely need to get reviewed by Samsung before they are pushed, which will cause a bit of a delay.

So how would I install this on my phone?

How to install? Recovery mode only shows an Android with open stomach and a red exclamation mark. Do I need further software?
Sent from my Galaxy Nexus using XDA App

efrant said:
Alright, given that I haven't seen this anywhere, I figured I'd start a thread to compile a list of all the OTA update URLs.
I'll start off with the ones that I have, and I'll add any other ones posted in this thread to the first post.
yakju
yakju ICK53F from ITL41F: http://android.clients.google.com/p....signed-yakju-ICL53F-from-ITL41F.1955a56d.zip
Click to expand...
Click to collapse
Do we need all of these? Are these incremental updates or mirrors? Is this the most recent one if so? Finally, just flash as "update.zip" correct? Thanks in advance.

jmwein said:
So how would I install this on my phone?
Click to expand...
Click to collapse
Updated the first post.
tonarm said:
How to install? Recovery mode only shows an Android with open stomach and a red exclamation mark. Do I need further software?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Updated the first post.
system6 said:
Do we need all of these? Are these incremental updates or mirrors? Is this the most recent one if so? Finally, just flash as "update.zip" correct? Thanks in advance.
Click to expand...
Click to collapse
These are incremental updates. You need to chose the correct one for your build. For example, if you are on yakju ITL41D, then you would need to apply both yakju ITL41F from ITL41D and yakju ICL53F from ITL41F if you want to go to ICL53F.

So just to confirm, you need to be rooted in order for any of these methods to work, right?

jmwein said:
So just to confirm, you need to be rooted in order for any of these methods to work, right?
Click to expand...
Click to collapse
No you do not.
You need one of the following:
CWM installed;
root;
unlocked bootloader;

hey, I've got a Nexus with ITL41F.
So I've downloaded the correct file, deleted the recovery folder in the zip file and put it onto the phone.
Now I've booted it to cwm and want to install the zip.
But I become the android with the red exclamation mark. It doesn't update.
Do you know, why?

FormelLMS said:
hey, I've got a Nexus with ITL41F.
So I've downloaded the correct file, deleted the recovery folder in the zip file and put it onto the phone.
Now I've booted it to cwm and want to install the zip.
But I become the android with the red exclamation mark. It doesn't update.
Do you know, why?
Click to expand...
Click to collapse
Are you sure you have CWM installed?

Ahm, yes, really.

FormelLMS said:
Ahm, yes, really.
Click to expand...
Click to collapse
Try either leaving the recovery folder in then, or toggling assert checks in CWM.

Hm, still the same. Very strange.
Have you updated your phone with this files?

FormelLMS said:
Hm, still the same. Very strange.
Have you updated your phone with this files?
Click to expand...
Click to collapse
Yes I have.
Let me ask you a question: forget about the update. Just boot into CWM. Does it work fine?

yes, this works fine. Updating the Radio via cwm works good.

[FAQ]Installing Verizon 4.0.4 OTA, Rooting, Etc.

There are many questions, and they are all being answered. That said, they are spread across 34324123213132 threads. So lets create a thread where they are all asked in one place.
Q: Where do I get it?
A: The mods refused to sticky this most valuable thread for me, but you can find it here:
http://forum.xda-developers.com/showthread.php?t=1482650
Make sure you get the right one.
Q: Where is the changelog?
A: This is not official yet. Hence, no official changelog. There is an unofficial one here by kangxi:
http://forum.xda-developers.com/showthread.php?t=1481044
Q: Can I install the 4.0.4 OTA over 4.0.3?
A: Of course not. It only updates stock 4.0.2. That means you must return to stock 4.0.2 to flash it, or use some packaged rom from the developer forum that is at 4.0.4.
Q: I keep getting an error 7 when trying to flash. What am I doing wrong?
A: You are not stock 4.0.2 and a patch check or assert is failing. If the file it fails on is mentioned, you can replace that file with a stock version and cross your fingers. Or you can remove the patch check and installation from the installer-script in the ota zip. Of course, then you must use clockwork recovery or the likes to install. Also, make sure your recovery (if non-stock) is up to date.
Q: Do I need to be rooted to install this update?
A: Not entirely. You must be unlocked, but you can then temp boot an adb rooted kernel and place the update in /cache. When you reboot to stock recovery, you are unrooted and back to stock. That leads into how (there are a few ways).
Recommended:
Code:
Download the pre-rooted 4.0.2 kernel:
[url]http://www.box.com/s/xf6bz8f1j004bk0zc78a[/url]
Enable usb debugging
adb reboot bootloader
fastboot boot newboot.img
---once back up----
adb remount
adb push 659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip /cache
adb reboot recovery
install from cache
choose the ota zip.
flash
Alternative method from williamthegoat:
Code:
Enable usb debugging
Put ota update on your sdcard
Temporary boot clockwork recovery. I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
adb reboot bootloader
fastboot boot recoveryimagename.img (use the correct name)
---once in recovery---
Flash ota.
Note: this method contains no signature checking for the ota to verify its validity.
Q: Will this break root?
A: Yup.
Q: How do I root again after the update?
A: You need to install clockwork mod recovery.
I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
Also grab the pre-rooted 4.0.4 kernel from here:
[url]http://www.box.com/s/dh5b2vjg13qm2uodfysk[/url]
To install clockwork (permanent) and flash Superuser:
adb reboot bootloader
fastboot boot 404boot.img
--once back up---
adb remount
adb shell
mv system/etc/install-recovery.sh system/etc/install-recovery.bak
adb reboot bootloader
fastboot flash recovery recoveryimagename.img (use the correct name)
fastboot reboot
---once back up---
adb reboot recovery
flash su.zip
To install Superuser temporarily and flash Superuser:
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
adb reboot bootloader
fastboot boot recoveryimgname.img (use the correct name)
---once in recovery---
flash su.zip
Q: I am on xxx's aosp rom? How do I update?
A: Go back to 4.0.2 stock or use one of the prepackaged, precompiled roms in the dev section. At this time, 4.0.4 is not on the aosp repos.
Q: What about GSM users?
A: I am sure they will see it soon, if not by ota, then by aosp.
More will come as I see them needing to be answered.

confused
how can i get here from AOKP......? LULZ

adrynalyne, why didn't you predict my <insert user error here> ?
Sorry, I had to get in before the flood of "you broke my phonez!!" posts.

Thanks guys. Always nice to have input from the IRC crowd

Will this work on my Charge?

Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?

sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
What I posted, works 100%.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
adrynalyne hacked a new version that works on 4.0.4.

matt30 said:
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
It will still receive updates from the market as well.

matt30 said:
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
Cool, thanks.

Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?

Se7enLC said:
Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?
Click to expand...
Click to collapse
Nope. Its exactly what I meant. There is gui root, via Superuser, and there is adb root, via kernel.

I updated by unlocking, temp booting CWM, and updating through there. Either way works

williamthegoat said:
I updated by unlocking, temp booting CWM, and updating through there. Either way works
Click to expand...
Click to collapse
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.

adrynalyne said:
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.
Click to expand...
Click to collapse
Oh, seriously? Should I go back to 4.0.2 and do it the other way? Does it make a difference? I still want to be getting OTAs and what not.

I wouldn't worry about it. I am just the paranoid type.

I got it to work, but trying to flash the update using the factory recovery would just give me the error with the android belly open with the !. I just moved it to the sd card then and used the alternative method (without verification) and it worked great. Thanks for everything - I really wanted to check this out. We'll see how long I stay on it though.

Thanks for the su file adrynalyne! I flashed it through cwm and it worked like a charm.
Sent from my Galaxy Nexus using xda premium

Can someone please explain this line and what goes in the image name spot?
fastboot boot recoveryimagename.img (use the correct name)
I tried the recommended upgrade and got the same as the person a few posts above "flashed the update using the factory recovery would just give me the error with the android belly open with the !"

following the recommended install way, i too get the android with red exclamation when trying to adb reboot recovery; after pushing the update into /cache.
Any suggestions?

OTA IMM76I from IMM76D cwm problem !!!!!

I have root and un-lock my Galaxy Nexus today and flash IMM76D which is download from Google developer page (https://developers.google.com/android/nexus/images)
after finish all the step and updated to Android 4.0.4 Google official rom, I have received Android 4.0.4 System Update by OTA, and ask me reboot the phone !
after rebooting, Build number is updated to IMM76I. and the Baseband version is I9250XXLA2.
But I can not go into CWM anymore after updated by OTA. that's it is normal case......????????????
why un-root after updated by OTA ???????

Sent from my Galaxy Nexus using Tapatalk 2

Your meant to pull the battery out when your flashing the ROM .. geeeez some people don't read instructions anymore!
Remember! Pull your battery out whilst flashing!

Rename the OEM recovery restore file, reflash CWM recovery, and you should be good to go.
Gnex toolkit should help, if you don't have it already.

hki_peter said:
I have root and un-lock my Galaxy Nexus today and flash IMM76D which is download from Google developer page (https://developers.google.com/android/nexus/images)
after finish all the step and updated to Android 4.0.4 Google official rom, I have received Android 4.0.4 System Update by OTA, and ask me reboot the phone !
after rebooting, Build number is updated to IMM76I. and the Baseband version is I9250XXLA2.
But I can not go into CWM anymore after updated by OTA. that's it is normal case......????????????
why un-root after updated by OTA ???????
Click to expand...
Click to collapse
Everything is in the OTA update instruction thread...
efrant said:
Notes:
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 ChainsDD's Superuser 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.
Click to expand...
Click to collapse

Recovery gets replaced to stock-version up on updating so cwm will need to be re-flashed after...
Sent from my Galaxy Nexus using xda premium

Tjotte said:
Recovery gets replaced to stock-version up on updating so cwm will need to be re-flashed after...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yup. That is in there as well...
efrant said:
Notes:
5) For those of you that don't know, there are two files that re-flash the stock recovery on every boot (/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...
Click to expand...
Click to collapse

zeekiz said:
Your meant to pull the battery out when your flashing the ROM .. geeeez some people don't read instructions anymore!
Remember! Pull your battery out whilst flashing!
Click to expand...
Click to collapse
What's the intention here? There's no need for this if you're not helping/explaining. What if he did and brick his phone? Would that make you happy?

[Q] Switching to Android 4.2 from 4.1.2

Hi,
I installed Samsung Galaxy Nexus Toolkit V9.1.0 for GSM to root my device and use Team Win Recovery Project V2.2.2.0 to install ROMs.
Currently on Official nightly build of Cyanogen Mod 10 Rom Android 4.1.2 Build JZO54K.
I want to know if I need to update anything to switch to Android 4.2 ROM or should I just download a good rom and flash it using the software?
While we are on the subject, can someone please recommend a good ROM? When will start getting Cyanogen Mod for Android 4.2?
Thanks.

You should update your recovery to the latest version (either CWM ot TWRP) to avoid nested "0" folders each time you flash a new rom.
Other than that, I didn't do anything else.
By the way, I'm using Cataclysm rom.

abulkhairi said:
Hi,
I installed Samsung Galaxy Nexus Toolkit V9.1.0 for GSM to root my device and use Team Win Recovery Project V2.2.2.0 to install ROMs.
Currently on Official nightly build of Cyanogen Mod 10 Rom Android 4.1.2 Build JZO54K.
I want to know if I need to update anything to switch to Android 4.2 ROM or should I just download a good rom and flash it using the software?
While we are on the subject, can someone please recommend a good ROM? When will start getting Cyanogen Mod for Android 4.2?
Thanks.
Click to expand...
Click to collapse
Just update your TWRP to the latest version 2.3.2.1. You can easily do that via GooManager app which you can find in the Play Store
There is no specific "good" ROM, just try then decide
Good Luck

ahmadallica said:
Just update your TWRP to the latest version 2.3.2.1. You can easily do that via GooManager app which you can find in the Play Store
There is no specific "good" ROM, just try then decide
Good Luck
Click to expand...
Click to collapse
like others have said use the latest twrp... and "best" rom is different for everyone so try them and see for yourself.. and cm10.1 is already out

ahmadallica said:
Just update your TWRP to the latest version 2.3.2.1. You can easily do that via GooManager app which you can find in the Play Store
There is no specific "good" ROM, just try then decide
Good Luck
Click to expand...
Click to collapse
Hi,
I have GooManager installed.... When I search for TWRP 2.3.2.1 I get 2.3.2.3 version shown as available as well. It's a zip and .img file as well. Am I supposed to just download and flash it? I mean the zip file would be flashed using the current TWRP right and it will auto upgrade?
Also, What I understand is that if I have 2.3.2.1 I can install 4.2 ROMs without having to root my phone using Galaxy Nexus Toolkit V10.1 because the screenshots shows 4.2 in it?
Also to find something I have to use search place on GooManager, isnt there a list of updated list of softwares available on it? I can see ROMs etc very neatly can be seen there but not patches like these.

abulkhairi said:
Hi,
I have GooManager installed.... When I search for TWRP 2.3.2.1 I get 2.3.2.3 version shown as available as well. It's a zip and .img file as well. Am I supposed to just download and flash it? I mean the zip file would be flashed using the current TWRP right and it will auto upgrade?
Also, What I understand is that if I have 2.3.2.1 I can install 4.2 ROMs without having to root my phone using Galaxy Nexus Toolkit V10.1 because the screenshots shows 4.2 in it?
Also to find something I have to use search place on GooManager, isnt there a list of updated list of softwares available on it? I can see ROMs etc very neatly can be seen there but not patches like these.
Click to expand...
Click to collapse
Please be careful with the TWRP version as 2.3.2.3 seems to be for Nexus 4 not our GNex. Follow the following steps to download and install latest TWRP for your device (2.3.2.1):
1- Run GooManager app
2- Click on the upper right 3 dots for settings
3- Click "Install OpenRecoveryScript"
4- Confirm Recovery Install --> Yes
5- Confirm download, reboot, and install --> Yes
6- A download process will start then it will be installed
7- (Optional) Reboot into recovery to ensure that TWRP is successfully installed and working.
As far as I know, you need root for GooManager app already for many functions. I never used the GNex toolkit nor have an idea which screenshots you are referring to.
I am not sure I got your last point but if you are searching for ROMs via GooManager then it is there in the first option of the app --> Browse compatible ROMs. But honestly I have never used this so can't share you any experience regarding it.
Hope this helps

[STOCK][C69XX][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB][16/1/2014]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.43 BETA or newer.
Current rooted FW version: 14.1.G.1.534 and 14.1.G.2.257 .
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.71 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.0.290:
If you attempted this before, make sure you delete XZDR.prop from the XZDualRecovery folder to make sure it will not cause a bootloop.
Files:
For C6902: Download C6902_14.2.A.0.290.flashable.zip (Bittorrent: 905MB) and C6902_14.2.A.0.290_Stripped.ftf (21MB)
For C6903: Download C6903_14.2.A.0.290.flashable.zip (Bittorrent: 784MB) and C6903_14.2.A.0.290_Stripped.ftf (21MB)
For C6906: Download C6906_14.2.A.0.290.flashable.zip (Bittorrent: 849MB) and C6906_14.2.A.0.290_Stripped.ftf (21MB)
For C6943: Download C6943_14.2.A.0.290.flashable.zip (Bittorrent: 863MB) and C6943_14.2.A.0.290_Stripped.ftf (21MB)
Save them somewhere you remember;
Put 'C69XX_14.2.A.0.290.flashable.zip' on (the external) SDcard1;
Put 'C69XX_14.2.A.0.290_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Install XZDualRecovery 2.7.74 or newer from PC.
In TWRP -> Wipe -> advanced Wipe Tick/Check:
Dalvik-Cache
System
Cache
Data
Then 'Swipe to Right' to make it happen and go back to the TWRP home screen;
Flash 'C69XX_14.2.A.0.290.flashable.zip' in TWRP (if you have an old C6903 flashable package, be sure to flash the patch from post 2 now!)
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C69XX_14.2.A.0.290_Stripped.ftf';
Now reboot to system;
Once you get to the language select screen, reboot to TWRP (no need to finish the guide);
Restore the backup of DATA only, when done go back to the TWRP home screen;
In TWRP -> Wipe -> advanced Wipe Tick/Check Dalvik-cache;
Reboot to system.
The first boot will be slow and after a long wait at the boot animation you will see Android start optimizing the apps on your phone.
Video Guide:
NOTE: This guide is based on an older guide which has since been updated a few times, but it will give you a general idea.
shem2409 said:
Click to expand...
Click to collapse
Enjoy! :laugh:
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][C69XX][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB][16/1/2014], a ROM for the Sony Xperia Z1
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.1.G.1.534 and 14.1.G.2.257
Based On: STOCK
Version Information
Status: Beta
Current Beta Version: 16/1/2014
Beta Release Date: 2014-01-16
Created 2013-12-19
Last Updated 2014-01-16

ROM Patches
For those who have this ROM installed or downloaded with the mutilated root and 40 second reboot bug in recovery or have it installed with a semi-root situation:
C6903_14.2.A.0.290.patch.zip (8.9MB)
Follow the ROM flash guide in the OP and flash the patch right after flashing the ROM zip.
This will patch your ROM release to have XZDualRecovery BETA (2.7.71). It will patch/fix root as well. It should be small enough to quickly flash using TWRP, as long as you do it right after entering it.

FAQ & Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this guide ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6903_14.1.G.1.534_[NUT].ftf (Bittorrent: 770MB) and flash it using FlashTool. I've also added the FTF to the downloads page on the DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .534 without loss of your IMEI :good:
Thanks to @mharckk and @MohammadAG for the workaround which contributed to the creation of this FTF.

About to download and flash now.

I'll do a deodex package for this ROM tomorrow, it's late now

How did u get FULL ROOT dude?

jackie099 said:
How did u get FULL ROOT dude?
Click to expand...
Click to collapse
Please remove the OP quote from your post, thanks
If you have an earlier version to update from, which has been rooted and has recovery, it's not hard to do

Big hugs man. Thanks. Much appreciated!!!
Sent from my C6903 using XDA Premium 4 mobile app

Hey Man, Good Job. Is this update tweeked to instal apps data to external memory by default?

eclyptos said:
Hey Man, Good Job. Is this update tweeked to instal apps data to external memory by default?
Click to expand...
Click to collapse
Nope, This is really a rooted stock rom with recovery, what you do to it after installing it is entirely up to you

[NUT] said:
Nope, This is really a rooted stock rom with recovery, what you do to it after installing it is entirely up to you
Click to expand...
Click to collapse
The root is not working on 4.3 until now. Is it? Even after flashing supersu on a unlocked bootloader we get partially rooted system partition. The busybox is not working either.

Can u upload it not in torrent? Thankyou
Gesendet von meinem C6903 mit Tapatalk

Sumedha Kapoor said:
The root is not working on 4.3 until now. Is it? Even after flashing supersu on a unlocked bootloader we get partially rooted system partition. The busybox is not working either.
Click to expand...
Click to collapse
On 4.3 SuperSU is to be daemonized, which means it gets turned in to a service. This ROM does that.
On the 4.3 Journalists & Commercial release for the XZ and ZL the root method I used is working flawlessly now Initially on these releases I made a booboo, which I fixed with an update package. The cause for the need of this fix has been removed before building this package, it should be properly rooted and working OK
Remember, Recovery has been integrated, which will work just as well even if root would still bugger out, so then I will find a solution and make it work in the end, if needed

[NUT] said:
On 4.3 SuperSU is to be daemonized, which means it gets turned in to a service. This ROM does that.
On the 4.3 Journalists & Commercial release for the XZ and ZL the root method I used is working flawlessly now Initially on these releases I made a booboo, which I fixed with an update package. The cause for the need of this fix has been removed before building this package, it should be properly rooted and working OK
Remember, Recovery has been integrated, which will work just as well even if root would still bugger out, so then I will find a solution and make it work in the end, if needed
Click to expand...
Click to collapse
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.

Sumedha Kapoor said:
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.
Click to expand...
Click to collapse
+1

Sumedha Kapoor said:
Can you send me a flashable zip with the recovery and this rooting method that you mentioned above? I have a deodexed, zipaligned, rooted, busyboxed, tweaked and debloated purely stock rom. I will see if I could fix the partial root in it. Plus it would be easier for me and others who already have a rom to fix their issues with it. Thanks.
Click to expand...
Click to collapse
Lets see what people's experiences are with the existing package, once confirmed working, I will release the base zip for devs to use

Do we have to flash the ftf after flashing the zip or can we just flash the zip? Also, after successfully flashing, do we have to backup TA partition, unlock bootloader, then restore or since Sony fixed it can we just unlock without restoring TA?

TheKnux said:
Do we have to flash the ftf after flashing the zip or can we just flash the zip? Also, after successfully flashing, do we have to backup TA partition, unlock bootloader, then restore or since Sony fixed it can we just unlock without restoring TA?
Click to expand...
Click to collapse
It's a stock ROM, so unlocking is not required. But if you had an unlocked bootloader, restoring it first might be wise.
Just stick to the flash order in the guide, that should be fine.

[NUT] said:
It's a stock ROM, so unlocking is not required. But if you had an unlocked bootloader, restoring it first might be wise.
Just stick to the flash order in the guide, that should be fine.
Click to expand...
Click to collapse
Will do. Now that the BL unlock is fixed theres no reason not to unlock it, that's why I asked. The more I do to it, the merrier.

If i have already updated to official 4.3, do i need to downgrade to 4.2.2, in order to get working recovery then flash your 4.3?
Sent from my C6903 using Tapatalk