Database Users

[Q] Custom Recovery or Stock Recovery?

I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?

This is exactly why I hate these toolkits...
Boot into recovery, check what it says. If it only shows you an android with a triangle, it's probably stock. If it's anything else (eg TWRP or Clockwork Recovery) then it's a custom.

You can be on Stock Rom with No Mods Unlocked Rooted with a Custom Recovery and you will get the ota update and it will install fine.
The ota update link will be posted here before you get on your device so it's good to have a custom recovery so you can just flash it. It will also protect you from losing root and your custom recovery
To check if you have a custom recovery with the phone off press and hold power and volume down then when in bootloader press volume down till you see recovery press power button if you get a android laying down that's stock recovery
Sent from my Nexus 4

ryfly65 said:
I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?
Click to expand...
Click to collapse
Rooting doesn't interfere with OTA updates. You are still able to update even with a custom recovery, and it actually makes things easier because you don't have to flash a custom recovery and then root after each update if you have a custom recovery. Custom recoveries offer many more options than regular as well.
For your original question, just power down your phone and turn it back on by holding both volume up and down while holding the power button. This will bring you to the bootloader. From there, navigate to recovery using the arrow keys and push power. If it's a custom recovery you'll know, and if it's stock, you'll just see an android.
It's recommended not to use automated programs to root because you don't learn anything, by the way, although it makes things much easier.
Sent from my Nexus 4 using xda app-developers app

^^^^^ that's what I said
Sent from my Nexus 4

spaceman860 said:
^^^^^ that's what I said
Sent from my Nexus 4
Click to expand...
Click to collapse
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app

hoponpop said:
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4

spaceman860 said:
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4
Click to expand...
Click to collapse
You're right. My bad, lol
Sent from my Nexus 4 using xda app-developers app

I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.

ryfly65 said:
I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.
Click to expand...
Click to collapse
That's the stock recovery. You have to press volume up and power to see the menu.

El Daddy said:
That's the stock recovery. You have to press volume up and power to see the menu.
Click to expand...
Click to collapse
Do you mean when it shows the dead Android with the triangle? Or before that?

ryfly65 said:
Do you mean when it shows the dead Android with the triangle? Or before that?
Click to expand...
Click to collapse
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.

El Daddy said:
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.
Click to expand...
Click to collapse
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.

ryfly65 said:
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.
Click to expand...
Click to collapse
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.

El Daddy said:
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.
Click to expand...
Click to collapse
I am completely stock with stock recovery; unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?

ryfly65 said:
So I am completely stock with stock recovery, unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?
Click to expand...
Click to collapse
You should be OK just changing them back. Additions to /system are fine too. If it does end up falling you can just flash the system image with fastboot
Sent from my Nexus 10 using Tapatalk 4 Beta

[Verizon]OTA Droid Maxx update info + Download File

Verizon Droid Maxx XT1080
-Camara application
-Google Drive 50GB Promotion
-Mophie Juice pack compatibility
- Wireless charging has been improved to support faster connections
- 4G LTE performance has been improved to support faster connection
- Motorola Assist has been improved for better stability
- Google Voice now returns cards with audible feedback when location setting is enabled
- The lastest version of NFL Mobile has been added
- Viewdini has been removed as a preloaded application
^^Thank you for reminding me supreme!
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Download Link:
Blur_Version.12.7.7.obake-maxx_verizon
Presumably you can drop the .zip into your /cache folder (where it was located on mine) and update

I wonder if the ultra will also receive this
Sent from Ahjee's Ultra which is likely better than your phone

Make sure you have a backup in TWRP before running this as it does not take kindly to root. I had a "Shutdown" loop after installing on rooted device.

Could you please extract and post the Google Drive Apk?
Sent from my Nexus 5 using Tapatalk

Kickbut101 said:
Verizon Droid Maxx xt1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Just to note: As far as I know I am not part of any pre-release test groups/soak tests.
Click to expand...
Click to collapse
I installed the update while rooted and now my phone is power cycling and I can't get it to stop. My fault for not unrooting, I know, but if anyone has insight on how to fix this, it'd be appreciated.

Well I unrooted by fxz save data then installed the pwnmymoto apk took the update and got root back all is normal but I can't access touchless control it wont allow me to check the box. google search works but not touchless control. Can we fxz back with this update or will it brick our phone.
Ok I unistalled and then updated the app but now I get to the training screen but it doesn't activate it's like it can't hear me.

