Idiot's guide to flashing the Xoom (for fun and profit)

pingvinen · Aug 1, 2011 at 8:19 PM

okantomi said:
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.

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.

okantomi · Aug 1, 2011 at 8:23 PM

pingvinen said:
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.

No, not at all....people need an easy to follow rooting guide.

pingvinen · Aug 1, 2011 at 8:40 PM

okantomi said:
No, not at all....people need an easy to follow rooting guide.

There is one here

http://forum.xda-developers.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.

abello00 · Jan 2, 2008 19 1 0

pingvinen said:
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?

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.

pingvinen · Aug 1, 2011 at 9:27 PM

abello00 said:
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.

Apology accepted, and thread closed. I guess that there are other threads on how to handle boot errors and defunct system images.

okantomi · Aug 2, 2011 at 12:06 AM

pingvinen said:
There is one here

http://forum.xda-developers.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.

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.

jonnunez · Aug 3, 2011 at 1:53 AM

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. :/

okantomi · Aug 3, 2011

jonnunez said:
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. :/

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.

pingvinen · Aug 3, 2011 at 9:10 AM

jonnunez said:
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. :/

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.

jonnunez · Aug 3, 2011 at 1:05 PM

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

Sent from my HTC Sensation Z710e using XDA Premium App

jonnunez · Aug 3, 2011 at 1:17 PM

Appreciate any help btw, whoever can help me succesfully beat this I will make a donation for their time.

Sent from my HTC Sensation Z710e using XDA Premium App

pingvinen · Aug 3, 2011 at 5:19 PM

jonnunez said:
Appreciate any help btw, whoever can help me succesfully beat this I will make a donation for their time.

Sent from my HTC Sensation Z710e using XDA Premium App

Sorry, no clue on what part that may have gone wrong.

okantomi · Aug 3, 2011

jonnunez said:
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

Sent from my HTC Sensation Z710e using XDA Premium App

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.

jonnunez · Aug 3, 2011 at 9:41 PM

okantomi said:
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.

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.

jonnunez · Aug 3, 2011 at 9:44 PM

and dont worry dude, i dont take any offense over the web, just looking for some help and i appreciate any so thanks.

okantomi · Aug 3, 2011

jonnunez said:
and dont worry dude, i dont take any offense over the web, just looking for some help and i appreciate any so thanks.

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.

jonnunez · Aug 3, 2011 at 10:46 PM

quick question, what if i try re-flashing stock image of 3.2?

pingvinen · Aug 3, 2011 at 10:46 PM

okantomi said:
Cool. So, from CWM recovery, do a complete wipe-user data/factory reset and that should get you back to stock 3.2. 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, you can wipe from adb, but you'll need to look up the commands.

I hope this helps.

The guide that okantomi refers to is here
http://forum.xda-developers.com/showthread.php?t=1170760

jonnunez · Aug 4, 2011 at 3:24 AM

nevermind, I reflashed the stock img via adb and started fresh

okantomi · Aug 4, 2011 at 3:55 AM

jonnunez said:
nevermind, I reflashed the stock img via adb and started fresh

Great news! Glad you got out of that jam.

Idiot's guide to flashing the Xoom (for fun and profit)

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Member

Senior Member

Senior Member

Member

Member

Senior Member

Member

Senior Member

Member

Senior Member