yashsingh1/xdaforums huggingface dataset:
[Vibrant General] junglerumble:
Any new news? Because I'm seriously considering gettjng an iPhone 5 if the next google phone is disappointing.

And the Hercules looks like **** and the screen resolution bothers me as well. And again, of course samsung build quality leaves a lot to be desired.
[Vibrant General] Emama:
Getting really upset by vibrant with the lack of upgrading support

Really want to get a nexus brand phone
[Vibrant General] Jasonhunterx:
Its all about hardware really an next Google phone should have OMAP an possibly SAMOLED+ HD 720P Res an nfc an ifs from what I last heard an go get iPhone 5 an enjoy having last years tech or 6month old by time is comes out
[Vibrant General] funeralthirst:
lololololololololol.....

boo on omap, rather have a samsung soc. guaranteed to have nfc. yay samoled+.

now, if google really wanted to impress (which they need to), and their release is on their typical schedule, meaning end of '11, this is what i want to see:

samsung screen - samoled++ hd?, but no 3d

kal-el - quad core?

ics - optimize optimize optimize, multicore support, and some ui polish wouldn't hurt

4-4.5" - i could go a little bigger than the vibrant if i had to

bigger battery - forget making it the thinnest phone ever, a little thicker + more battery life will make everyone happier
[Vibrant General] junglerumble:
no more cheap plasticy materials please!
[Vibrant General] funeralthirst:
i'll take 'cheap and plasticy' over easily breakable, and, in the iphone4's case, easily shatterable any time. in fact, i have no problem with the build quality of the vibrant. it may get hot when playing games oc'd at 1.4Ghz, but it's super light and thin. but i guess i'm much more of a function>form person.
[Vibrant General] Mirmensky:
Lovely rant. I've thought much of the same lately in regards to "official" updates. Yea it would be great but since figuring out how easily flashing can be I haven't looked back.

I was also confused when the vibrant came out and everyone kept telling me they didn't like it because it was "plasticky". I'm not sure what it was supposed to be made out of, metal, or glass or something? I came from a cheap nokia and a motorola flip before that and they were all plastic and much cheaper. The only real difference I've noticed from other phones is the thinness and the difference in heft. I've played with evo's and droids, and yes they seem a little more solid but honestly I think anything heavier will always seem that way.
[Xoom Android Development] okantomi:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
[Xoom Android Development] juDGEY2k10:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
[Xoom Android Development] pingvinen:
Of course, done :)
[Xoom Android Development] pingvinen:
This is only tested on a US device. OP updated.
[Xoom Android Development] BrokenPixel:
Will this wipe all USER data?

Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
[Xoom Android Development] bwcorvus:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
[Xoom Android Development] cam30era:
When you unlock your Xoom, it will wipe all user data.
[Xoom Android Development] okantomi:
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
[Xoom Android Development] pingvinen:
Yes it will. Read 3.4 again, it will do factory reset.

The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
[Xoom Android Development] pingvinen:
This is true, and I will update the OP to reflect that.
[Xoom Android Development] yordikins:
So has anyone followed this guide successfully yet? I don't really want to be the first...
[Xoom Android Development] pingvinen:
Hi

I did!. And you know that someone gotta be first (actually second). Why not take the credit?
[Xoom Android Development] Abracastabya:
So I'm guessing the OP has been updated? I think I'm ready to dive in :-)
[Xoom Android Development] cam30era:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
[Xoom Android Development] Abracastabya:
Sounds good and thanks B-)
[Xoom Android Development] redsat:
Tnx . Very help full .
[Xoom Android Development] rmcsc:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...

I don't know, I'm kinda lost here. Let me retry (for the tenth time).
[Xoom Android Development] pingvinen:
Try again, and remember that timing (3 seconds) are key to success ...
[Xoom Android Development] rmcsc:
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.

I'll update in a few. Thanks!
[Xoom Android Development] pingvinen:
There are no error messages or anything weird happening during step 5, is there?
[Xoom Android Development] rmcsc:
No, none. That's the thing. It flashes perfectly. Anybody would believe it works.

