Update issues

[matt]

Unified thread?

The developers of root enabled apps always play catch up when there's an update. I'll try to categorize the issues and hopefully someone will post their solutions. Waiting to update all root apps and recoveries with bug fixes before the os update might be prudent.

1. Update not installing due to altered system files. (\cache file to find system file check errors?)
2. Hanging in recovery. No command. (Twrp?)
3. Hanging at boot animation. (Non stock launcher?)

Did I miss anything?

Sent from my Nexus 7 using Tapatalk 4

[radiocycle]

Hey Matt,

I've got the OTA update hanging there waiting for me to 'touch to install' but the first time it came around it didn't stick.  I am rooted but I don't *think* I've altered any of the system files how should I proceed?

radio

[matt]

I would first update all the apps with root privilege. If you open the superuser or supersu app there should be a list. Also busybox and supersu might have bug fixes. I've seen that stickmount has a kit kat update.

Do a backup just in case and make sure your adb or toolkit is still working. One of the toolkits may have a no wipe image install that could work. Wugfresh?

If the update doesn't take, there's a log file in /cache directory that should tell you what failed. Its usually a system file but it could be a bad memory chip or corrupted update download. Then search that file name on xda to find the app at fault. I.e. debuggered =stickmount
When you rooted, did you flash twrp or load it temporary?

I'm not an expert, haven't rooted my nexi, getting this info while trolling for other issues. Anyone else?

sent from me n7 using tappitytalk 4

[matt]

If you haven't cleared cache, the log file from the first aborted update may be useful.

sent from me n7 using tappitytalk 4

[matt]

/cache recovery.log

sent from me n7 using tappitytalk 4

[radiocycle]

Ah, tnx for the info matt!  I'll check into that first OTA attempt as soon as I can after 'spin' this morning...

radio

[matt]

If you aren't concerned with keeping your user data, you can flash the kit kat factory image, which will repair the system files.

With a toolkit, or adb/fastboot?
Stock, modified stock with root, or custom?

Sent from my Nexus 7 using Tapatalk 4

[radiocycle]

I guess you'd say stock with root.  I'll try the N7 toolkit now... we shall see, said the Colonel.

r

[radiocycle]

Ah, got it matt; thanks!  Now to decide which method to use to root again.

r

[matt]

This article may help explain the recovery hang issue.

http://www.androidpolice.com/2013/12/23/psa-make-sure-you-reboot-after-unlocking-your-nexus-or-gpe-devices-bootloader/

Part of the ota may be giving stock recovery commands on reboot which are ignored by a custom recovery.

Sent from my Nexus 7 using Tapatalk 4