bigv5150 said:
Well I unrooted by fxz save data then installed the pwnmymoto apk took the update and got root back all is normal but I can't access touchless control it wont allow me to check the box. google search works but not touchless control. Can we fxz back with this update or will it brick our phone.
Ok I unistalled and then updated the app but now I get to the training screen but it doesn't activate it's like it can't hear me.
Click to expand...
Click to collapse
You have to update it from the play store. I had that problem before the update. Could you tell me the exact process you used to root the update? I'm about to try and upgrade, but can't survive without root lol
Sent from my XT1080 using XDA Premium 4 mobile app

needshelp101 said:
You have to update it from the play store. I had that problem before the update. Could you tell me the exact process you used to root the update? I'm about to try and upgrade, but can't survive without root lol
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did an fxz save data with house of moto which restores to stock but keeps data. Then I re-installed pwnmymoto but did not run it. rebooted to recovery and installed the update from my sdcard. everything went fine but no touchless controls I installed the update and still it would not let me past the training screen. So I said **** it and installed the stock recovery did a factory reset and now I am good I will just juse the new root method.
If you use my method above when you reboot after the update pwnmymoto will automatically run and install root it cycles 3 times so don't worry you are not in a bootloop with it shutting on and off.

The adb root method? By jcase? I'm a little hesitant to use that one. Since I have no prior adb experience
Sent from my XT1080 using XDA Premium 4 mobile app

needshelp101 said:
The adb root method? By jcase? I'm a little hesitant to use that one. Since I have no prior adb experience
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PwnMyMoto was an apk you download http://forum.xda-developers.com/showthread.php?t=2444954
Super super easy to do.
Glad to hear someone was able to use this as a new ota root method. But I haven't heard of many others doing this. It's still a little early to hear all the news.

starose
Kickbut101 said:
Verizon Droid Maxx XT1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Moved the downloaded file to /cache. Fastbooted the stock recovery and temp un-rooted. Every time I try and update though, it tells me that my device is up to date.
Thoughts?
Click to expand...
Click to collapse

Can anyone confirm if SafeStrap is working with the updated build? After the new root exploit, that is.

offeldn
killboredom said:
Kickbut101 said:
Verizon Droid Maxx XT1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Moved the downloaded file to /cache. Fastbooted the stock recovery and temp un-rooted. Every time I try and update though, it tells me that my device is up to date.
Thoughts?
Click to expand...
Click to collapse
Booted to recovery and applied update from SD. failed with "set_perm: some changes failed" Rebooting and it says "Android is upgrading." We'll see I guess.
---------- Post added at 01:08 AM ---------- Previous post was at 12:49 AM ----------
killboredom said:
killboredom said:
Booted to recovery and applied update from SD. failed with "set_perm: some changes failed" Rebooting and it says "Android is upgrading." We'll see I guess.
Click to expand...
Click to collapse
Brilliant! Booted to system version 12.15.15. So...followed these directions to maintain root:
http://forum.xda-developers.com/showthread.php?t=2466191
To apply the "OTA" I booted to stock recovery and updated from SD. This failed, but booted to 12.15.15.
Then in the above directions, used fastboot to install the new baseband from the modem drivers from another thread in this forum.
profit!!!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Just to help anyone out I am part of the soak test. If you try to update by hiding root and then flashing stock recover you will get error from trying to install from stock recovery or if you where able to do an ota it will fail. It will show afterwards that you are on the version but you are lacking some things. Anyways The way That I got everything to work without a single error including the baseband coming from the ota .
used fastboot to flash recovery back to stock recover . Flashed stock system to system in fastboot. After that then I installed that I backed up after download from verizon through stock recovery from sd card. after I came back online. I used adb and the RockMyMoto Root and walla everything good to go.
Hope this info helps some !!

I've downloaded it and placed it in cache but my phone still says it's up to date? Any thoughts?

Sorry, what do you mean under
Make sure you have a TWRP backup before installing!
Click to expand...
Click to collapse
?
Is there a boot-loader unlock option for XT1080Mto flash TWRP? Where is TWRP for XT1080M?

I installed it in reocovery. It did say that it was aborted and that some files did not update however after rebooting it says Android is upgrading Optimizing apps xxx of 131.
Did it update or not?

bluh5d said:
Just to help anyone out I am part of the soak test. If you try to update by hiding root and then flashing stock recover you will get error from trying to install from stock recovery or if you where able to do an ota it will fail. It will show afterwards that you are on the version but you are lacking some things. Anyways The way That I got everything to work without a single error including the baseband coming from the ota .
used fastboot to flash recovery back to stock recover . Flashed stock system to system in fastboot. After that then I installed that I backed up after download from verizon through stock recovery from sd card. after I came back online. I used adb and the RockMyMoto Root and walla everything good to go.
Hope this info helps some !!
Click to expand...
Click to collapse
Interesting... How do you determine the you are missing stuff? How did you flash the stock system?
Things seem to be running fine through my method, but the update did fail and I certainly haven't tried everything.
Sent from my XT1080 using Tapatalk

