yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] HuckFinn:
Sorry to be a pest but just want to make sure I understand.

A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.

B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.

C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).

Again I really appreciate all the advice.

-HuckFinn
[Xoom Q&A, Help & Troubleshooting] okantomi:
I guess that my original idea of using the idiot's guide for everything but step 5 still might work, as long as you substitute any older HC 3.1 specific files with the new ones from jase33's post.Meaning new boot image for old boot image, etc...At some point, someone willcreate a "rootboot"zip for HC3.2 but til then, jase33's way is it.

The Tiamat recovery listed in the Idiot's Guide is still valid and jase33 didn't include a custom recovery in his guide (at least I didn't see it). So I think you can install it earlier or later. I'm not sure it makes a difference, as long as you have it installed so you can flash the new kernel!
[Xoom Q&A, Help & Troubleshooting] kosenn:
I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.

.
[Xoom Q&A, Help & Troubleshooting] davidsos:
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.
[Xoom Q&A, Help & Troubleshooting] okantomi:
Your answer is more technically correct. Thanks.
[Xoom Q&A, Help & Troubleshooting] redhairedscot:
Random reboots, coming from 3.2 stock OTA

Does anybody else get random reboots in Tiamat Katana coming from 3.2 stock OTA? So far it's been exclusively a sleep-related problem; I haven't seen it reboot during active use. I'm not (over|under)(clocking|volting).

I've tried clearing cache and Dalvik cache. If it matters, I've been using the Overclocked GPU version. I'll try the Standard GPU version of Katana, but that's not a likely fix, since all the problems seem to be sleep-related.

(PS: I've read all the FAQs I could find, but I couldn't find the answer to this one: I'm coming from a Viewsonic G, and I'm used to the ability to nvflash completely back to a working state no matter what. Is there an equivalent method of restoring a Xoom to absolute stock? Thanks!)
[Xoom Q&A, Help & Troubleshooting] redhairedscot:
Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!
[Xoom Q&A, Help & Troubleshooting] okantomi:
And if you set WiFi sleep to NEVER (hardly uses any additional battery) you will not have any more random sleep-related reboots.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
CWM after rooting?

I followed the instructions in Post #2 of this thread to root my Xoom (HC 3.2). All seemed to go well. However, I have noticed that when following pingvinen's instructions (linked from Post #2), in http://xdaforums.com/showthread.php?t=1130996, to install Tiamat 2.0.0, the steps include installing CWM

before

rooting. I can't see that it matters that I install CWM after rooting and before Tiamat installation, but I thought that I had better check. Could somebody please confirm that it doesn't matter whether CWM is installed before or after rooting?

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] hchxoom:
Had my 3g zoom for 4+ months before deciding to root. The advantages I've seen in a few short days rooted:

better performance, faster booting, smoother webpages

full SD card use (write access to go along with read in stock 3.2)

ability to fully and truly back up the device

a very resposive developer community

a very knowledgeable and helpful user community (though they'll help you even stock)

a growing understanding of how this great device works

what I'm not sure of is how much effort and attention it will take to keep up with updates from the dev community, and whether tinkering with this thing will become addictive and end up consuming as much time as my original reasons/uses for buying it in the first place
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Thank you for the reply. I thought the thread had died :-)

You say:

cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.

I tried to install CWM (flash with fastboot) on a rooted stock US 3.2 WiFi Xoom. I am not clear why starting with a rooted device would make any difference for flashing a new recovery, before flashing a new ROM. Can you explain further? Nevertheless, I haven't managed to flash a fully functioning CWM. It works but with error messages, as indicated in my post at http://xdaforums.com/showthread.php?t=1130996&page=4.

Maybe I need to go back and unroot.

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] hchxoom:
1st, a disclaimer that I'm not much more experienced than you (if at all). Take what I offer knowing that.