What build do you have? I'm just curious now.
[Xoom Android Development] pingvinen:
Build HMJ37
[Xoom Android Development] rmcsc:
Okay, so the build isn't the difference...

[Edit] I do note, however, that I have a kernel installed without having started step 6. It says it's Tiamat 1.4.2 BDRizzled. Was this installed with the recovery?
[Xoom Android Development] cam30era:
If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock.
[Xoom Android Development] drdoja:
hey if someone could help me out im really new to adb in general but i can follow decent directions. i got the bootloader unlocked and i cant seem to install the tiamat recovery when i try the command line listed in number 4 i get a access denied error i have tried unlocking bootloader but cant seem to get it working...any help would be awesome
[Xoom Android Development] pingvinen:
Well if the unlocking does not give any error message, then it is indeed strange. What software and hardware version do you have?
[Xoom Android Development] drdoja:
ok so I seemed to get bootloader unlocked and root access cause I'm able to set up setcpu and few other SU required programs no my problem seems to be rebooting into bootloader. when I try and do so i get the Droid and explination point screen I have been able to access cwm once or twice by what seems to accident. I am turning unit on waiting 3-5 seconds power button down and boot into booloader and everytime it gives me that green Droid screen....any help? btw I'm on 3.1 hmj37

Sent from my PG86100 using the XDA mobile application powered by Tapatalk
[Xoom Android Development] drdoja:
also this just crossed my mind is it possible either the boot image I flashed or the modded recovery image somehow got messed up? could I just look around for correct files and try to reflash again?

Sent from my PG86100 using the XDA mobile application powered by Tapatalk
[Xoom Android Development] pingvinen:
Try to download the ones that I link to in my original post. If they are outdated, try to find newer of the same "brand". And remember, the 3-second count-down is not a joke, not even an approximation. It need to be 3 seconds, not 2 or 5 ...
[Xoom Android Development] drdoja:
u understand the timing I have gotten many devices into bootloader although when i try this one I get that described screen of the Droid with the explunation point I am working few another hour then will be on my way home to try this. any idea where I.cab find up to date download Links btw that ka for all help and quick repkys

Sent from my PG86100 using the XDA mobile application powered by Tapatalk
[Xoom Android Development] joejens:
hey all,

I have a problem maybe someone can help. So I have been following the guide step-by-step, and now I am up to the part where I have to enter into CWM, but I cannot seem to get it right, I get options for fastboot, RSD and Nvflash. Am I doing something wrong? My 3 sec count is pretty accurate I'd say, but I cant seen to get into CWM.. Any help is much appreciated.
[Xoom Android Development] Gordon1M:
I've flashed recovery-Tiamat-R4c-100611-1150-cwm.img into recovery and this seemed to go well. I then rebooted, waited for the three seconds after the "M", pressed Vol down and all seemed still to be correct. After pressing Vol up, CWM started, but there are error messages:

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

[Edit] A bit more information. This is a record of the commands that I sent to the Xoom:

C:\Program Files (x86)\Android\android-sdk\tools>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

0288418643413457 device

C:\Program Files (x86)\Android\android-sdk\tools>adb reboot bootloader

C:\Program Files (x86)\Android\android-sdk\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

sending 'recovery' (3998 KB)...

OKAY [ 0.462s]

writing 'recovery'...

OKAY [ 1.939s]

finished. total time: 2.403s

C:\Program Files (x86)\Android\android-sdk\tools>fastboot reboot

rebooting...

The bootloader is unlocked, of course, and the device is rooted (checked with Root Check).

So far as I can see, the Xoom is still behaving correctly with a normal boot.

[Edit}

Any ideas?

Thank you

GordonM
[Xoom Android Development] pingvinen:
I am no expert on cwm, but it looks like a corruption. Try to reflash from start.
[Xoom Android Development] Gordon1M:
I wondered about curruption, but then I found a thread related to an earlier version of CWM, which referred to the same errors, i.e. http://xdaforums.com/showthread.php?t=1038870&page=10. This is a long thread (33 pages) and I haven't been through everything yet. However, it ends up with the thread being closed and the issue transferred to http://xdaforums.com/showthread.php?t=1074979, which refers to the newest version of CWM, which is the one that I flashed. So, I am not sure where to go from here.

