• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Kitkat 4.4 OTA failing even after passing ota verifier

Modman

Android Enthusiast
I didn't get the usual debuggerd failed.
Everything passed but I still got the red exclamation on the android with the error.

Hey Scary have you tried the 4.4 OTA yet? :confused:
 
I didn't get the usual debuggerd failed.
Everything passed but I still got the red exclamation on the android with the error.

Hey Scary have you tried the 4.4 OTA yet? :confused:

Did you try flashing the factory image? If you go that route, make sure you back up first
 
I get archive doesn't contain boot. sig and system. Sig now it's finally rewriting the system. Ill report back
 
I didn't get the usual debuggerd failed.
Everything passed but I still got the red exclamation on the android with the error.

Hey Scary have you tried the 4.4 OTA yet? :confused:

Hey Modman, sorry for the very delayed response here :(.

Got a couple of probably too late nuggets of info for all:

1. Had you previously saved root w/OTA RootKeeper or SuperSU (root survival mode) or with my app?

Turns out that the saved root's immutable settings hat all three of the above root saving methods employ [and pioneered by the OTA RootKeeper dev] (that allows root to be saved by not allowing the su binary to be removed or altered) kills the OTA installation.

2. Google added an "abort" verb/function to the updater-script for the KitKat OTA that my app expressly did not process. I did that because the app basically only expressly simulates or executes a limited number of innocuous and non-invasive functions, of which I didn't expect that the abort verb would be needed.

I do plan on supporting that in an upcoming version of the app that should rectify this, albeit much too late for you (and others).

Please, always feel free to PM me or ping me via email (scary.alien@gmail.com) if you have any questions or issues with any of my apps.

Thanks!
 
Back
Top Bottom