I actually experienced an identical problem. Like you, I was working from several "guides" at once and I think the issue resultedbfrom mixing instructions for one cwm version with an earlier (or later) version. I THINK the version you have is the same as the one referenced in the guide I pasted. If you'll note his directions, he suggested renaming the recovery document to "recovery.img" before flashing it. When I went back and did that, it worked for me... then I was able to flash the updated cwm 3.2.0.0 with no errors.... then tiamat 2.0

I have no idea, though, whether there are ramifications to being rooted without a error-free recovery.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Thanks again for this ... at least someone has been through the same problems as me!

The version of CWM that I am trying to flash is "recovery-Tiamat-R4c-100611-1150-cwm.img", which is what is shown in the fastboot line in http://xdaforums.com/showthread.php?t=1130996. However, I am not seeing any reference to renaming to recovery.img. Are we looking at different threads?

If necessary, I will go back to stock 3.0.1 and un-root, but I would like to avoid the stress, if possible :-)

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] hchxoom:
I went back and found my cwm file... it is indeed thebsame as yours.

see my post #16 above, and look for the flash recovery img section. These are the instructions I followed... originally posted by Steady Hawkins on xoomforums if you want to search for the original...

I don't know why it would matter, but like I said, this little change made it workbfor me.
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
Your steps in a nutshell are:

1. put xoom in dev mode

1a. Unlock your Xoom (wipes)

2. reboot, set up and put xoom in dev mode again

2a. Flash CWM recovery

2b. Reboot into CWM (do not reboot into xoom again, it will overwrite recovery)

3. Flash Tiamat Rom from SD (do data/wipe first)

4. Win.

