4.4.2 KK Update Fix.

Search This thread

Ciberious42

Senior Member
Mar 16, 2013
57
15
INFO: Rooted Version of NB4, I was on 4.4.2 Kit Kat leaked. I reverted to MJ5 from the leaked version then updated to NB4 and rooted with kingo.

Thanks to...

@smokeystack76
@Otisrhw
@Jakman85
@Azrael.arach
@Budrweber


UPDATE: 3/30/14
The same method has been confirmed by @Budrweber but instead of using adb, just flash from your ext sd card.


NOTE: ADB SIDELOAD WILL NOT CAUSE A WIPE, BUT PUSHING THE UPDATE FROM EXTERNAL SD WILL WIPE ALL DATA.

Few users have reported unrooting on NB4 after changing files and downloading the OTA and updating normally.



USB DEBUGGING MUST BE ENABLED, if you are this far there is no need for me to explain how to turn it on. If your phone is unresponsive to your computer even though you have installed, re-install via Kies 3. Turn Kies 3 off before running ADB.


First of all, you are going to need an ADB Sideloader and it can be found here.

Install to directory C:\Mini-SDK

We'll come back to ADB later.

Now you're going to need the update file found here.

Rename the file to update. (DO NOT NAME UPDATE.ZIP, JUST "UPDATE".)

Place "UPDATE" into the same directory as your ADB C:\Mini-SDK

Now lets leave ADB and the Update file alone and start replacing the files on your phone! :)

You'll need the following files.

system/xbin/dexdump (if deleted you can find the file here or you can copy/paste & replace)

system/csc/feature.xml (If deleted find it here.
Delete the original "feature.xml" and rename "feature.xml.bak" to "feature.xml")

Download the fix.zip from this page.

You do not have to reset permissions, I did not how ever do as you feel and works for you.


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

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

Now navigate to system/bin

You should have a "ddexe" file, if it is named "ddexe_real", rename it to 'ddexe".

This should fix all the known errors in the process of adb side loading.

If you continue to get more errors use the file dump located here.

UPDATE: app_process is another recurring error, please grab this file from the dump uploaded from @smokeystack76

Now to the fun and most anticipated part of the day...

Volume + button up, power and home button all at the same time. Release once you see Recovery mode.

Navigate to Update from ADB.

Plug up to USB.

Now, when you start windows cmd prompt, you can either start from the ADB folder is located in by control, shift + right clicking or manual cmd.exe in "run" or "search"

Once command prompt is loaded,

Type in the following command.

"CD /D C:/MINI-SDK"

Then if you are in the right directory and you placed the "update" file accordingly... type...

ADB SIDELOAD UPDATE.ZIP(the file name should not have .zip or you will get a "can not read" message.)

and now you should be on your way to 4.4.2 Kit Kat.
 
Last edited:

clownfart

Senior Member
Jun 15, 2007
424
55
Thanks for the step by step. I'll try this tomorrow.

You were on a rooted NB4, correct? You restored to MJ5, updated to NB4, rooted, and then did this?
 

ariel123

Senior Member
Jan 28, 2009
582
11
New Jersey
For anyone trying to find an easy way around this whole update mess. Just go to your local best buy store and talk to one of the Samsung reps. They don't have the kit kat update yet but however they can reflash 4.3 on your phone wiping out all your data (make sure you do a back up from home) and this will let you get the OTA update with no problems. My note 3 has been rooted twice one being last night and it worked. Just make sure your not rooted when you take your phone.
 

mazdamiata210

