-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
I don't have any experience with your device or the N4 but with HTC phones at least, you cannot take the OTA while rooted. The ota requires at least a stock recovery and I believe one more requirement that is evading me at the moment.
Some people choose to return to stock, take the OTA and then root the OTA. It may be different for your device, but that's how it is for HTC phones anyway for what it's worth.
tmicrd68
Member
Was able to install 4.2.1 OTA update after rooting & used CM recovery on my Nexus 4. CMR allowed root to be kept after installing update. Only issue I initially had was I had also messed with my build prop which was blocking the OTA install. So I reinstalled the stock build prop & the OTA update took. Probably a good idea to keep nandroid backups or flashable copies of the stock ROM/kernel around if you go ahead & install a custom ROM or kernel as these may block any OTA update.
BTW I updated using a flashable zip of the 4.2.1 OTA found on XDA.
BTW I updated using a flashable zip of the 4.2.1 OTA found on XDA.
ritchea
Well-Known Member
tmicrd68, "BTW I updated using a flashable zip of the 4.2.1 OTA found on XDA." indicates that you did not get the OTA, correct? Just to be clear for ooberandy, as Brian706 said, Android OS won't accept OTA updates if you are running a custom recovery, or, as you indicated, altered build.prop. But, since the phone is running a custom recovery, flashable zips of the update get posted almost immediately, and Google posts the img files if one wishes to apply that way so zip/img files of the OTA's are available to apply---just not OverTheAir.
tmicrd68
Member
Not true downloaded the update several times over the air from Google and try to install with both stock and custom recovery and did not take. Also zip downloaded from XDA would not take at first. After researching I found out that some people who were having issues with the 4.2.1 OTA had messed with their build prop. After I fixed the build.prop, zip file I downloaded from XDA was the easiest available to install the time. My reason for posting was to reassure op that updating after rooting is possible from my experience with the n4.
An OTA's ability to be successfully installed is based wholly upon the cross-checks that are done in the updater-script file contained in the OTA's .zip installation file.
Typically, the files that are crossed-checked to make sure they are present and have the expected content are the key/core files that was present when you initially booted your device (i.e., system apps, files, stock recovery, stock boot image, stock boot animations, etc.).
Simply rooting your device (i.e., installing the su binary and either the Superuser or SuperSu app) would not prevent you receiving or successfully installing an OTA.
Having a custom ROM installed typically updates/replaces/omits many of these files and would cause the OTA to fail (for good reason: most OTAs are simply patches and and not wholesale replacements of the new versions of the Android components).
Hope that helps.
Typically, the files that are crossed-checked to make sure they are present and have the expected content are the key/core files that was present when you initially booted your device (i.e., system apps, files, stock recovery, stock boot image, stock boot animations, etc.).
Simply rooting your device (i.e., installing the su binary and either the Superuser or SuperSu app) would not prevent you receiving or successfully installing an OTA.
Having a custom ROM installed typically updates/replaces/omits many of these files and would cause the OTA to fail (for good reason: most OTAs are simply patches and and not wholesale replacements of the new versions of the Android components).
Hope that helps.