I used the CWM 3.2.0.0 RC4 instruction guide, and flashed the .IMG file not the .ZIP (since I didn't previously have CWM to begin with).
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Thanks for the reply cwizardtx.

I went through the whole thing again, noting your comments, but the end result was the same. After starting CWM, I still see errors, as before, viz:

E:Can't open /dev/block/mmcblk1p3

(No such file or directory)

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

CWM is showing:

Clockwork Recovery v3.2.0.0 (solarnz-R4c-10061-1150) and the CWM menue seems to be all there and also the green robot.

I don't have an external SD card inserted. Is that correct, when I am starting CWM?

Gordon
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
I just want to check someting. After the unlock, the Xoom re-boots and goes to a screen with "Start" on it and the robot etc. If I tap "Start" I then enter a series of screens that set up wifi, TZ/date/time. connects with my Google account, and restores data from my Google account. Should I allow this to happen before flashing CWM?

Also, in the instructions above, there are a couple of places where set in dev mode is indicated. I presume that this is through Setup/Applications/Development with USB debugging checked. I don't need to do anything as the check mark is already there. Is this to be expected?

Gordon
[Xoom Q&A, Help & Troubleshooting] hchxoom:
no, you enter recovery mode earlier, at the red motor dot screen (3 secs after it displays)

yes, it seems you have debug mode correctly checked
[Xoom Q&A, Help & Troubleshooting] hchxoom:
if you haven't resolved, check this article... may be helpful...

addictivetips.com/mobile/what-is-clockworkmod-recovery-and-how-to-use-it-on-android-complete-guide/
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
I had the SD card in the slot and ready with the tiamat .ZIP when I rebooted into CWM.

I didn't make explicit instrutions but i'll be happpy to try and help with any step along the way.
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
If you just wiped, and are re-setting up from scratch you should certainly not have development already enabled. But you do want to make sure it's turned on before you go back to flashing CWM.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
I may be recalling the sequence incorrectly. However, I still have the problem of these error messages and I don't know why. I am wondering whether it is related to the fact that my Xoom was purchased in Canada. I would doubt this. I "US-ized" it by flashing 3.0.1 US stock and automatically received the 3.1 and 3.2 updates.

So, I presume that what you are saying is that I should expect what I am seeing, i.e. setting up wifi, TZ/date/time. connecting to my Google account, and restoring data from that account, before flashing CWM.

This is all very strange. The procedure isn't really that complicated!

Gordon
[Xoom Q&A, Help & Troubleshooting] okantomi:
No, no, no, not correct. You must have the external SD card in your Xoom with the zip file(s) you are going to flash on it. That's how the flashing through CWM recovery works.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Thanks okantomi ... but I am not flashing through CWM recovery, I am doing a first flash of CWM recovery using fastboot .... as per the "Idiots' Guide" .... unless I am very badly misunderstanding!

I am flashing an img file of CWM, not a zip.

Gordon
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
No, it's really not.

You don't need to do all the restoration, but you DO need to get the Xoom back to the point where you can go into application settings and turn on development mode.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Yes, that's what I did .... Settings/Applications/Development/USB debugging is checked. It is always checked when I go to confirm this. It doesn't change back by itself, either.

Gordon
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
It will if you completely wipe and reset the device.

So have you flashed CWM?

Keep in mind that after you flash CWM, if you let the system do a full reboot and go back into Android it will revert the recovery which means you need to reboot and go straight into recovery, then flash Tiamat.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
OK, I am doing this again. Note that my Xoom is already loaded and I have no successful installation of CWM.

1. I unlocked the boot loader again to be able to flash with fastboot.

2. After it said that it was formatting UDA, it eventually re-started and presented a welcome screen with English, Start and a green robot.

3. I tapped Start

4. It than went to a WiFi setup screen and I tapped on the correct wifi network.

5. The next screen asked for a password, which I entered and then tapped on connect.

6. The next screen said that it was connected to my wifi network and I tapped on Next.

7. Next screen was Use Google's location service. Here, the check-boxes for "Use WiFi and mobile networks to determine my location ...." and "Use my location for improved Google Search results ...." were already checked and I left them that way. I tapped on Next.

8. Next screen was Set Date and Time. I selected the correct time zone (EST) and tapped on Next.

9. The next screen was Sign in with your Google Account and I tapped on Next (or should I have skipped?).

10. On the next screen, I entered my gmail account username and password, and tapped on Sign in.

11. The next screen said Signing In followed by a screen for Backup and restore. The boxes for "Restore data from my Google account ...." and "Keep this device backed up ...." were already check and I left them that way. I clicked on Done.

12. The next screen said Restoring and after a few sconds the normal desktop appeared.

13. I checked and Settings/Applications/Development/USB debugging was still checked. I went back to the desktop.

14. Next I booted into flash mode with "adb reboot bootloader" from the PC.

15. The Xoom rebooted and stopped at the Red M Dual Core and showed "Starting Fastboot protocol support" at the top left of the screen.

16. I flashed CWM with "fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img". The PC said:

sending recovery (3998 KB)...

OKAY [ 0.462s]...

writing 'recovery'

OKAY [ 1.976s]

finished. total time: 2.439s​

The Xoom said:

Flashing allowed for partition recovery (in red)

OneWire: Charger is not connected or battery is not being charged... (the battery was fully charged and the charger was plugged in)

Battery charge level 100%

Flashing StorMgr partition recovery STATUS: - done!​

17. I restarted with fastboot reboot from the PC.

18. I did the 3 second thing and volume down and Android Recovery appeared at the top left of the screen

19. I then did volume up and, I couldn't get all this, but it said something like "starting recovery ODA Fuse1"

20. CWM started with the proper menu and the green tiamat robot and then the usual error messages appeared, i.e.

Clockwork Recovery v3.2.0.0 (solarnz-R4c-10061-1150)

E:Can't open /dev/block/mmcblk1p3

(No such file or directory)

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log​

So, does this all look correct .... other than the error messages?

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
Hey Gordan can you confirm that you do or do not already have an SD Card in the Xoom when you boot into CWM?

Please have an SD Card in the unit with the tiamat rom .zip already ready to go and report back.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
I have a 4GB microSD card but it is not yet in the Xoom. I will have to go and look for the zip and then loaded onto the card via the PC. I presume that it doesn't matter what else is in the card, as long as there is space for the zip and it is placed at root level.

Can I use this method without CWM being correctly installed already?

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
It appears as if you have CWM properly installed. You just need to put the SD card in, because these errors are generated because CWM cannot place its cache files on SD. Solarnz sends his apologies.

The zip is easy to find, it's in the dev section. Just toss it on your card and you're set.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
OK, I have found "recovery-Tiamat-R4c-100611-1150-cwm.zip". It's the version that has been modified to skip /data/media (Internal Storage).

I presume that's OK.

I'll go and load it onto the SD.

Gordon
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
OK, I have the zip at root on the SD card. The Xoom is still sitting at the CWM screen. Should I just hot-plug it into the SD slot?

I see that there is a menu item "install zip from SD card". Is that the one I use. I presume that I will be asked to select the zip at some point.

Gordon
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
er.. uh..

yea that recovery is what you flash to recovery

then boot into that recovery and flash tiamat

the only thing you're putting on the SD card is the .zip file for the tiamat rom

yes?
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
And the Xoom is happy to accept SD cards while turned on?

I have cleared everything else off the SD card.

Gordon
[Xoom Q&A, Help & Troubleshooting] hchxoom:
it is when fully operational, but I can't say when in recovery mode... probably safest to turn the zoom off, insert, then reboot into recovery.

following on cwiz's question, do you have a recovery zip file or the rom zip file on the SD card... you want the latter and not the former
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Thanks, hchxoom. Yes, I was initially thinking that we were fixing my CWM, but cwizardtx reckons that it's probably OK. So, I did realize in the end that it is a ROM that I should be loading on the SD card!

I have downloaded Tiamat-Xoom-Rom-2.0-Manta-Ray.zip and Tiamat-Xoom-Rom-2.0.1-UPDATE. I presume that these are OK for me use, doing the main zip first and then doing the same thing with the UPDATE. I am starting with HC 3.2 US stock.

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] hchxoom:
good luck and let us know how it goes... will be interesting to see if just having the SD card in place when booting into recovery clears those errors. The only other thing I can think of is that your cwm download corrupted somehow.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Well, after all my concern with the CWM errors, all seems to have gone well and Manta Ray and the UPDATE has installed without a problem. The SD card is showing up in Storage and my 4GB card is quite adequate for the moment.