Cincybearcatfan said:
I installed it in reocovery. It did say that it was aborted and that some files did not update however after rebooting it says Android is upgrading Optimizing apps xxx of 131.
Did it update or not?
Click to expand...
Click to collapse
It appears at least some things were updated. When I rebooted, I got the "moto camera" update from the market and when I check build number it is the 15.15.15 update so it looks like that went through. I'm just curious as to what "failed" and what made it through.

For those that failed halfway through, you most likely don't have the new baseband (95). You'll be unable to take future updates until you get everything squared away.
Sent from my XT1080MDEV.

Google Edition - 4.4 Phase 2 OTA roll out.

Post here if you received the OTA after initially being declined on the first phase.
Sent from my HTC O'ne-xus

Still no OTA .. how long does phase 2 last ?

Izzymane said:
Still no OTA .. how long does phase 2 last ?
Click to expand...
Click to collapse
Until phase 3.

Why not download the zip and flash it like the rest of us?

Because when I tried my phone would boot only into recovery

still waiting here. sideload fails. (check cid failed) and im 100% stock, real GPe purchased new from Google Play store.

nothing yet... uk
Sent from my HTC One using XDA Premium 4 mobile app

Just so you know when you download the OTA it will download the same zip and boot into recovery for you. If you get some sort of errors now you will get them when you try to install the OTA. Best way to install it is to re-install 4.3 stock and than the 4.4 OTA zip.

Seen people mention even with genuine stock gpe's have failures with side loading.
Due to these issues i decided to wait.
Hopefully we can identify when phase 2 starts.
Sent from my HTC O'ne-xus

pr0x2 said:
Just so you know when you download the OTA it will download the same zip and boot into recovery for you. If you get some sort of errors now you will get them when you try to install the OTA. Best way to install it is to re-install 4.3 stock and than the 4.4 OTA zip.
Click to expand...
Click to collapse
i never thought about this. my phone is 100% stock purchased from Google. I got the 4.3 OTA just fine back when it came out.
why the issue now?

If people want it they just need to go stock 4.3 unrooted with stock recovery. Download the zip and push it to the sdcard. Boot into recovery, hold vol h and press power. I got an sdcard mount failure 5 times then a menu. Choose load from phone storage and select the ota zip you pushed.
Sent from my HTC One using Tapatalk

Donjuanal said:
If people want it they just need to go stock 4.3 unrooted with stock recovery. Download the zip and push it to the sdcard. Boot into recovery, hold vol h and press power. I got an sdcard mount failure 5 times then a menu. Choose load from phone storage and select the ota zip you pushed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes yes its so simple. you clearly arent reading the posts where people are stating this isnt working. even on stock real GPe already running stock 4.3 unrooted.

Im on an ATT converted model and it worked just fine for me. I find it hard to believe its not working on legitimate GPe devices.
Sent from my HTC One using Tapatalk

Donjuanal said:
Im on an ATT converted model and it worked just fine for me. I find it hard to believe its not working on legitimate GPe devices.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
you can find it hard to believe...or you can just read around and see that we cannot flash it

CraigP17 said:
you can find it hard to believe...or you can just read around and see that we cannot flash it
Click to expand...
Click to collapse
You need S-OFF to manually flash an OTA file, regardless of the phone being an official GPe or a Sense-based phone. No S-OFF, no manual flash

hTC_102...converted to GPE...unlocked, s-off, rooted...just temporary unrooted and installed the OTA from Stock recovery...works...

I received the OTA, and it soft-bricked my phone. Fortunately, I was able to get into bootloader and just ran the RUU...

Upgraded fine
Mine just updated fine in the uk

marantz69 said:
Mine just updated fine in the uk
Click to expand...
Click to collapse
I've converted my one to GE, s-ff, cid GOOGL001, flashed 4.3 RUU, only received 4.3(JWR66Y.H1) update, no 4.4 yet(

mih3y said:
I've converted my one to GE, s-ff, cid GOOGL001, flashed 4.3 RUU, only received 4.3(JWR66Y.H1) update, no 4.4 yet(
Click to expand...
Click to collapse
if you have s-off, just sideload the OTA

At&t moto x 4.4.2 ota link

https://onedrive.live.com/redir?resid=CCA504C67312C165!507&authkey=!ANidm4D119J3yZc&ithint=file,.zip
Here you go gang.
Sent from my XT1058 using xda app-developers app

Worked like a charm for me. Thanks!

