Database Users

[Q] Can you install the 4.1.2 OTA on an unlocked phone with CWM installed?

I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...

Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.

what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.

Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app

bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!

bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...

sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...

After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.

bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.

netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.

patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!

Can't get root access?

I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html

Any ideas?

XXUAMDM Root not possible?
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
BTW: After the start of Titanium Backup the window asking about root for the app appeared.
Now starting Super SU I can see Titanium in the list, but short after start the mentioned "SU-Binary missing" window appears...

jochenthomas said:
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
Click to expand...
Click to collapse
Exactly the same as me, the update went fine, the rooting seemed to go fine too, but the binary is supposedly missing.

Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!

StuartTheFish said:
I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Click to expand...
Click to collapse
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app

topcat07 said:
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Different guide, but same method. We simply needed a modified file t work on the newer firmware.

StuartTheFish said:
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
Click to expand...
Click to collapse
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app

topcat07 said:
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Pass, don't know! All I do know is the regular cf auto root didn't work for me on this firmware, but the modified one did.

StuartTheFish said:
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
Click to expand...
Click to collapse
OMFG I have googled and torn my hair our for hours and hours as I just could not get root on my MDM S4 using the methods detailed on this site, this modified file rooted it straight away with no problems. It REALLY needs to be shouted a bit louder lol !
Thanks all.

this doesnt work for i9500
this kernel does not root i9500.
anyway i have a different problem and its about bluetooth. is this the proper place or should i search elsewhere?

No, there's a different method to rooting for a gt19500.

Thanks

I'm not rooted and I keep getting Custom Status...why?

I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!

polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.

euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer

You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2

peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...

I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2

polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2

Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium

XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.

polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.

TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.

CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here

CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....

Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.

CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last

so far so good!!!:fingers-crossed:

polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...

joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!

Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[Q] root for JDQ39.19505XXUBMEA

My new Samsung Galaxy S4 GT-19505 is running build JDQ39.19505XXUBMEA (android 4.2.2).
I haven't found anything on this build number with regards to rooting, so I'm wanting to be a little cautious before I attempt anything.
Any pointers on what tools / options I might attempt to use to root this?

SirLoinOfBeef said:
My new Samsung Galaxy S4 GT-19505 is running build JDQ39.19505XXUBMEA (android 4.2.2).
I haven't found anything on this build number with regards to rooting, so I'm wanting to be a little cautious before I attempt anything.
Any pointers on what tools / options I might attempt to use to root this?
Click to expand...
Click to collapse
Flash CF-Root with Odin and you`re rooted. Link http://forum.xda-developers.com/showthread.php?t=2219803, read the OP well and it will be easy.

Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta

SirLoinOfBeef said:
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No, it will only root it, you will not loose any data. After that flash a custom recovery if you need it and Busybox from Google Play,

SirLoinOfBeef said:
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There won't be any changes but root will be extra it won't wipe anything and u need not factory reset also
.

I tried it, and I'm not sure if it worked or not.
I have a a new SuperSU icon, but when I open it SuperSU tells me that the binary needs updating.
When I try to update it though it comes up with "Installation failed!"
Did the root fail? Is there something wrong with SuperSU? I'm not sure what's going on :s

SirLoinOfBeef said:
I tried it, and I'm not sure if it worked or not.
I have a a new SuperSU icon, but when I open it SuperSU tells me that the binary needs updating.
When I try to update it though it comes up with "Installation failed!"
Did the root fail? Is there something wrong with SuperSU? I'm not sure what's going on :s
Click to expand...
Click to collapse
Close all apps, reboot and try again to update the binaries. Have you checked for an update of the SU app in Google Play?

There was an update, which I have installed.
I also just installed Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) which tells me I am not rooted

SirLoinOfBeef said:
There was an update, which I have installed.
I also just installed Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) which tells me I am not rooted
Click to expand...
Click to collapse
Open the SU app and unroot and try rooting again by flashing CF-Root. Do you have usb debugging enabled on the phone in developer options?

I have debugging enabled.
I tried re-rooting, and now have no SU app at all
Very confused. This should be a simple process.

4.4.2 KK Update Fix.

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.

Not bad. The system dump is here.
Now you need to post links to this thread in the other thread

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?

clownfart said:
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?
Click to expand...
Click to collapse
Correct.

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.

Ciberious42 said:
Correct.
Click to expand...
Click to collapse
I think you should mention that in the OP for perfect clarity.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

incisivekeith said:
I think you should mention that in the OP for perfect clarity.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I did actually...

Ciberious42 said:
I did actually...
Click to expand...
Click to collapse
I didn't see in the OP that you rooted the NB4.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

incisivekeith said:
I didn't see in the OP that you rooted the NB4.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU

smokestack76 said:
Not bad. The system dump is here.
Now you need to post links to this thread in the other thread
Click to expand...
Click to collapse
How do I flash this?

xuanphucn said:
How do I flash this?
Click to expand...
Click to collapse
you don't, it is used by DEV's to make a flashable update

carl1961 said:
you don't, it is used by DEV's to make a flashable update
Click to expand...
Click to collapse
Did we have any safe method yet? I want to keep root

xuanphucn said:
Did we have any safe method yet? I want to keep root
Click to expand...
Click to collapse
knoxraid
http://forum.xda-developers.com/showthread.php?t=2577273
I am currently updating the UrDroid Stock KitKat

carl1961 said:
knoxraid
http://forum.xda-developers.com/showthread.php?t=2577273
I am currently updating the UrDroid Stock KitKat
Click to expand...
Click to collapse
is this one use the official 4.4.2 or the leak?

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?

xuanphucn said:
is this one use the official 4.4.2 or the leak?
Click to expand...
Click to collapse
yes custom rom with latest OTA kitkat

Thanks OP. Worked for me. I'm ok with stock on the Note 3 that's why I got a nexus

Ciberious42 said:
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU
Click to expand...
Click to collapse
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?

hp79 said:
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?
Click to expand...
Click to collapse
you can re-run and use kingo to remove the root

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.