Now when I boot into Recovery, no errors are shown, so I guess it was just an installation problem, which hasn't affected functionality, so far as I can tell.

Thank you both for all of your help and to others who helped me along the way.

This is a great community!

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] solarnz:
Those errors that you were getting in recovery are exactly the ones you get when you dont have a microsd inserted.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Thanks solarnz. I did wonder about that but none of the instructions that I found mentioned the issue.

I am very pleased with the performance of Manta Ray so far.

Thank you

Gordon
[Xoom Q&A, Help & Troubleshooting] okantomi:
I'm glad you finally got it worked out. Some of these procedures don't make a lot of sense until you've done them a few times.
[Xoom Q&A, Help & Troubleshooting] Gordon1M:
Yes, what put me off were the unexpected error messages and the fact that the only references that I could find to them indicated a problem with CWM. My concern, of course, was bricking the device. If I had just ploughed on all would likely have been fine. Anyway, your help was much appreciated.

Gordon
[Xoom Q&A, Help & Troubleshooting] cwizardtx:
Glad to see you got it working well :)
[Xoom Q&A, Help & Troubleshooting] hchxoom:
cwiz - enjoyed your article/video on splashtop/zoom/htpc, by the way
[Xoom Q&A, Help & Troubleshooting] HuckFinn:
I am so glad my original post has led to so much discussion. I am planning on giving this a try very soon. I am away from my PC for the next week or so with only my Xoom and very slow internet access. Tethering to my cell over BT with only Edge coverage is pretty painful when trying to keep up with everything on XDA.
[Xoom Q&A, Help & Troubleshooting] HuckFinn:
I want to thank everyone for all of thier advice. I have finally made the jump and rooted my Xoom and installed the Tiamat Manta Ray ROM. Everything went extremely smooth as I followed http://xdaforums.com/showthread.php?t=1170760 to unlock and root, then installed CWM using the fastboot method on the CWM threadhttp://xdaforums.com/showthread.php?t=1074979 and the the instructions in the Manta Ray Rom thread to install.

