Database Info

[Q] Clockwork Recovery problem

First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.

The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.

Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.

[Q] GTablet not booting after attempt to load TnT Lite ROM

I was in the process of flashing TnT Lite v5.0.0 on my Viewsonic Gtab and all was going well. Got the Viewsonic screen, then the message that a recovery key was pressed and then booting recovery kernel image. Then the screen changed to a graphic of a package being updated with a progress bar.
Unfortunately, I let go of the Power and volume + key before the progress bar finished. When I realized I had to hold the key sequence longer, I quickly tried pressing both the Power and volume + key sequence again. This led to the screen turning black and then I got the familiar messages, "Booting recovery kernel image."
From that point it hangs indefinitely.
I did ensure I was using TnT build 3588 before I attempted flashing with TnT Lite 5.0.0.
Is there any way to recover from this state?
Any help is appreciated in advance.

Actually once the recovery starts you can release the buttons.
You're most likely going to have to use NVFlash to flash a stock ROM. Update that and then reflash 5.0.

sabre2002,
A number of folks have had problems with the 5.0.0 install. But the advice Cannibul gave you about holding the buttons only until the recovery starts is good.
You will need to use NVFlash to recover -- and that's not too bad except that you need to be prepared and understand the process.
First, go back to Roebeet's original 5.0.0 thread and read all the parts of the instructions about "what if problems happen" again.
Then go to the NVFlash Recovery thread:
http://forum.xda-developers.com/showthread.php?t=861950
and read it thoroughly. There are a couple of links in it to threads where several of us describe exactly how to get the stuff, set up and nvflash your
recovery.
Good luck to you. Know that a bunch of folks already have done the same thing,
so all is not lost.
Rev
P. S. -- There also is a thread I put near the top of the Developer Forum that provides additional info on the USB Drivers for the nvflashing if you need it.

Thanks, butchconner.
I found an earlier post of yours where you provide step by step instructions on using NVFlash to recover the G-Tablet to an old image.
It worked perfectly including getting the USB drivers for recognizing G-Tablet in APX mode (I was having difficulty with this last night).
Got the tablet up and running but had problems applying the TnT 3588 build update. However, I'll retry and re-read Roebeet's post as you suggested.
Thanks again for your help.

Update on progress
Ok ... I had a heck of a time getting the TnT build that was contained in the zip file from roebeet's post (http://forum.xda-developers.com/showthread.php?t=861950) to update to the necessary build 3588 in order to apply the TnT Lite v5.0.0.
I tried multiple times, but each time the 3588 build update would error and I would have to nvflash all over again.
After a couple of times with this error, I decided to try the TnT update.zip provided in another of roebeet's post:
http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
I copied all of the image files in the same directory where NVFlash was located on my Windows PC. It overwrote the bootloader.bin and the system.img and added 2 others (recovery.img and boot.img).
Ran the nvflash_gtablet.bat file again with the updated images and the gtab came back up as usual and it told me that it had been updated to build 3588.
However, don't believe it because when you check the Settings for the build number, it still shows an older build (2367 I think but don't quote me).
Clicked on the TnT Updates app and was prompted to download and install the build 3588 update again.
This time the update worked like a charm!
Not sure if this is really a useful workaround, but thought I would include it here just in case.

sabre2002,
When you do the nvflash as several of us have documented using Roebeet's files, your at the 2638 update.
Most of us have found that if you just activate the wifi on the 2638, VS Update almost immediately offers the OTA 3588 update from VS. Just let it download and install.
If not, the downloadable version of 3588 is in Roebeet's 5.0.0 thread I believe and you can put it and a new recovery/command file on your /sdcard and the power/volume- into recovery and install it.
Glad to hear you are on top of it all. Of course, I think all of us that "play" with these things really deep down inside know we are going to keep doing things and changing things around ------and some day something will happen again!
Rev

Loaded TnT Lite v5.0.0 successfully
I have TnT Lite v5.0.0 flashed on my Gtab now ... it's very nice. Much smoother than the stock TnT and access to the full Market is worth the price of admission.
Thanks for everyone's help ... it was fun flashing the new ROM and now I am familiar with nvflash in case I need it in the future.

FYI, TwoTapsX (TNT Lite 5.x) flip-flopping - latest is that it's pulled again

