Originally Posted by chrisjm00

Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?

Assuming you have already flashed CWM, then the command would actually be fastboot reboot recovery. Not sure what but you speak of.

Originally Posted by Shano56

There's a CWM official out?

Sent from my Nexus 7 using Tapatalk 2

Yes. There sure is. If you have Rom Manager installed it can be flashed directly from there.

I dont think you can really hard brick this device anyways

I'm sitting here at the command prompt with it on "erasing userdata"

It's been a couple minutes and I'm freakin' out! How long is it supposed to take? Everything flashed correctly, if I start the device now will there be an issue?

EDIT: Nevermind, just rebooted from the bootloader in the tablet and it booted fine. I'll get the OTA to 4.1.1 and that should probably fix any outstanding little issues.

hard brick?

---

I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.

I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?

Originally Posted by chris.wueste

If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.

Pressing and holding the Volume down + Power buttons works just fine to launch the bootloader (at least for me).

No need to press (and force) the entire volume rocker button at all.

Originally Posted by nugalonious

I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.

I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?

Try and press and hold just the power button for 30 seconds or so to re-boot the tablet and you should be fine and it should boot up just fine. From fastboot you cannot go into cwm recovery because of a bug.

I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:
FAILED (remote: (FileWriteFailed))

Anyone seen that before or have any ideas to fix?

I tried wiping cache/factory reset from CMW but no joy.

Thanks. Worked for me. I did get worried when i got (data transfer failure (too many links)) error when trying to flash the bootloader.

Turns out it was the USB port. I switched the ports and all was well.

But I followed the commands in side the flash-all.sh file

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jrn84d.zip

---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------

Originally Posted by yeahthatsme

I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:
FAILED (remote: (FileWriteFailed))

Anyone seen that before or have any ideas to fix?

I tried wiping cache/factory reset from CMW but no joy.

Try the commands i posted above and see what happens

Nuts. I tried it on many USB ports and did your commands one by one. Ended up in the same spot. It happens when writing 'userdata'...