[Nexus 7 Android Development] SteveC485:
Well, after several very frustrating days with little success with either this or mskip's tool kit I finally got to root. Many of my issues are mirrored in some of the frustrations posted here. So for a little perspective I was using a Windows Vista laptop to do this with. It started out that I could do everything but actually root the device, the Su and Busybox would not push through the process to the device. It would do everything else, except flash the older bootloader which I initially thought might be the problem, but it would get to the fast boot screen with the message it was booting the image and would stick there, multiple tries, even letting it sit over night 8+ hours and the toolkit was still waiting for the device to reboot. Everything else worked, driver installation gave me the success sign, it would backup and restore, it would relock the OEM boot loader, it would flash stock, it would unlock...everything, but it would NOT give me the SU or BusyBox, and would NOT flash the older image. The more I tried however, the funkier things got...some of the above would suddenly not work, where they had before. I was ready to scream I was so damn frustrated. I finally got around to the thought that right after I had bought this and before rooting had become a serious thought, I was going to just get used to the thing first and see if it would do what I needed without root, I did flash the new system update, 4.1.2 (the one with the Z in the build #). Well then I could not get it to flash tha 4.1.1 factory image, which it did once. I was beginning to wonder if I had a Nexus with some issue as mskip's kit did no better. The best I could get with the laptop was stock 4.1.2 with an unlocked bootloader with backups.

So I figured maybe the problem was with the laptop or the initial installation having a corrupted file ot two. I uninstalled the WF kit and reinstalled a new download and same old crap. At this point I figured maybe the 4.1.2 was not rootable, although I didn't see much evidence for this. Anyway I went to a Windows XP desktop installed the WF tool kit. I did a backup, successfully flashed back to stock 4.1.1 (which I could not get done on the Vista machine). I went through the whole routine on the last 4.1.1 build listed in the kit and bang everything worked like a charm. Let me tell you I was a happy camper when I saw SU and BusyBox icons in the app drawer!!! So maybe the issue is with rooting 4.1.2 or What I think I have is a laptop that is on its way out, it was doing some other stuff it has not done lately, but I'd sure try a different computer if you are having issues. I also got root without flashing any custom recovery and for now used ROM manager to get CWM. I'd rooted android stuff successfully in the past on both machines. SDK is on both.

I now have a decision here. Do I try to let the new 4.1.2 system update through and hope it will re root (I'm not real anxious to try all this angst again...once bitten twice shy I guess) ? or do I flash a 4.1.2 ROM and forget the OTA...the latter is where I'm leaning at the moment.

So if I accept the system update to 4.1.2 will the tool kit root that build?

At any to Wug Fresh, thanks for your time and effort on this, I'll come up with a donation :).