Official - the 4.X.X update - discussion thread

This is for people that had the first problem of mobicore problem.

Warning::: THIS WORKED FOR ME BUT I CAN NOT SAY FOR EVERYONE. I AM NOT A DEVELOPER SO MY KNOWLEDGE IS VERY LIMITED!!!!

You need to download the update file from this thread. You will need to rename it to change the .cfg to .zip

Attached is a fix.zip that contains the files you need. You will need to be on a nb4 with root.

Extract zip files and copy them to your internal memory on phone.

Step 1 copy the mobicore-presetup.sh to /system/bin

Step 2 copy all the apk files to /system/app.

Step 3 For each apk you copied you need to set the rght persmissions. rw-r--r--

Step 4 Copy the update file that you renamed to external sdcard.

Step 5 Reboot into recovery by rebooting phone. As soon as screen goes blank from shutting down hold Volume Up + Home + Power. Once you see rebooting into recovery let go of only power button and wait.

Step 6 Once in recovery use the volume down button to highlight update from external storage and hit the power button.

Step 7 Use volume buttons to scroll down to update file and use power button to select it.

Step 8 Wait for about 5 to 10 minutes.

Step 9 You will be returned to recovery menu, scroll down using volume buttons to wipe cache and hit power button.

Step 10 Hit power button on reboot and wait.

Finally got mine to patch!

----CONFIGURATION OF MY PHONE -------------
+My phone was rooted via Kingo 1.18 on MJ5.
+Upgraded to NB4 via OTA.
+SafeStrap installed with 1 custom Rom on Slot 1. The "Stock" slot was untouched in SafeStrap.
--------------------------------------------------------------------

What I Did:

1) Boot into SafeStrap
2) Go to the Rom slots and delete all Roms and Partitions EXCEPT the stock slot (AGAIN, LEAVE THE STOCK SLOT ALONE!)
3) Reboot into the Stock Rom
4) Open the SafeStrap App and uninstall the bootloader

If Wanam Xposed is installed on your phone continue, else skip 5 & 6
5) Open Xposed app and Uninstall the Xposed Framework
6) Uninstall Wanam Xposed and Xposed apps

If you froze/Deleted any System apps continue, else skip 7 & 8
7) Open the app you used to freeze the system apps (e.g. Titanium Backup) and unfreeze them
8) If manually removed the system apps, go into your backup folder and restore them along with changing their permissions (search the forums for better explanations)

9) Open Root Explorer (or any file manager with root access) and go to /system/csc/
10) Look for feature.xml.bak. If this exists, delete feature.xml and rename feature.xml.bak to feature.xml
11) Go to /system/bin/
12) Look for ddexe_real. If this exists, delete ddexe and rename ddexe_real to ddexe.

13) Connect your phone to your computer and transfer the OTA Zip (here) to your External SD
14) Reboot into Recovery and select the update from SD Card option.
15) Choose the OTA Zip file and let the Flashing Start!


If this helped you, please hit the Thank You button and let us know.

Just to clear up any confusion...

There is no issue with the OTA in and of itself. If there was a mass problem, ATT would have recalled the update and made an announcement about it. The reason it is failing for some is because, at one point, these people had done something to their system. Either manually flashed a file in recovery, such as the GPS fix, or the leaked KK update from a month and a half ago, or attempted to root, or deleted system apps/bloatware. If you have never modified your system, or ran any task that would have modified your system in any way, the OTA works as intended. The tiniest change to your system, even if you're not rooted and are on stock NB4, would cause the update to fail.

What the update is doing is running a full system scan before applying the update. It's looking for every system app, every piece of bloatware, every system configuration file, etc, and comparing the data within to a reference list, so that each file can be updated. The OTA does not include the FULL system, meaning the data in the OTA cannot be used to make a full system image. That is, after all, the point of an "update" file. All of the apps and bloatware contained within the OTA are not the full apps, but are only the fragments of the apps that need to be updated. If the OTA was a full system image, it would be many GBs.

A lot of people are wondering why the NB4 update worked on modified MJ5 systems, but not this one. The NB4 update was a very small maintenance update that likely did not update any of the system files that are commonly modified, so it did not need to run the same kind of scans on the file system. The KK update, regardless of how people view it as, was a monster update which also updated every system app.

I've also seen some people mention that merely disabling a system/bloatware app through the Application Manager in Android would cause the OTA to fail. I can tell you that is not the case, as I had every ATT app and a lot of the Samsung provided apps disabled via this method. My OTA gave me no issues. Bottom line, if the update fails for you, you have either modified, or attempted to modify the system in some way, big or small. If you bought the phone used, or "certified refurbished", or if someone other than you uses it, they have attempted to modify the system, or have done so in the past.

The good news is that, even if you have modified the system, the talented people in this thread have figured out the issues and developed work-arounds. These will work. Just read, and follow instructions.

I created another mirror here: http://fs1.androidfilesharing.com/21dc79dd56165a61

baddison said:

Uploading to Dropbox. Link on the way.......

Click to expand...

Click to collapse

*dropbox suspended my public links*