Gordon
[Xoom Android Development] Gordon1M:
Still puzzling over what to do with regard to these error messages. When I flashed, through fastboot, I had no external SD card installed. I didn't think that this was necessary. Is this correct?

I am wondering whether to reflash CWM again, though suspect that the result will be the same. Maybe I should go back to HC 3.0.1 and start again, though I don't see why this should be necessary.

This is a Canadian-purchased WiFi Xoom that I am using, but the update to stock US 3.2 went without a hitch.

From what I have read, I think that the error:

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

refers to a partition. If so, does the CWM install set this up? Cerrtainly, I I look with ES File Explorer there is nothing with that name.

If anyone can offer any suggestions, I would be keen to hear from them.

Thank you

Gordon
[Xoom Android Development] rmarquez1974:
I am also in a quandary, I have followed the OP step for step and it worked great. Got root, got CWM, and then went through CWM to flash manta ray...it updated the recovery image to 4.0.0 and I don't have access to my sdcard...

Is there a way to get the original image back without having to go through all those steps? Does CWM have an earlier version with sdcard support?

Can I download fastboot to my xoom and run the command from terminal on the xoom?
[Xoom Android Development] Gordon1M:
Marquez - You are further ahead than I am. I haven't got a fully functional CWM yet. Was the recovery that you flashed "recovery-Tiamat-R4c-100611-1150-cwm.img"? Did you have to rename it to just recovery.img before flashing?

I seem to have read somewhere that the mount-point of the external SD card has been changed, but I don't know where I saw this. Also, I am not sure whether you have to give a mount instruction before the SD card shows up.

Gordon
[Xoom Android Development] rmarquez1974:
Gordon, the name was the full name of the recovery I found in the thread "idiots guide to rooting and flashing your xoom for fun and profit". I did rename it the first time but it doesn't seem to matter.

I reflashed it and was able to see the sdcard in recovery.

Where are u stuck?
[Xoom Android Development] Gordon1M:
Marquez - I seem to have split my problem over two threads, so I am going to focus on http://xdaforums.com/showthread.php?t=1170774&page=3. As you may see from there, I have reflashed the recovery image and the result is the same ... error messages when CWM starts.

Gordon
[Xoom Android Development] hellraiser2011:
got a problem. when I type "adb devices" nothing shows up even though I installed the Motorola drivers and rebooted. Tried different USB ports but still not showing.

Xoom was updated to 3.2 so dont know if that makes a difference.

Also tried on different computer and still now showing.
[Xoom Android Development] rmarquez1974:
Are you trying to flash using cwm? Do not have cwm update/install a newer recovery. Fastboot that recovery image again and I found you don't need cwm. Tiamat comes with an app called quickboot, use that to get back into recovery menu. I have had no problems with the original recovery image I got from the idiots thread. Cwm is nice, but it wont recognize the recovery image you have flashed and wont boot into recovery it doesn't recognize.

Use the quickboot app or volumeUP + power to reboot and after the 3 seconds the logo is onscreen, hit volume down to get into recovery.

I hope this helps you out, I have been rooting and flashing my devices for 2 years now. It does get frustrating, just have to find the steps you're comfortable with.
[Xoom Android Development] rmarquez1974:
Did you make sure you had USB debug turned on for the device?
[Xoom Android Development] pingvinen:
Good point. I will add that to the guide.
[Xoom Android Development] hellraiser2011:
Yea totally forgot about USB Debug Mode. Thanks!!!!!
[Xoom Android Development] hellraiser2011:
In Section 5 when I click to download Root file it takes me to a page with "[BOOT] Wifi-Only Charge Light Off". Is that the file for Root since I looked around on that site and found "xoomwifiroot.zip". Should that be the correct file?
[Xoom Android Development] pingvinen:
Yes, that is the one .
[Xoom Android Development] hellraiser2011:
So it is the "[BOOT] Wifi-Only Charge Light Off". Just making sure. Cant wait to try this. Thanks :)
[Xoom Android Development] abello00:
I followed all the steps up to the end of step 4.6 and now my device is at the Motorola boot screen saying:

