KitKat 4.4.2

[dominic]

Thank You S. Prime for your patience
I did try what you mentioned before and retry again this morning.
I tried all 3 options, stock recovery, cwp (?) and TWRP.
All failed when try to sideload the zip file.
Error:  device not connected
The N7 was recognized throughout the process without any issues.
When I got the fallen red triangle, I hold the power + vol up buttom, it give me a menu.
Using the volume button to choose sideload. N7 waits for the file and I type yes on the skip soft question, this is where skipsoft indicates device not connected
I had to hold the power button for a few seconds to reboot in android

=============
Note: I read in XDA forum that someone had to change the debuggerd file. I download the file,  however I am unable to locate the folder system/bin on the N7 to replace it. I checked every folder on the N7 and can not find the system/bin folder I used the PC as well as File Explorer to find it but not success in doing so

[matt]

I think you need to get the adb/fastboot drivers working again. The debuggerd file is modified by stickmount and can cause the ota to fail, but not to soft brick IMO. If you can get android to load, uninstall stickmount before updating, this should replace that file with stock. Then reroot and reinstall.

sent from me n7 using tappitytalk 4

[S.Prime]

With the nexus 7 connected to your computer, open a command prompt in the folder where adb is installed and type adb devices and if adb is installed correctly it should list your nexus 7, if not you will need to reinstall the drivers with the toolkit.

[dominic]

I uninstall Stickmount and reboot and try the OTA using both Skippensoft and Wugfresh but no success
I try "adb devices" as suggested and  it recognize my N7
Using ES explorer I found the debuggerd file but unable to delete/rename it. Try to copy a new debuggerd file over the old one and it does not allow me

My wild guess is that if I can replace the current debuggerd file with another one, it should work

[matt]

Look for recovery.log in /cache, it may tell you where the ota is failing.

Sent from my Nexus 7 using Tapatalk 4

[matt]

In es file explorer, scroll down on the left pane, select tools and turn on root explorer. You can find the debuggerd file on xda, if that is the cause. If you replace it, make sure the permissions are set the same.

Sent from my Nexus 7 using Tapatalk 4

[dominic]

Thank You for your great efforts and patience in trying to help me
I really appreciate it
I FINALLY got the 4.4.2 (KOT49H) in a crazy way, should I say unorthodox.
I understand that there is a flashable zip that may help me so I download it (grouper_krt160)
and install it using TWRP.
After installation I check "about table' and it shows KRT160. However, it also allows the OTA update to  KOT49H (4.4.2)
I have to re-rooted it and all is in order

[matt]

Yeah, a clean install of a factory image seems the easiest fix. It doesn't find the cause. Ideally, any app that needs root should be able to revert to stock the system files it changed to allow an ota to complete. Congrats!

Sent from my Nexus 7 using Tapatalk 4

[S.Prime]

Glad you made it work. My Nexus 10 is a bit problematic with OTA's as well, but my Nexus 7 has no issues, just saying. :-)

Sent from my Nexus 7 using Tapatalk

[CBers]

Deleted.

[CBers]

Deleted.