[Nexus 7 General] techn0mage:
Unfortunately, bricked?

I own the Nexus 7 (2012), WiFi only. I rooted it, in the process I ended up with clockworkmod recovery and twrp and SuperSU installed. CWM recovery was the designated recovery mode at the time I tried the update. I received the notice of the OTA 4.3 update, did a full backup (from CWM), and tried to install 4.3 from the OTA notification. But the install failed. The device booted normally but I did a restore to before I even attempted the update anyway, and searched for the 'right' way to do this. (The OTA update notification is back, since I restored everything).

Unfortunately these instructions did not seem to work for me. My bootloader reported success in updating but did not actually update - and now the device is not reachable via ADB and does not respond to any button presses, I think it is powered on in a 'frozen' state.

I have the command window open showing what I did and I will paste it here. I am doing this from git-bash under Windows 7 x64

$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d490699180801 device

--(So far, so good)

$ adb reboot-bootloader

--(Seemed to work, device shows green android with the hatch open)

$ dir
sh: dir: command not found

--(Oops, I often do this)

$ ls
AdbWinApi.dll NOTICE.txt api fastboot.exe source.properties
AdbWinUsbApi.dll adb.exe deljava.txt nakasig-jwr66v

$ ls nakasig-jwr66v/
bootloader-tilapia-4.23.img flash-all.sh image-nakasig-jwr66v.zip
flash-all.bat flash-base.sh radio-tilapia-1231_0.18.0_0409.img

--(So this is what I've got)

$ fastboot flash bootloader nakasig-jwr66v/bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
OKAY [ 1.232s]
finished. total time: 1.504s

--(Success, right? Actually, WRONG, keep reading)

$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s

--(Seemed to work. But what I didnt notice YET is that the bootloader still identifies as "GROUPER" when I just flashed "TILAPIA", supposedly)

$ fastboot update nakasig-jwr66v/image-nakasig-jwr66v.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d490699180801
--------------------------------------------
checking product...
FAILED

Device product is 'grouper'.
Update requires 'tilapia'.

finished. total time: 0.182s

--(OK, now I look again at the bootloader screen and can see it says 'grouper' in micro print. So what to do? Maybe try flashing bootloader again?)

$ fastboot flash bootloader nakasig-jwr66v/bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
OKAY [ 1.222s]
finished. total time: 1.488s

$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s

--(Should work, right? Well, bootloader still says grouper. Maybe I should power cycle the device to get the bootloader update to 'take'?)

Unfortunately powering off the device from the bootloader was the last time I interacted with the device. Since the N7 has no LED, I cannot tell if it is powered on or off. When I plug it into USB chargers, it does not show the 'charging' indicator on screen, and the computer I did this flashing from now sees it as 'Unknown Device', driver installation failed, so I believe it is powered on. I am going to attempt to access it via ADB on a different pc.

$ adb devices
List of devices attached

It is entirely possible that I noobed something up, and I would be appreciative of any help offered.