-->Android Recovery

Entering Android Recovery Mode

Reading ODM fuse: 1

I can reboot with vol up + power on. I tried redoing step 4 a few times (which was also mentioned on other forums) and I still get the same results. Not sure if it matters but my xoom already updated to honeycomb 3.2
[Xoom Android Development] hellraiser2011:
Got all the way to 5.7. Rebooted and now stuck on the Motorola Logo. Cant get it start. Just sits there and wont shut off. Please Help.

I tried "ADB REBOOT" too but still hangs at Motorola screen.
[Xoom Android Development] pingvinen:
What happens when you press Power and Vol Up?
[Xoom Android Development] hellraiser2011:
reboots and then gets stuck on Motorola screen.

I can get into recovery but doesnt make a diffrence. Just hangs at Motorola Screen.
[Xoom Android Development] pingvinen:
Sorry, no idea how to break this evil circle. Maybe reflash the kernel from recovery, but that assumes that you can get the needed files on yccour sd card, and that cwm recognizes the card.
[Xoom Android Development] abello00:
I am having trouble accessing the CWM menu. I followed all the instructions but I get stuck at the end of step 4.

My screen boots to the Motorola splash screen and reads:

-->Android Recovery

Entering Android Recovery Mode

Reading ODM fuse: 1

I retried doing step 4 various times and I've also tried starting from scratch but I get stuck at the same step.

Would someone be able to help?

Thanks in advance.
[Xoom Android Development] pingvinen:
I remember getting the same error message once, but I can honestly not say that I remember how I fixed it. I *think* that I first considered the device bricked, but then suddenly I was able to boot into recovery again. But my memory may play tricks with me ...
[Xoom Android Development] okantomi:
So you press volume up plus power to reboot (takes you to red dual core screen), then 3 seconds later press volume down (takes you to android recovery mode...ODM fuse: 1), then press volume up again to choose android recovery (takes you to CWM recovery). Were you missing the last volume up?
[Xoom Android Development] abello00:
You ask for help and get sarcastic comments.... thanks. If you have no idea how to fix it why not just say so instead of trying to make smartass remarks. I do appreciate all the help that I have gotten from the forum but some members are more interested in poking fun at other members than actually helping out.
[Xoom Android Development] abello00:
When I press vol up again nothing happens. Is it supposed to read Reading ODM fuse: 1 ? I can try again tonight and see what happens, but I remember pressing every button hoping something would happen to no avail. Only thing that works when I'm at that screen is Vol. Up + Power to reboot.
[Xoom Android Development] pingvinen:
What did you see as sarcastic? Did you know that I wrote the OP, and that I really want to help anyone that are having problems. However that does not mean that I have all the answers.

So again, what part of my reply did you see as sarcastic?
[Xoom Android Development] okantomi:
I too am stumped as to what that poster thought was sarcastic. You went to a lot of work to create this guide (I remember!) and it is one that I send a lot of people to because it is so thorough and user-friendly.

Speaking of which, the only aspect that is a bit out of date now is that this guide is for rooting from 3.1 and many people are now on 3.2. Would you consider creating an update? I usually tell people to just substitute the file(s) from jase33's thread and his instructions for your section 5. Maybe there's a way to integrate these threads.
[Xoom Android Development] pingvinen:
I guess I could update the guide, but the original purpose was to get access to the sd card. Since 3.2 have sd card support, the guide is now becoming obsolete.
[Xoom Android Development] okantomi:
No, not at all....people need an easy to follow rooting guide.
[Xoom Android Development] pingvinen:
There is one here

http://xdaforums.com/showthread.php?t=1170760

I have tested it myself on my stock 3.2, and it works fine (note that mine was already unlocked since the previous "experiment" so I skipped the unlock part).