Thanks!
southern87 said:
https://onedrive.live.com/redir?resid=CCA504C67312C165!507&authkey=!ANidm4D119J3yZc&ithint=file,.zip
Here you go gang.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Awesome. thanks!
for those who are like me and haven't felt the need to root their phone or use a custom recovery, the process below worked to update an unlocked, un-rooted, stock AT&T moto x. this is probably available elswhere on the forms too.
- copy the zip into "download" on the internal storage
- boot into bootloader by holding volume down and power together
- at the bootloader screen, use volume down and scroll to "recovery", then press volume up to select it
- in recovery mode you will see "no command". hold volume up and press power to show the recovery menu
- use volume down to go to "apply update from sdcard" then press power to enter
- you should be at "choose a package to install", use the volume buttons to highlight "download/" and press power
- use the volume buttons to highlight the zip and press power
the update will start. it took about 5 minutes on my device. when it finishes, use volume keys to select "restart system" and press power. device will restart and you're done.

for unlocked bootloader we'd have to delete superuser to install this, correct?

murso74 said:
for unlocked bootloader we'd have to delete superuser to install this, correct?
Click to expand...
Click to collapse
No, you don't need to uninstall superuser. If you use xposed, make sure you uninstall the framework (no need to uninstall the modules).

rohandhruva said:
No, you don't need to uninstall superuser. If you use xposed, make sure you uninstall the framework (no need to uninstall the modules).
Click to expand...
Click to collapse
awesome. thanks
---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------
crap, didn't work. says its for "ghost" devices, which i though i was (att 1058)

I get to this point and nothing happens.
- in recovery mode you will see "no command". hold volume up and press power to show the recovery menu
Only thing I can do is long press power to reset the phone
Sent from my Moto X

REDFOCZ said:
I get to this point and nothing happens.
- in recovery mode you will see "no command". hold volume up and press power to show the recovery menu
Only thing I can do is long press power to reset the phone
Sent from my Moto X
Click to expand...
Click to collapse
I tied to flash via recovery, but the verification check didn't complete. the email.apk didn't match. I removed it when I updated to 4.4.
I flashed down to 4.2.2 from 4.4 and rerunning slap my moto because I am rooted, but no su binary. lol

For those who had issues taking the OTA. You have 2 options that I see.
Removing the verification lines from the updater script. Don't know if that will work or what it will do.
or
Reflashing to 4.2.2 via RSD Lite. The write protection is still 0. using slapmymoto again and updating via OTA to 4.4. You will lose all data. I used to titanium back up and stored my stuff to the my box drive.
I am installing 4.4.2 via recovery from the OTA i downloaded this morning and I don't have that stupid email.apk issue. The system update says i am up to date so I had to do this way.

rohandhruva said:
No, you don't need to uninstall superuser. If you use xposed, make sure you uninstall the framework (no need to uninstall the modules).
Click to expand...
Click to collapse
Excuse my not knowing, but I just came to the forums here to peek around and see about this, since I'm on AT&T. If I uninstall the framework and take the update, what do I have to do to enable xposed after the update? Do I have to reinstall the framework every reboot?

Xenther said:
Excuse my not knowing, but I just came to the forums here to peek around and see about this, since I'm on AT&T. If I uninstall the framework and take the update, what do I have to do to enable xposed after the update? Do I have to reinstall the framework every reboot?
Click to expand...
Click to collapse
Redownload the framework install app. Is what I did after I eventually got it to update to 4.4.2 lol

Xenther said:
Excuse my not knowing, but I just came to the forums here to peek around and see about this, since I'm on AT&T. If I uninstall the framework and take the update, what do I have to do to enable xposed after the update? Do I have to reinstall the framework every reboot?
Click to expand...
Click to collapse
Additionally, you also want to ensure that your /system is not write protected. If your bootloader is not unlocked, /system partition will most likely be write protected, so XPosed will not work until you do a soft-reboot (from the installer app) every time you restart your phone.

I just figured that out hahaha
Sent from my XT1058 using xda app-developers app

Do you need stock recovery for this to work or will twrp work? Can't figure out why mine won't take
Sent from my XT1058 using Tapatalk

murso74 said:
Do you need stock recovery for this to work or will twrp work? Can't figure out why mine won't take
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
You need stock recovery, TWRP won't work.

Does it say some bs about the email. Ask?
Sent from my XT1058 using xda app-developers app

Thanks for the link, updated and all is good so far. I was a tard in the recovery and hitting power vs volume up to select recovery.... Oops but all is good now
Sent from my Moto X

Took the ota and kept root but not write protection.
Sent from my XT1058 using xda premium

had to restore my email.apk back to stock before this worked...oh well

[email protected] said:
Took the ota and kept root but not write protection.
Sent from my XT1058 using xda premium
Click to expand...
Click to collapse
Everyone lost it. I tried to use the thing to kill it again. Fail lol
Sent from my XT1058 using xda app-developers app

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.