Root [Verizon] Error updating to 4.4 OTA From 4.3 (Rooted)

[KingdomMan3]

I am currently on 4.3 rooted with Kingo. I see that Kitkat has finally been rooted.

When I accept the OTA update it fails. Am I doing something wrong?

What steps should I take to go from Stock 4.3 rooted with Kingo to OTA Kitkat rooted with Towel Root?

 

[scary alien]

Examine the last part of your /cache/recovery/last_log after trying to install the OTA to see why it failed.

There are cross-checks inside the updater-script file inside the OTA's .zip file to help ensure that it's being installed on the correct device, version of Android, etc. and to ensure that any files that might be patched are the correct version.

Your next steps will depend on what you find in the recovery log file and will probably require the feedback of the fine root folks in this Note 3 area.

Cheers!

 

[KingdomMan3]

Thanks for the response

I believe this is the section the root experts will need

[Installing package]

-- Installing package...
stat() of /dev/block/platform/msm_sdcc.1/by-name/userdata succeeded on try 1
Finding update package...
I:Update location: /cache/fota/update.zip
stat() of /dev/block/platform/msm_sdcc.1/by-name/efs succeeded on try 1
Opening update package...
I:read key e=3
I:read key e=3
I:2 key(s) loaded from /res/keys
Verifying update package...
I:comment is 3317 bytes; signature 1778 bytes from end
signed len : 646729963
sha1 : 646729984
e93b18c8 e23747ff 343399f1 64cae043 87ddad49
e9 3b 18 c8 e2 37 47 ff 34 33 99 f1 64 ca e0 43 87 dd ad 49
52 53 41 50 4b 05 06 00 00 00 00 68 08 68 08 b9 c5 02 00 1e
8b 89 26 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
34 62 87 58
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Register_libbootloader_updater Qcom msm8960
open failed '/sys/fs/scfs/system_type' - No such file or directory
Verifying current system...
file "/system/bin/ddexe" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
failed to stat "/data/.saved.file": No such file or directory
failed to load data file
script aborted: "/system/bin/ddexe" has unexpected contents.
"/system/bin/ddexe" has unexpected contents.
E :Error in /cache/fota/update.zip
(Status 7)
E:Error in /cache/fota/update.zip
(Status 7)
FOTA_update_success_log_result()
Update Fail. File is written. status = 7
Installation aborted.

[installing post-recovery]

 

[scary alien]

The following snippet of your recovery log:

:
:
Installing update...
Register_libbootloader_updater Qcom msm8960
open failed '/sys/fs/scfs/system_type' - No such file or directory
Verifying current system...
file "/system/bin/ddexe" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
failed to stat "/data/.saved.file": No such file or directory
failed to load data file
script aborted: "/system/bin/ddexe" has unexpected contents.
"/system/bin/ddexe" has unexpected contents.
E :Error in /cache/fota/update.zip
(Status 7)
E:Error in /cache/fota/update.zip
(Status 7)
FOTA_update_success_log_result()
Update Fail. File is written. status = 7
Installation aborted.

shows that it failed because the file /system/bin/ddexe does not match what the OTA expects it to (i.e., it's SHA1 checksum is different that the version expected). It doesn't want to (and shouldn't) try to patch a file that would not be correct (you'd end-up with a bad file).

I'm not familiar with that file or how it might have gotten updated/replaced but there's at least the starting point for you to try to get the original file version restored back to what it expects. Some root apps will monkey with things in the system partition, but often don't create a backup version or tell you what is being done so that you can easily get back to the stock version.

Also note that this might not be the only file that your OTA will find that's different--it typically only reports and fails on the first bad file. If you are able to save the OTA's .zip file (before installing) from your /cache partition (/cache/fota/update.zip) off to somewhere else (/sdcard, etc.) before installing it, you could download and run my OTA Verifier app to analyze your OTA: it will try to tell you all of the files that it thinks the OTA will report as an issue. See the link in my signature for the app.

Cheers and best of luck!

 

[Digital Controller]

Please if you intend on rooting do not update to 4.4 stock.

It is more difficult and not a full proof root strategy once you are on 4.4.

If you are looking to root to 4.4, please follow my guide here: http://androidforums.com/verizon-ga.../852829-guide-nonrooted-rooted-4-3-4-4-a.html

 

[scary alien]

^^^ :thumbup:

Also, you should be able to save a 4.3+ root prior to installing an OTA (that would typically strip / remove root) via Pau Oliva's keeproot.sh script.

I've supported that script and method in my Android Root Toolkit app for those interested.

 

[KingdomMan3]

Thanks guys for the help!

Please if you intend on rooting do not update to 4.4 stock.

It is more difficult and not a full proof root strategy once you are on 4.4.

If you are looking to root to 4.4, please follow my guide here: http://androidforums.com/verizon-ga.../852829-guide-nonrooted-rooted-4-3-4-4-a.html

I want to stay stock because I am probably going to get a new a phone in the next couple of months and want to sell this phone with a stock rom. With the information you provided should I just wait until the root process becomes more streamline?

^^^ :thumbup:

Also, you should be able to save a 4.3+ root prior to installing an OTA (that would typically strip / remove root) via Pau Oliva's keeproot.sh script.

I've supported that script and method in my Android Root Toolkit app for those interested.

I guess I'm kind of stuck if I don't want to update to a custom rom since it is failing with the OTA.

 

[Digital Controller]

You could just push the new firmware onto your device via Odin.

You could also try and use Kies.

 

[KingdomMan3]

^^^ :thumbup:

Also, you should be able to save a 4.3+ root prior to installing an OTA (that would typically strip / remove root) via Pau Oliva's keeproot.sh script.

I've supported that script and method in my Android Root Toolkit app for those interested.

You could just push the new firmware onto your device via Odin.

You could also try and use Kies.

I tried using the Android Root Toolkit to save root, and it said it was saved, however after a successful upgrade via Kies I don't have root.

Is Towelroot my best method now? Should I do a factory reset or clear cache now that I am upgraded? I remember back in the day there were issues with upgrading to major versions.

Edit: It's actually weird. Now that I'm on 4.4.2 it's saying I have another OTA. I didn't think 4.4.3 or 4.4.4 had been released for the Note 3.

Thanks for the help guys

 

[scary alien]

I tried using the Android Root Toolkit to save root, and it said it was saved, however after a successful upgrade via Kies I don't have root.

Did you happen to reboot after doing the 4.3+ root save via my app?

It only saves root for one reboot cycle and needs to be done just before you'd need root to be saved (i.e., just before the OTA is told to install).

 

[KingdomMan3]

Did you happen to reboot after doing the 4.3+ root save via my app?

It only saves root for one reboot cycle and needs to be done just before you'd need root to be saved (i.e., just before the OTA is told to install).

I saved root and then used Kies. I'm not sure how many times it rebooted while connected to Kies. That may be the reason it lost it.

 

[Digital Controller]

There was a minor security update, that's what that little update is.

Also Towelroot, I am pretty sure, is still the only method.

Should be some guides in the stickied area in this root forum.