(At the request of management). Even with all the unsticking / mod intervention and warnings up the wahzoo, there are still a lot of user problems. It may return in a week , but for now it is PULLED. The moderators have hidden the thread, at least for the short term.
For those of you on TNT Lite 5 / TTx, just keep using it and no worries. Once we know where VS is headed, I will have a plan to either ask you to downlevel or upgrade. Again, depending on what they do.
EDIT: For those of you who had issues, could you please write up the steps you used before it failed? It would help everyone to understand why there are so many problems with this 3991 stock / TNTL 5 / TTx. From the posts and PM's I've seen, the majority have been either:
1- The device was flashed with clockworkmod to 3991/TNTL5/TTx and gets stuck at the birds or
2- The device was being prepped to stock 3588 and recovery was broken, after the 3588 reversion.
But I'm hearing that others might have applied all the proper steps and still had problems. We're trying to gauge just where the problem lies with this 1.2 UAT of Viewsonic's.
From my own device, I know that clockworkmod flat-out does not work. That's because the BCT partition is being touched by standard recovery, which clockworkmod does not replicate (and seems to be required). But as long as I have a clean 3588 stock ROM running on my device, I have not had an issue upgrading to 3991/TNTL5/TTx, it has worked for me 100% of the time.
Stock 3991 / TNT Lite 5.xx / TTx .9x backout instructions:
There are two way I know of to back out of these:
- Flash to stock 3588. This assumes you have NOT added clockworkmod and have standard recovery. I have done this several times and never had a problem. Stock 3588 link: http://forum.xda-developers.com/showthread.php?t=842000
- nvflash using bekit's 1105 image: http://forum.xda-developers.com/showthread.php?t=861950. This is still the best way to back out, as far as I'm concerned. You can do a full erase first, to wipe user data as well, thread is here: http://forum.xda-developers.com/showthread.php?t=974422

NOOOOOOOOO. Hopefully VS will decide what they are going to do by the end of the month. I am enjoying TnT Lite 5.0 with no issues at all. Thank you for all your hard work Roebeet, it is unfortunate that so many have had problems with this.

Damnnn, was about to install it
Really sucks that people have had problems maybe people should read and then re-read instructions instead of jumping into things and just assuming devs and mods can help them out. They have a life and dont think that after putting in all the work in to create something they want to hear from whiny a$$, irresponsible people that probably caused their own problem
Now people, like me, that wanted to install cant. nice.
thank roebeet tho and all the other g tab devs

I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.

One of the obstacles I've had in the last 2 weeks is that this is a UAT, not a released firmware from Viewsonic - so its validity is in question (and understandably so). If they release it with the same bootloader and upgrade requirements, it's going to shake things up here a bit.
I still think the odds are that they will - from their standpoint, they are only supporting stock users so, as long as they can ensure that a user is on 3588 stock, then the upgrade should work. In our case, many of the issues were either getting from a mod to 3588 stock, or using clockworkmod by mistake. Viewsonic doesn't have to worry about either of those issues.
But, there's still the X-factor -- everything is 3588 stock and the upgrade still fails. That might be what's holding them back.
bkbrod said:
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
Click to expand...
Click to collapse
No, clockworkmod won't work (even the new one) - if you wanted to backout to old stock (3558, for example), you'd have to use Viewsonic's recovery. Clockworkmod will kill your device, trust me on that. nvflashing to bekit's 1105 also works, that's how I've been backing out to old stock.

Hmmm
In the last 24Hrs, my gTab v.9.02 just decided to go totally nuts. Constant FC's, lockups, lost sound. Tried every fix listed on XDA, wiped /data , re-downloaded apps from Market instead of restoring with TiB; wotked for a little bit, then the same FC's. And random loss of sound.
Going back to 3558 and CWM and 4.2.5.
We'll see what VS throws our way.
Keep up the good work Mr.Roe!!!

roebeet said:
The backout, btw, is the same -- run stock 3588 and it will downlevel you back to the old bootloader. BUT, make sure it's standard recovery and not clockworkmod.
Click to expand...
Click to collapse
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.

TwoTapsX works great for me so far. Had TNT Lite 5.0.1 but it wouldn't run some apps correctly. Tried all the ROMS and they all had sleep of death problems. TwoTapsX works the best for me without giving any glitches.