Senior Member
Apr 8, 2012
685
340
Brooklyn, N.Y.
Has anyone tried doing an emergency restore (or whatever it's called) through kies first then trying to get the OTA to work without failing?

It seems like it's 50/50 on who's works and who's fails. Am I right?
 

hp79

Senior Member
Nov 14, 2007
483
104
Tigard, OR
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU

So did you root with Kingo too when you were on NB4? I didn't want to use Kingo, but I thought what the heck, and used it for quick rooting. Then after the Kitkat update, I realize I have SuperSU as a system app even after factory reset. Apps like CPU-Z reports my devices is rooted when it's not.

Is this the only thing that's not same as pure stock NC2?
 

carl1961

Senior Member
Dec 5, 2010
7,521
6,201
Tickfaw
So did you root with Kingo too when you were on NB4? I didn't want to use Kingo, but I thought what the heck, and used it for quick rooting. Then after the Kitkat update, I realize I have SuperSU as a system app even after factory reset. Apps like CPU-Z reports my devices is rooted when it's not.

Is this the only thing that's not same as pure stock NC2?

you can re-run and use kingo to remove the root
 

Ciberious42

Senior Member
Mar 16, 2013
57
15
Also if you are weary of the update, back up your files and apps then factory reset. Once you are factory reset, download the OTA but just hit "remind me later".

Do the instructions in the OP and after it installs it tells you that you have an update pending, install the update and it covers any files that may have went missing in the update.zip.

If you wanted to be 200% sure.

I am set at official and with no custom lock and Knox is 0x0.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    INFO: Rooted Version of NB4, I was on 4.4.2 Kit Kat leaked. I reverted to MJ5 from the leaked version then updated to NB4 and rooted with kingo.

    Thanks to...

    @smokeystack76
    @Otisrhw
    @Jakman85
    @Azrael.arach
    @Budrweber


    UPDATE: 3/30/14
    The same method has been confirmed by @Budrweber but instead of using adb, just flash from your ext sd card.


    NOTE: ADB SIDELOAD WILL NOT CAUSE A WIPE, BUT PUSHING THE UPDATE FROM EXTERNAL SD WILL WIPE ALL DATA.

    Few users have reported unrooting on NB4 after changing files and downloading the OTA and updating normally.



    USB DEBUGGING MUST BE ENABLED, if you are this far there is no need for me to explain how to turn it on. If your phone is unresponsive to your computer even though you have installed, re-install via Kies 3. Turn Kies 3 off before running ADB.


    First of all, you are going to need an ADB Sideloader and it can be found here.

    Install to directory C:\Mini-SDK

    We'll come back to ADB later.

    Now you're going to need the update file found here.

    Rename the file to update. (DO NOT NAME UPDATE.ZIP, JUST "UPDATE".)

    Place "UPDATE" into the same directory as your ADB C:\Mini-SDK

    Now lets leave ADB and the Update file alone and start replacing the files on your phone! :)

    You'll need the following files.

    system/xbin/dexdump (if deleted you can find the file here or you can copy/paste & replace)

    system/csc/feature.xml (If deleted find it here.
    Delete the original "feature.xml" and rename "feature.xml.bak" to "feature.xml")

    Download the fix.zip from this page.

    You do not have to reset permissions, I did not how ever do as you feel and works for you.


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

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

    Now navigate to system/bin

    You should have a "ddexe" file, if it is named "ddexe_real", rename it to 'ddexe".

    This should fix all the known errors in the process of adb side loading.

    If you continue to get more errors use the file dump located here.

    UPDATE: app_process is another recurring error, please grab this file from the dump uploaded from @smokeystack76

    Now to the fun and most anticipated part of the day...

    Volume + button up, power and home button all at the same time. Release once you see Recovery mode.

    Navigate to Update from ADB.

    Plug up to USB.

    Now, when you start windows cmd prompt, you can either start from the ADB folder is located in by control, shift + right clicking or manual cmd.exe in "run" or "search"

    Once command prompt is loaded,

    Type in the following command.

    "CD /D C:/MINI-SDK"

    Then if you are in the right directory and you placed the "update" file accordingly... type...

    ADB SIDELOAD UPDATE.ZIP(the file name should not have .zip or you will get a "can not read" message.)

    and now you should be on your way to 4.4.2 Kit Kat.
    1
    Thank you budrweber, I have to add that to the op.

    Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
    1
    Everyone saying they went to best buy or what not... lol... I was on nb4 and having the update error at 27%. All you have to do is root with kingo 1.1.8 use es explorer change all the files from the fix.zip. unroot through super su restart change your date a day ahead and pull the OTA update. Did it twice now and worked great!!!