[GUIDE][I337UCUAMF3][STOCK][NEUTERED] MF3 OTA Update - Keep Recovery and Root! [7-12]

• It will flash a new boot.img, which primarily includes the MF3 Kernel.
• It will flash the RPM partition, which as far as I can tell is strictly for power management. I kept it in the package because it seems harmless.
• It will update many files in your /system partition, bringing you up to the latest MF3 build (the whole point).
• It will flash the new MF3 modem/Baseband, along with its counterpart, the NON-HLOS partition as well. The NON-HLOS partition will cause some problems with your sound (keep reading), but I've added a patch here that will solve this problem while creating another (WiFi breaks). I've kept this included in the original neutered patch, just in case someone is able to find a very easy fix for the sound and/or WiFi.

dd if=/dev/block/mmcblk0p16 of=/sdcard/system-MF3.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/boot-MF3.img

1. Save a backup copy of your update file. One copy for safekeeping (in case you want to start over) and another to work on. Do it now.
2. Open the update file using basically any .zip editor. I used 7zip because it performed quickly, whilst Win7's zip capabilities were VERY SLOW dealing with this file.
   [*]From the root directory of the file, delete:
   
   • aboot.mbn
   • sbl2.mbn
   • sbl3.mbn
   • tz.mbn
   • The entire "recovery" directory.
3. Within the file, browse to META-INF\com\google\android and pull a copy of the updater-script. This file does all the magic.
4. Edit the updater-script using a text editor, preferably something like Notepad++ (great program! I recommend it). Make the following changes:
   
   • Remove the following line:
     Code:

     assert(getprop("ro.secure")=="1");

   • Edit the following line from:
     Code:

                      "/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil",

     to
     Code:

                      "/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil");

   • Remove the following line (it's right after the last one you edited):
     Code:

                      "/system/recovery.img");

   • Remove the following lines:
     Code:

     delete("/system/recovery-from-boot.p",
            "/system/etc/install-recovery.sh");

     and remove:
     Code:

     ui_print("Unpacking new recovery...");
     package_extract_dir("recovery", "/system");

     and remove:
     Code:

     set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");

     and remove:
     Code:

     ui_print("Update sbl2 ota");
     assert(write_backup_fota("/dev/block/mmcblk0p4", "/dev/block/mmcblk0p22"));
     assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p4"));
     assert(erase_backup_fota("/dev/block/mmcblk0p22"));
     ui_print("Package sbl2 Done.");
     ui_print("Update sbl3 ota");
     assert(write_backup_fota("/dev/block/mmcblk0p5", "/dev/block/mmcblk0p22"));
     assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p5"));
     assert(erase_backup_fota("/dev/block/mmcblk0p22"));
     ui_print("Package sbl3 Done.");
     ui_print("Update aboot ota");
     assert(write_backup_fota("/dev/block/mmcblk0p6", "/dev/block/mmcblk0p22"));
     assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p6"));
     assert(erase_backup_fota("/dev/block/mmcblk0p22"));
     ui_print("Package aboot Done.");

     and remove:
     Code:

     ui_print("Update tz ota");
     assert(write_backup_fota("/dev/block/mmcblk0p8", "/dev/block/mmcblk0p22"));
     assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));
     assert(erase_backup_fota("/dev/block/mmcblk0p22"));
     ui_print("Package tz Done.");

5. Save it, and put the modified updater-script back inside the update file where you found it, replacing the old one.
6. Upload it to your SDCard and flash. See all the warnings here in this post and in the original post about what to do with this thing.

• A careful reader will be able to easily tell what each part of the updater-script does, and you can choose whether or not to keep it, modify it, or delete it.
• Keep in mind that the update will fail if it does not pass all of those integrity checks. You can technically remove all of the integrity checks, and the update will still process, patching files left-and-right. However, depending on how heavily you have modified your system, you will probably run into extreme problems (soft brick most likely).
• CRITICAL WARNING ABOUT BOOTLOADERS: At this time, do NOT allow the update package to only partially update your bootloader! Failure to update the entire bootloader will result in a hard brick. For example, if you were to include the parts that update sbl2 and sbl3, but not include tz and aboot... your chain of trust will be violated, and the device will refuse to boot normally (a.k.a. QDL Mode or Emergency Boot). The only theoretically known way out of this is JTAG. You don't want to go there. So, simply put: regarding bootloaders, it's all or nothing. The bootloader updates included in this package are: sbl2.mbn sbl3.mbn aboot.mbn tz.mbn. It's like any good D&D campaign - if you separate these party members, the campaign is toast.
• REMINDER: At this time, it appears that flashing the new bootloader will trip an e-fuse. This is a hardware device that is only capable of incrementing a number. If the number on the e-fuse is higher than the bootloader you are trying to flash (with Odin, for example), the device will refuse to take the update. In other words, if you flash the MF3 bootloader, there is no known way to return to the MDB or MDL bootloaders at this time.

Aou said:

Interesting. Did you odin back to MDB stock or MDL stock? If you happen to have the MDL Odin (I still don't know where to find that?), then you'll probably get errors at that stage.

It's likely possible to do things in a slightly different order and skip some steps if you have the MDL Odin package. Otherwise, I posted what worked for me with what I had.

Click to expand...

Click to collapse