I was VERY carefull to only use img files over ADB and zip files on the SD card through CWM - again thanks for the advice.

The market is busy trying to recover my applications so once it is finished I will try it out.
[Xoom Q&A, Help & Troubleshooting] okantomi:
Awesome! You'll never look back now that you're rooted.
[Xoom Q&A, Help & Troubleshooting] HuckFinn:
I will say I was pretty nervous when typing those first few adb commands, but it really is not too difficult. The harder part is setting everything back up.

I do have a question though that I have not found an answer to. Right now I am running the Manta Ray rom but with the Tachi kernel. When I flashed the kernel I flashed the stock GPU version.

Of course when I set out to root and do all this, overclocking really was not of interest to me. Now that I have the option might as well. I see there is a SetCPU paid application in the Market. Are there other options?

What are you running at and your observations, ie battery life, stability, etc. ?

I edited this post after doing some searching, but I am still interested in your experience with overclocking.
[Xoom Q&A, Help & Troubleshooting] okantomi:
I use CPU Master, set the cpu speed to 1504 which is a nice stable speed for me, and use the interactive governor. I have also set profiles for screen off, charging, low battery and high temperature...this basically insures that the Xoom is running at top performance when I'm not worried about battery use, and preserves the battery when I am. Also gives the Xoom a chance to cool off when it's been working too hard. I've tested the 1504 speed's stability and it's good, so after making a nandroid backup without the oc set on boot, I went ahead and checked "set on boot" so I could preserve my profile settings. My battery life is really good, at least 10 hours almost continuous use (some, but not all of it really taxing). I'm also using the tachi kernel with the oc gpu...it just seems to add that last additional bit of smoothness and performance. Gawd, I love this thing!11
[Thunderbolt Q&A, Help & Troubleshooting] No Pants Hero:
Ok, so my touch screen seems to be out on a small spot on the right hand side. being where the o,k,m keys would be on the keyboard, p,l, and backspace work as well as i,j,n. However, the same spot when i rotate sideways, doesnt seem to be having issues (where a,z,x,shift,and ?123 are). The problem arose about a few days into running cm7 rc1.2 mr2. The spot also seems to be present in things outside of the keyboard as well, internet browsing is goofy if i need to press in that area, as well as the lockscreen in that spot, very difficult to rotate to change to sound profile.

I have flashed other roms, stock roms, tried different keyboards off the market, everything i could think of. I just want to avoid having to unroot and return to stock, replacing the phone, and rooting, etc all over again to get back to where i was.

Anyone have any suggestions?

admins, sorry for double post in general section, thought i was here
[Thunderbolt Q&A, Help & Troubleshooting] stayin100:
Same thing happened to me the other day on cm7. A reboot seemed to fix it for now, looks like your issue might actually be hardware related though, looks like you may have to do a warranty replacement
[Thunderbolt Q&A, Help & Troubleshooting] joshnichols189:
This happens sometimes when typing.. if I finish the word it goes away, and I've heard of it happening to others as well. Yours does indeed sound like hardware though, since it occurs in more places than just typing.
[HTC 7 Pro] Prerna:
Hi all,

I see the prices for the Pro 7 have gone down dramatically (just CHF 316 today!) and I'm getting tempted to get myself one.

But I need to be sure there will soon or later be the Mango update possible.

Can someone tell?
[HTC 7 Pro] dxdy:
is no reason to mango not come for 7 Pro...