Used Titanium Backup as test bed for root access. Works fine.
[Xoom Android Development] abello00:
If you weren't being sarcastic, then my apologies. When I first posted regarding the issue, I posted that I thought I bricked my device. Then I updated the post saying that pressing vol. up + reset allowed me to reboot. When I read your post I assumed you read my earlier posts and were making fun of me. If it was a genuine coincidence then please accept my apologies. I won't go on about this as I feel it is taking away from the true purpose of this thread.
[Xoom Android Development] pingvinen:
Apology accepted, and thread closed. I guess that there are other threads on how to handle boot errors and defunct system images.
[Xoom Android Development] okantomi:
Well, yours is really complete and user friendly. It's ok. Maybe I'll put something together to be able to refer the n00bs to.
[Xoom Android Development] jonnunez:
hey can anyone help me out i tried this method up to step 5.7, rebooted and now im stuck @ the motorola logo screen. i was on 3.2, access clockwork. :/
[Xoom Android Development] okantomi:
Ok, so what files are you using, since you have updated to HC3.2 and the rootfile etc...in the guide is for HC3.1? This is a really complete and comprehenive guide to rooting in terms of all the prep work, clear instructions, etc. but for people who want to root from 3.2 stock, they need to use the files and method from jase33's thread as a substitute for Part 5 of this guide.
[Xoom Android Development] pingvinen:
Sorry for not being crystal clear on the fact that the guide has only been tested on 3.1, but at the time of writing this was the only available version. I have now updated the guide to be specific about the version number. In any case, the main purpose of the guide, get sd card access, should not attract any 3.2 users IMO.
[Xoom Android Development] jonnunez:
Thisis the last thing I flashed before I ended up getting stuck @ MOTO logo screen

http://www.android.net/forum/downloads.php?do=file&id=57
[Xoom Android Development] jonnunez:
Appreciate any help btw, whoever can help me succesfully beat this I will make a donation for their time.
[Xoom Android Development] pingvinen:
Sorry, no clue on what part that may have gone wrong.
[Xoom Android Development] okantomi:
That boot img looks like it was old, and certainly not for 3.2. I'm afraid that you are really confused, and I'd like to help you. If you have already updated to Honeycomb 3.2 (the newest version) you can not flash any files that are for a version prior to 3.2. You will not be able to boot. Period.

Can you please confirm your Xoom model (US/non US, wifi/3G) and the Honeycomb version you are running as well as are you rooted and what version of ClockworkMod recovery you have installed? With that information I or someone else will be able to guide you. Also, what are you seeking to do?

On edit: Re-reading this I sound condescending, but I don't intend it that way. It's just that it looks like you are mixing apples and oranges--different files for different versions and it's hard to figure out what's going on. So, I'm sorry if I have offended you.

Thanks.
[Xoom Android Development] jonnunez:
my xoom did have honeycomb 3.2, as i received the OTA update a few weeks ago. i was looking to root my xoom so i used this guide, didnt realize it was an older root guide. i followed everything exact in this guide, after flashing that root file via clockwork i rebooted the xoom to confirm it was rooted. thats when i got stuck on the moto screen and never came back from it. the recovery file i used to flash clockwork was the same one in the guide. my clockwork version is ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150) and i have a US WIFI XOOM. all i want to do is get my xoom working again. if it helps any, i did go into adb and typed "fastboot oem unlock" to see if my computer recognized my device and it did.
[Xoom Android Development] jonnunez:
and dont worry dude, i dont take any offense over the web, just looking for some help and i appreciate any so thanks.
[Xoom Android Development] okantomi:
Cool. So, from CWM recovery, do a complete wipe-user data/factory reset. You may be able to boot from there. If so you are lucky. You will still be unlocked so you don't do that step again. Then you can root using the 3.2 US WIFI method by jase33--you'll find it in the Development section. It uses adb.

If you can't access CWM Recovery to wipe, or if it doesn't work, you can wipe from adb, but you'll need to look up the commands.

I just don't remember them if I'm not using them.

I hope this helps.
[Xoom Android Development] jonnunez:
quick question, what if i try re-flashing stock image of 3.2?