Wonky Xoom

[ggrant3876]

I'm new to tablets . . a laptop person. However I bought an almost new Xoom from eBay. I bought it to use while I'm having treatment for cancer . . easier to handle. Everything was going great until I got a message that new updates were available. Now the problems. After I started to download and activate the updates, my Xoom switched off . . then on came the 'throbbing' M inside a circle.
That was it. Wouldn't switch off . . nothing. Having GOOGLED it I found the answer to rebooting. Power and UP volume. Off it went, then switched on again. I have repeated this countless times since the problem showed up.
I have managed to access the Android reset screen . . nothing happened.
Can anybody, anwhere give me an answer to this?

Welcome to the forum. Glad you decided to join us. Has your issue been resolved by reflashing the stock images?

[Ads]

[papacool]

What you have is called a "Soft Brick". It's annoying, but not so hard to fix.

If it's a WiFi-only Xoom, you should just GEDify it. Here's my step-by-step guide on doing this. It'll fix it because you'll be flashing the stock US GED firmware onto it, meaning any "corrupt" firmware will be removed and replaced with nice, clean, working firmware

Thanks for this information. At last, I thought . . I have an answer.
Yes it is a WiFi-only Xoom. I live in the UK. I printed off the instructions from your link, sat quietly on my own with my Xoom, USB cable and my laptop.
Having read everything I sat thinking carefully of what is about to happen, I went to it. . . . nothing!!
After several attempts, I ended up with a 'waiting for device' notice . . . . .
Try again, I ended up with the 'dead / sick android' and the red triangle with the exclamation sign.
Eventually, I had to give up when relatives came to visit me for a progress report on my health treatment.
I've not given up though. I'll try again later.
I'm ever hopefull this will be solved
Thanks to you all for your assistance with this.

[soulstlr]

any luck yet papacoool? oops too many "o's", that must mean you are way coool!
perhaps we can prompt LaKraven to drop by and give you a hand.
hope all is well and you were eventually successful.

[papacool]

any luck yet papacoool? oops too many "o's", that must mean you are way coool!
perhaps we can prompt LaKraven to drop by and give you a hand.
hope all is well and you were eventually successful.

Sadly, I wish I was WAY C o O o L. Still nothing going right wih this. I think I'll leave it in a cupboard for a few days, let me calm down over it.
Build up some strenght and go for it again. Thanks for all the help and assistance you've all offered.

[motoguy]

Papacool, if you do get your Xoom back in working order I'd like to hear how since your situation appears almost exactly like mine. The only difference is that I'm in the US. I fully understand your frustration.

I noticed the GED link that was provided above says it's a procedure for putting GED on a non-US Xoom so it's unclear if this would work for me. Can anybody tell me if it would also work for a Xoom for the US?

[soulstlr]

Papacool, if you do get your Xoom back in working order I'd like to hear how since your situation appears almost exactly like mine. The only difference is that I'm in the US. I fully understand your frustration.

I noticed the GED link that was provided above says it's a procedure for putting GED on a non-US Xoom so it's unclear if this would work for me. Can anybody tell me if it would also work for a Xoom for the US?

i re-read LaKraven's gedify guide and it is not clear if it will work for you or not. my inclination is leading me to believe that it will not, but the definitive answer should, obviously, come from the aforementioned developer.
if i were you i would send LaKraven a private message with your question and see if he has any advice that will aid you in your predicament.
if you would not mind, it would be extremely helpful if you could, in detail, describe the situation that your are currently experiencing.
that would aid others it attempting to identify your needs and affect a possible resolution.

there are many incredibly knowledgeable persons on this site, please feel free to pick their brains...

and, i forgot my manners, welcome to the forum and enjoy!

[ggrant3876]

Papacool, if you do get your Xoom back in working order I'd like to hear how since your situation appears almost exactly like mine. The only difference is that I'm in the US. I fully understand your frustration.

I noticed the GED link that was provided above says it's a procedure for putting GED on a non-US Xoom so it's unclear if this would work for me. Can anybody tell me if it would also work for a Xoom for the US?

Welcome to the forum. Glad you decided to join us. LaKraven has taken his Gedifying instructions off of his blog, he has stopped sharing. You can go to Astrix's thread and just flash the US firmware, that's basically all gedifying is.
[HOW] Rookie Rooting, Flashing And UnRooting Under One Roof

[motoguy]

if you would not mind, it would be extremely helpful if you could, in detail, describe the situation that your are currently experiencing.
that would aid others it attempting to identify your needs and affect a possible resolution.

I'll try. I didn't want to hijack the post thread but I suppose this could help papacool or others with this same problem.

I have a US WiFi Xoom which had been running JB. It was not rooted. After being powered down, it would no longer boot but stayed at the red Mot splash screen. It will not power down (except to let the battery run down completely which I've done three times now). I _can_ soft reboot by pressing and holding the power button and the volume up button together. I tried using android recovery and performing a “Wipe data/factory reset” but this did not change anything. My attempt to use my usb cable to reflash the device did not succeed because I get a 'waiting for device' message at the command prompt. As I understand, this is due to the fact that I can't turn on "USB Debugging".

Right now I'm not sure what should be my next step. In another post, Astrix suggested to someone the rsd/sbf method which I may try next. I was just a bit confused by some of the information I read in some forums. Do I select RSD from the "RSD, Fastboot, Android Recovery" menu? The video that was in one of Astrix's posts was confusing since it described using a Mot phone instead of the Xoom.

[papacool]

What you have is called a "Soft Brick". It's annoying, but not so hard to fix.

If it's a WiFi-only Xoom, you should just GEDify it. Here's my step-by-step guide on doing this. It'll fix it because you'll be flashing the stock US GED firmware onto it, meaning any "corrupt" firmware will be removed and replaced with nice, clean, working firmware

OKay . . I've spent the past hour or so. Below is what I get either on my laptop or the Xoom;
Showing on Xoom after Startup with Power and Volume
Starting Fastboot protocal support.

laptop shows: Xoom_GEDIfy
and file GEDIfy your Motorola Xoom
I printed this off, studied it carefully.

You say go to START
I type in RUN
type cmd
hit OK

I see C:\Users\Andy>
I type fastboot oem unlock

I see 'fastboot' in not recognised as an internal or external command,
operable program or batch file.

C:\Users\Andy>

The Xoom shows Starting Fastboot protocol support.
Can't get any further than this.

[tedster]

Did you do this?

■On your PC, open Windows Explorer (or My Computer)
■Navigate to the GEDify folder you extracted from the AIO package.

■Hold down Shift, and Right-Click somewhere inside the folder (but NOT on a file).
■Press Open Command Window Here.
■You should now see a Command Prompt window on your PC screen.