TwoTaps .9.2
Thanks Roebeet for all you do here. I am finding this ROM easier to work with than any other. I have noted that periodically it will flash the home screen while I am working. Mostly this has been while in Dolphin Brower HD.

jholmes5 said:
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
Click to expand...
Click to collapse
Good point, since the other thread is hidden.

So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!

P00r said:
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
Click to expand...
Click to collapse
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.

manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It does not... if you install a custom boot animation it stay there... so it's not full even if after the unit doesn't even start (red text) it's not fully wiped...
I have used clockwork with the partition option, this seem to perform a full format with either the nvflash format or bekit recovery but I am not sure why we can't get this done tru the nvflash...

manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It's in my first post, as well. Run that nvflash first to erase the device, then the bekit 1105 nvflash to complete the process.
What seems to happen is that the old stock / new stock user data setups are not compatible. When going to new stock, it's not so bad because new stock has a better recovery. But when reverting, old stock has a crappy recovery with no user data wipe options. Even Viewsonic understood the limitations which is why they changed their recovery in this UAT of theirs.
I mentioned to jerdog that I wanted to see if I could port their new recovery to old stock (using an old kernel). If that works, we could conceivably offer a "bekit 1105 enhanced" version that adds it. This is better than clockworkmod in that it's the vendor's own recovery and includes the ability to wipe user data, calibrate the device AND update / downlevel the bootloader. For the purposes of getting users backed out if needed, it might be a critical piece of the puzzle.
EDIT: No go. The recovery functionality is actually IN the kernel, my bad. So it can't be ported over. Oh well.

You guys are GODS at this. Simply amazing what you are all doing with this G Tab. So I guess I'm one, of some lucky few, that ACTUALLY READ the install instructions for 5.0 and 5.0.1.
Glad I did because I love the market on this thing.
Eagerly watching what happens with Viewsonic......Any chance they did this as a step to make a Honeycomb upgrade easier? I doubt it since the original G Tab with OTA updates is still crippled.

First off just want to give my thanks to roebeet and the devs here at XDA. I've been running TnT Lite 5.0 / TwoTapsX ??? since the day I bought my Gtablet on 3/11 with no problems. On Friday the 11th I was itching for a Xoom somehow managed to find out Staples had the Viewpad 10 but not in store and somehow managed to end up finding out that Office Depot had the Gtablet for $379.99 in store. I read roebeet's at the time TnT Lite 5.0 thread several times before walking to my nearest Office Depot and brought home a Gtablet within minutes of reading that thread.
Out of the box from 2967 I went to 3588 through stock recovery and not OTA; and then did the same thing to go to TnTLite 5.0.0
I have successfully backed out of TNT Lite 5 in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
Click to expand...
Click to collapse
My question to roebeet or anyone who has gone from TnTLite / TwoTapsX back to 3588 using stock recovery. I could swear the above quote from roebeet had an additional line about using stock recovery to run the 3588 stock rom and then wiping user data from stock recovery. From TnTLite 5.0.0 can I go back to 3588 using the stock recovery and wipe user data with the stock recovery after running 3588 but before rebooting?
Android system recovery <3e>
Wipe Data/Factory Reset
Wipe Cache Partition
Click to expand...
Click to collapse
If it is possible to wipe user data after flashing back to 3588 do I need to just wipe data or do I need to use the 'wipe cash partition' as well.
edit: never mind my rambling probably better to wait until we know what Viewsonic is going to do and at that point roebeet will let TTx users know how to proceed from TTx to whatever comes down the pipe from VS

I did have a line (I think in the TwoTaps thread) about reversion and wiping data before you reboot into 3588 stock. But, I tried this once myself and it didn't work.
Maybe I should make a special 3588 "mostly stock" with clockworkmod, as a backout solution (so that, if you get into a bootloop situation post downgrade, you already have clockworkmod installed to fix it - that could work). It's the "wipe data" option, btw.
But first, lets see what the vendor does - if they stick with this new bootloader then TNTL5 / TTx users might already be one step ahead of everyone else - you may not want to backout.

Using it since first release with no problems. I always read the entire first post as well as user issues prior to updating. There are probably many users that try before reading which can lead to issues.
I think this is a great ROM.
Sent from my GTablet-TwoTapsX using Tapatalk

