So I am just about at my wits end. I am fairly computer literate but an absolute noob when it comes to my gtab and flashing it.
I’ll try and give a step by step.
1. Got my Gtab today. I was sooooo excited!
2. Installed CWM and the latest TNT lite ROM.
3. All is well everything worked great.
4. Started up Android market…all hell starts breaking loose with “forced closes”.
5. Ok…so I shut down and restart
6. It starts what I have learned is called a “boot loop” going from the birds to the “G Tablet” screen to black to the birds…
7. I try to reflash TNT…nothin’.
8. I try NVflash, it *says* it completed successfully, but stays in the boot loop.
9. I’ve tried copying the CWM onto the microsd card (yes, command is pointing to the micro card). I then go through the Hold down the plus and start.
10. CWM *seems* to install, then HEY…right back into the boot loop.
11. I try something else and get (in little red text in the top left corner of the screen) something about “Magic” something missing.
Does anybody have any suggestions? I am a smart guy…I can read. The thing is, is that it seems like the mods and the CWM’s are completing successfully, but then I am right back in the flippin’ boot loop. I am afraid I’ve just wasted $300.
Sorry to be the dumb noob.
Pat
Did you change the partition when you installed the new rom? That was what fixed mine.
No...none of the instructions I saw mentioned that. Now I am seeing using CWM to do it but the problem is I can't get CWM to load!
if CWM is installed, you just need to hold V+ and power button when restarting. if not (and this happened to me) you should follow the instructions that were given to me by regalpimpin on this thread http://forum.xda-developers.com/showthread.php?t=1025128 to install CWM, and re partition (you will loose all the data on your internal SD card so be sure to back up) but repartition at 2048 and 0 unless the ROM specifically asks for a different partition.
You need to nvflash if you are getting the magic value mismatch. You could have gotten out of the boot loop originally by repartitioning. Only use bekit 0.8 recovery as any others will bork your tab. Dont use rom manager either.
mocheesehead,
First don't panic. We can fix this. It's REALLY hard to brick
a G-Tablet!
You have done all the right things from what you have written.
As Lisa said the one thing you haven't done is re-partition and
it seems that re-partitioning fixes boot loops most of the time.
Double check. Use your microSD with the CWM update.zip on it.
Since the command file is erased when you use it, you will need
to copy a new copy of the command file edited for /SDCARD2 back
into the recovery folder. Boot into recovery with power/volume +.
When all is finished shut down properly. The reboot as above and
see if you get CWM.
If you don't, you will have to try to load CWM by nvflash. If you
will try the above again, I will see if I can find directions for CWM
by nvflash. I know the process but will have to find the correct
command line.
*************
Just in case CWM loads: I will go ahead put the fix process here:
1. When CWM starts, go to the Advanced Menu and run the
Partition SDCARD, Fix Permissions, and Wipe Dalvik Cache options.
The re-partition takes a few minutes so
don't panic! Then go back to the Main Menu and Wipe Cache
and Wipe/Reset Factory Settings.
2. Once that is done, reboot and hopefully you will be fixed.
3. If not fixed, nvflash back to stock as per the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Makes everything -- especially the files to load -- is correct.
Keep us posted on how you do. Meanwhile I will look for the
other procedure and post it.
Rev
Hi Lisa! Yes! That sounds like my problem. I'll give it a go.
Quick question...is there a preferred format (ie, FAT32, etc) for the micro SD card?
I'll let you know how it turns out!
Thanks...Pat
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
butchconner said:
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
Click to expand...
Click to collapse
Hey cheesehead! Absolutely follow Rev's advise! I was the Guy in the thread he references above. The fix worked like a champ.
You will get it fixed, just as I did. Same issue.
Mark
Thanks to everyone for the kind and informative responses. I probably won't get to a fix til Monday morning I as I have a soccer tourney (kids) all weekend, but I'll report back when I know something!
Thanks again,
Pat
As everybody said, it is almost brick proof, as long as you follow the correct procedures. Some people don't seem to understand missing one step can make things worse. Most of these post give you step by step instructions and by finding the right one to read you can't go wrong. I'm sure you will eventually have it worked out, learning what does what and why you did that will be a big help in the long run.
Ok! So I think I am breathing again! I partitioned the card and got back to the stock UI...man...it does really blow! So, a couple of questions...
1. I flashed TNT lite, and had force close issues. Would you recommend Vegan?
2. Now that I partitioned the card 2048 and 0 like everyone said, do I need to do this again before or after I flash a new rom?
Again, thanks for everyone's kind responses!
Pat
Glad to hear you made back to stock. Here in a bit I will write a step by step how to upgrade to TNTL 4.40 for you if some one doesn't beat me to it.
Thanks JH! I look forward to giving it another go! I appreciate your help!
Pat
Pat,
Remember that the bekit 1105 is about the oldest stock UI that exists!!! Most of us
started with 2967 on our first G-Tablets.
It WAS bad and there was no Flash and no replacement kernal and TnT was at about 2.x and VEGAn was at about .beta 3.
On the other hand, we didn't miss a lot of it because we were trying to keep them
running and find out what they would do and find apps we liked!!!
When I run the latest software I just can't believe how lucky we are.....IMHO.
Rev
Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
Hey, fellas. As you may or may not be aware, I am in dire straits. Recently I had been browsing the XDA forums for the first time in a long time, and lo and behold there was a magnificence I had thought to never see in our own development forum... a Honeycomb alpha! In my haste I tried to follow every instruction to the tee and discovered that I need the stock bootloader/ROM to do this.
Well, coming from cyanogenmod7 and a first time nvFlasher, I followed the instructions from one thread to flash back to stock 3588(I think it was)? So after fiddling with the drivers for about 5-10 minutes, I start flashing and everything is going great, no errors whatsoever. Then the tablet starts to boot up and what happens? A bootloop at the TapNTap screen. So, I tried to boot into recovery thinking it might be fixable with a factory/data reset...and recovery no longer works, it just reboots back int pthe TnT bootloop. And then I came to the this forum, particularly the Q&A, to ask one question...
Is my G-Tablet well and truly forked?
Sincerely, this guy.
[edit]P.S I am also currently trying a bunch of stuff atm to see if I can fix it myself, but just reply if anything I do is futile and I should consider recycling my new hunk of silicone and plastic.
Load cwm .8 via update.zip and repartition your tab. Then try nvflash again.
"Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared. "
Or try loading it by nvflash with instructions from this thread
http://forum.xda-developers.com/showthread.php?t=1058649
Here is a thread on how to easily flash to the 1.2 bootloader.
http://forum.xda-developers.com/showthread.php?t=1039000&highlight=guide
Holy heck, thanks man. Do you have a paypal or something so I can send you like 5 dollars?
Nope, just mash the thanks button ;-)
Good luck!
No offense to the OP, but from my observations it seems that NVFlash is more of a breaker than anything. Everybody says to know NVFlash in case you end up with problems...that's fine, people can apparantley use ot to help fix errors that may have happened...
The fact is, most of the "I've bricked my G-Tablet" posts usually contain the line "So I NVflashed..."
I know that the developers use NVFlash for it's ease of use to go between roms, and see what it is that they need to see (I've never used it, so I don't know)
The fact is, the instructions that Mantara posted do not require NVFlash at all. In fact, after flashing 3588, they don't even require CWM.
If I ever softbrick, THEN I'll mess with NVFlash...but until then, it seems that NVFlash might actually cause me to have my first softbrick.
Nvflash is a handy tool to have and yes it can cause errors. Most of the time those errors occur because the partition table on the tablet don't match the partition table for the Rom being flashed. About half the gtabs have different partition tables from what is considered standard. That's why I have been pressing the issue of repartitioning when you first get your gtab and also when you move from 1.1 to 1.2. It helps make sure your tab and the software are on the same page.
I'm stuck in a loop. I flashed CWM. Then proceded to partition. I followed GoodIntentions web page to the letter untill I got to the fix permissions. As soon as I executed it immediately said fixing permissions...Done! I was waiting for some on screen instruction but damn that was fast and it said "Done!" It then highlighted reboot recovery so I executed. Then it said booting recovery kernel image and took me right back to the first CWM menu then highlighted reboot system now. So I executed and it said again booting recovery kernel image and highlighted reboot system now again.
There were a few things that were odd to me during the CWM flash.
1. I already had a recovery file in my root directory of my gtab. I had to do a factory reset on the 11th because of something my kids did. Note kigs no longer play with gtab. The file was a text file so I thought that it would be able to tell the difference when booting. Maybe an issue, maybe not, just putting that out there.
2. The gtab never autimatically rebooted after CWM install. It did highlight the reboot option so I pressed the home key to execute.
3. There were no on screen instructions in the fix permissions. It just said "Done!"
For information purposes I am providing my bootloader version and CWM.
- Bootloader 1.2-4349
-ClockworkMod Recovery v3.0.2.8 (GTAB 1.2 and NI Adam rev5)
HELP!
When you reboot the system, make sure you reboot the right option. There are 2 reboot options in CWM: (a) reboot system and (b) reboot CWM. Whenever you're done flashing a ROM or fix permission, CWM will automatically highlight choice (b). You need to press the back button to go back out to main menu and choose reboot system.
I did both
I did both and it still loops me back to the CWM main. At the root menu "reboot system now" is on the top and "advanced" is at the bottom. Reboot system now is highlighted so I execute then it shows me the birds and the kernel image message. Then I'm right back at the CWM root menu. The only thing I did was partition and fix permissions. The fix permissions just said done as soon as i hit they button. There was no instruction beyond that.
How did you flash in CWM?
I'm guessing... oh gosh... tell me first how you flashed in CWM.
While I figure out what's going on, have you checked to see if the volume + button is stuck?
it's not stuck. I'm able to change highlighted options.
Ok, try this. When you're in CWM, do a data wipe.
OK doing it now.
ok I did it. it says data wipe complet and took me back to the root menu
What next?
Well, after data wipe then try to reboot system.
PS - we're trying to solve a problem over in development. Sorry, I'm distracted.
nothing, still doing the same thing.
No problem. Im just stoked someone is willing to take the time to help me out. I joke at the term dummies cause I'm ignorant to this new technology. But so you know, I'm exmilitary MI so I'm very anal about following instructions. I know I did this to the letter so it blows my mind as to what went wrong. Your web site is very thorough so I have to believe that it has something to do with that damn recovery text file that was already in my root directory before I unzipped the other. Just a thought.
It appears that somehow your boot image has been replaced by CWM. Without delving too much into details, visit my page on nvflash and nvflash your way out. What rom were you running before you put cwm in?
Added by edit.
On second thought, yes that recovery file might have something to do with it. Without knowing what it is, I can't really tell you what it did.
You should just flash in a new rom using cwm.
Added by edit again.
You're not going to sniper me are you? If so, I'm x-cop... almost won the damn marksman competition, too.
HA HA no sniping. But it is good to know I'm dealing with another person that has life experience. I was running 1.2-4349.
1.2 stock rom?
yeah 1.2 stock ROM
If you still wanna use stock rom, then nvflash back to stock rom. Look at the nvflash page of my website. If you want something better, I highly recommend the calkulin+clemsyn combo. It's in my rom page. The whole process should take you about 20 minutes and then you will have a tablet that's 10 times faster and smoother. Also, your kids will be able to play with it and you won't have to worry about them messing it up. Trust me, man, you'll be a lot happier.
PS - we got the problem solved in the development section. Good thing, too, because I'm about to go on my nightly run.
Added by edit.
Actually, go to start here page. And choose "You bricked your gtab and now you are freaking out."
The way I understand this is that I have to flash back to stock ROM first. Then install CWM. Then install the new ROM.
You are the man. Thanks for all your help. I'll give this a shot and post how it turned out. Enjoy your run!
I have followed you instructions on the web site to the letter. I tried it several times and each time it stops booting at the birds screen. I went back and restored it using the backup file I created during the flash. That Part D has me a bit confused. I don't understand why you choose "install zip from sdcard" in step 1. Then what seems to be some reformatting when you "Choose wipe data/factory reset" in step 2 and "Choose wipe cache partition" in step 3 and "Choose Wipe Dalvik Cache" in step 5. Then you "Go back out and choose install zip from sdcard" in step 6. The only difference that I can see is that you expand the step by explaining how to find the zip file in the following steps. I have done it by the letter several times and I've also tried it other ways. As I'm typing this my tablet is still on the birds screen. I'm almost there. I can taste it. I just need a bit more guidance. As a note I will tell yousince I've had to do this the hard way, I'm not in the least bit intimmidated by this process. And I can do it with some speed now. Thanks GoodIntentions!
I have done some additional reading in the forums and discovered that this considered a soft brick. I do a CWM restore and everything goes back to stock and works fine, but each time I try to load Calkulin_Clemsyn Combo Overclock it locks at the birds during boot. I already nvflashed in case you don't remember. I can go back and do it again, but I'm at a loss. I'm not sure if it would accomplish anything more than my current result since I had already done it. I really don't know where to go from here. I also read that Viewsonic may have locked the bootloader to keep us from modding the Gtab. Which makes no sense cause modding is really the only thing driving the sales for these things. Even if I were to nvflash this thing again whose to say it doesn't do the same thing. I haven't seen a fix or workaround for this anywhere once it's been nvflashed again. What do I do from here?
I'm having the same problem here.
Hey, Folks
Let me say that you guys are the best. I have tried to follow most of the things you have done with gtablet, and they are amazing. That said, I have tried every thread I could find and have not found a solution to my problem. I completely bricked my gtab. All I can get now is the bird screen with "booting recovery kernel image". It won't go any farther. I've tried NVFlash, clockworkmod, droidpirate and whatever else I could find. The tablet won't recognize my micro sd card. So do I put the tab on my fishing line and go back to the store for another one? Thanks for you help. Sorry If I'm rehashing an old thread, but I've really tried all I know to do.
Have you tried my website? I'd say you're a code red.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
A Code Red sounds like a good idea, especially since it asks you to use the one that replaces the standard recovery partition in the image with a CWM partition.
The only other thing that comes to mind would be the possibility of a recovery folder (with command) on the root of the internal memory that is telling the tablet it needs to run update.zip... and then something being wrong with an update.zip that's there.
Also, go ahead and take your microSD out if there's some concern about it not recognizing it (just in case the command and update.zip are on that).
Thanks, Ted
But, I'm reasonably sure the problem is with the recovery file on the gtab. I probably erased it when I was trying to install the Honeycomb update. I've tried nvflash. It worked once before and did re-partiton the tablet, but now it won't do the same thing.
Thanks, Gentlemen
I'm going to try goodintentions step by step directions again. Sometimes these things are all just a matter of how you hold your mouth. Maybe after a few dozen times I'll get it right. Thanks to you folks, I really loved my gtab. I had it mod'ed to gingerbread and it was great! I just couldn't leave well enough alone and had to try honeycomb. I promise if I ever get it back to where it was, I won't mess with it again. (Sure I won't)
The thing with honeycomb that I have discovered is that if you don't wipe the data RIGHT AFTER nvflash you will not be able to boot up the new rom you just nvflashed. Nvflash doesn't wipe data. And there's something in the honeycomb data that interrupts the normal boot process of other roms.
So, in the code red procedure, the most important part is wiping the data/factory reset RIGHT AFTER nvflash.
For some reason, people keep ignoring this step even though it's written right there. Like I said at the top of that page, do not skip any step.
goodintentions said:
The thing with honeycomb that I have discovered is that if you don't wipe the data RIGHT AFTER nvflash you will not be able to boot up the new rom you just nvflashed. Nvflash doesn't wipe data. And there's something in the honeycomb data that interrupts the normal boot process of other roms.
So, in the code red procedure, the most important part is wiping the data/factory reset RIGHT AFTER nvflash.
For some reason, people keep ignoring this step even though it's written right there. Like I said at the top of that page, do not skip any step.
Click to expand...
Click to collapse
Good Intentions
You are the GRREAATISt! I followed your instructions, and they worked like a charm! I had already done something similar before to no avail, but I erased everything and followed your guide to the letter. I couldn't figure out how to get back to this message forum, or I would have thanked you sooner. How do I contribute to your beer fund?
I have a G-tablet that belongs to a friend. When they first bought it, I used Clockworkmod and installed Vegantab. everything worked great for a few weeks and then she said apps started randomly force closing more and more till it got to the point it was unusable. She didn't use it at all for a few weeks and now it will not get past the Viewsonic flash screen (3 Birds).
I got it from her and have tried everything I can think of to get it into any kind of boot or recovery screen. I used a new SD card (formatted) and then copied several different recovery files on to it. Hold Volume + and Power up.. Nothing. Still will not go past Viewsonic screen. Another SD card (Formatted) Copied ClockWorkMod v8 (Unzipped, Command file and update folder to the root, Nothing else on the card). Hold Power and Volume +.. Still nothing.
Any suggestions?? Will gladly paypal enough to buy a few drinks for anyone that help me out here.
I had the same trouble, If your GTAB is not broken (hardware issue) then follow this basic procedure located at:
http://forum.xda-developers.com/showthread.php?t=892090
You will need an update.zip so you can download zip files from Viewsonic's TNT page and just rename them to update.zip.
If this process does not seem to work then you will have to setup what is called NVFLASH and you will need APX drivers to do it, you can use this link to find the instructions and pertinant links:
http://forum.xda-developers.com/showthread.php?t=861950 I have used this and followed exactly and was back on old stock rom. I ADVISE YOU TO READ AND REREAD this post then make sure you have all files and drivers before completing this, then you can go through the process and after that restore CWM recovery and go from there.
This is to restore the 1.1 BL along with stock 3588 image... if you like you can just get all stock updates to get you to the 1.2 BL as well then move on from there.
Basic instructions after the NVFLASH operation is succesfull to get back to CWM:
http://forum.xda-developers.com/showthread.php?t=865245
I hope this helps and props to roebeet, TeamSpeed, rr5678 and scsione889 for all the linked posts.
EDIT:
You may want to run this prior to any NVFLASH operation you do:
http://forum.xda-developers.com/showthread.php?t=974422
And only use this to format uSD cards. Time and again installs or fixes fail due to a bad format. Not saying that is the issue but always best to start with a good format.
Why don't you just nvflash it?
Google "nvflash for dummies" and follow those instructions, it might seems scary, but you just gotta follow the instructions correctly and everything will work out. This will return you to the stock tapntap rom.