[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Citi,

It's not likely that anything you did made it any more of a "brick." Unless you've been mucking about with root level command line stuff the tools you've used are safe enough to prevent you from doing any serious harm. Even if you have there are ways to get it going again if there isn't any physical damage to the device. Which is why I'm thinking you might actually have a hardware problem.

At this point I would make one last attempt using the standard tools doing the following.

1) Delete everything related to nvflash from the computer.

2) Re-Download all files necessary to make a clean nvflash installation including bekit's 1105 image.

3) Redo the nvflash

4) Get a clean copy of ClockworkMod .8 MicroSD install

5) Install from the MicroSD if at all possible. If it won't install that way, do not modify your nvflash config file. Flash only partition 9 with the CWM image. If you aren't sure how to do that I'll send you the instructions.

6) Boot into CWM, clear cache/data, clear Dalvik cache, and re-partition 2048 and 0

7) Re-nvflash the bekit image one more time.

8) Do a factory data reset from the system settings or through standard recovery.

This may seem like overkill but here is my reasoning. First, There are two layers of partitioning happening here. The flash memory is first partitioned into a 2 gig "System" space and a 14 gig "Storage" space. nvflash then partitions the "System" space into additional sub partitions for the Android OS. Since we have two different tools working at two different "levels" of partitioning we want to make sure that both partition tables are clean and accurate. Without knowing exactly how the flash memory is managed in the gtablet this was the only method I could come up with where I was sure that would happen and it should also leave the tablet in a fresh from the factory state.

If this doesn't work then there is some chance that more can be done with ADB and some command line tools that require root access. However, the chances for success don't really increase much and the risk is far greater since a simple typo can have fairly serious consequences. Knowing this I'm very hesitant to suggest trying that level of work remotely or without the appropriate expertise (which I do not have at this time).

One last note. You'll find that I harp on certain details. Specifically the version of the images, drivers, etc. Some don't think this is important. I can't stress this enough... I have never failed to recover my own tablet from any situation using the tools I recommend and they have worked for many other people. The details are important. There are lots of other images, multiple versions of nvflash, different drivers. Any deviation no matter how slight can cause failure. In fact, I usually try not to get involved with helping folks that are using Windows for the simple reason that I don't use it myself so I can't test drivers and software changes that are Windows-centric and that introduces uncertainty.

All that being said... I don't give up easily and will find a better solution to this issue. Others are working on it as well and I'm staying in close touch with them.