I'm one of the ones who ran into troubles getting this to load and I honestly believed I followed all the instructions when doing so. I've tried mostly all of the custom ROMs and was on the Vegan experimental before loading TTx. Not sure what the problem was but nvflashing with or without recovery didn't take. Kept getting stuck in APX mode. I wasn't really worried since I could always get the tablet to take the nvflash so I just kept playing with it until lo and behold, I was able to enter the TTx recovery mode. Been working fine since. I really like this ROM but I definitely feel like the disclaimer is justified - if you're not into tinkering this isn't something you wanna try.
The only problem I've run into so far is that when I recover my Angry Birds file and run the app it FC's. Runs fine if I just install either version, but when I try to restore my saves by using TB, the app refuses to run. Weird. Other than that, no problems. I don't really like the default browser, but understand that it's required at this point. FLash works fine and I haven't had any issues at all with the market. Even found a few apps that were supposedly only available with XOOM builds.
Many thanks Robeet and hopefully we can get a more "idiotproof" upgrade process.
T

roebeet,
Where can we obtain the bekit 1105 file?
I remember seeing the name somewhere but don't remember seeing the D/L source.
Rev

GTablet Experiences

I originally purchased a GTablet from the original Woot! sale based on reviews during that sale that this was a wonderful tablet once a new rom was installed. The first tablet I purchased as a gift for my wife. I received it on a Friday after I got off work. Within about an hour, I was up and running with TNT Lite, a fully functional app market and Adobe Flash Player.
I primarily followed this guide from these forums. I had zero problems and everything worked flawlessly following the guide.
I was so impressed with the tablet, when it came up on Woot! again, I decided to purchase another one. This tablet arrived quickly, and by all appearances was the same as the tablet for my wife. I checked the stock OS, installed the OTA update and verified I was on 1.1 3588. I proceeded to follow the guide again and ran into problems immediately with the app market.
I used the basic app market fix listed and no matter how many times I did it, I couldn't see the majority of apps. I then began looking around the forums and found this guide for the titanium backup method. I followed this exactly and still the market wouldn't work.
I found one more guide (can't find the link now) that instructed me to edit files on the tablet to known working configurations. I grabbed the files and they already had exactly what the guide was telling me to change to. So no luck there.
I then remembered reading that some Roms had a working app market out of the box. I figured I'd try VEGAn or Cyanogen Rom instead of TNT Lite to see if this fixed this problem. This is when I ran into another brick wall. I was completely unable to load these Roms on my tablet. After performing the install in ClockWork Mod and rebooting, the tablet would get the ViewSonic screen with Birds and never complete the boot. I left it on that screen for as long as an hour and still nothing worked.
I came back to the forums looking for more information. Buried deep in the VEGAn 7.0 thread I found a gem from someone who had a similar boot problem (they made no mention of market problems). This person said they were able to fix the boot problems by using NVFlash to restore the tablet to original settings and pointed towards this thread as a possible fix.
I followed the steps in there directly. I was hung up for about 20 minutes trying to figure out how to use NVFlash and ClockWork mod until it dawned on me that accessing for NVFlash was used with the Volume Minus button instead of the Volume Plus button. So if you are confused in that section, keep in mind they use different power up methods and don't conflict.
After using NVFlash and restoring back to the original settings I was able to get into the stock rom. I tried the OTA update immediately and it failed after the download. Restarting the tablet fixed the problem. After you are able to boot back into the stock rom, I recommend a restart just in case. Then do the OTA 1.1 3588 update.
I then followed the original guide again. This time, everything worked as expected. Using TNTLite and the Market Fix worked the first time. I formatted and installed VEGAn and it worked on the first time too.
I decided to make this post as a thank you to everyone out there who works on these ROMs and everyone who has posted fixes to their problems. Hopefully this will help anyone else that is having problems.
My wife and I absolutely love our tablets and this wouldn't be possible without the fine people here.
TLDR;
Market was broken and known Market Fix didn't work. Used NVFlash and it fixed it.
NVFlash uses Volume Minus not Volume Plus
Restart Stock OS after first boot before installing OTA update

Thanks for posting this. I plan on switching to vegan from tnt lite soon. This is good info to know ahead of time.

Thanks for the info from someone who is waiting to theirs in the mail.

Pushing Recovery on 3.2.6

Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks

DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.

after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.

Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.

DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way