Xoom US Wifi: Appears dead

[Lyrrad0]

Hi,

I'm having an issue with my Xoom Wifi (US, original). It's running Jelly Bean and is unrooted, locked, and stock everything. It won't turn on.

Today, I was charging the Xoom, it was on and at 15% battery life. Later, when it around 45-50%, I unplugged it and let it be on standby. Later, I returned to it and it was unresponsive with a blank screen. I don't know if it was on at that point. However, at one point I noticed that the screen was backlit (but still showing black), and holding down the power and one or both of the volume keys for a few seconds turned the Xoom off. Since that point, I have been unable to turn it on.

Status of Xoom:
- Charging appears to work. White LED showed when charging, then later changed to green.

I've tried the following:
- Waiting for Xoom to charge (LED to turn green), and holding down the power button for a few seconds; holding down the power button for a minute, holding down the power and volume up for a few seconds as well as up to a minute, holding down power, and volume down for up to a minute, as well as all three buttons. I've tried these steps while plugged into AC as well as not plugged in.
- I've also removed the battery for at least a few minutes before reinstalling it and tried the above steps for trying to turn it on.
ETA: - Also tried removing microSD card.

It still doesn't seem to be turning on.



What are my options?

Thanks.

 

[tincbtrar]

Can you access the device via fastboot or adb?

 

[Lyrrad0]

Can you access the device via fastboot or adb?

I'm not sure if my fastboot is set up correctly. I'm having difficulty using it on my Mac running Mountain Lion (getting (ERROR: could not get pipe properties), when I'm doing the ./fastboot devices command)

However, when I run "./adb devices", I can see my Galaxy Nexus as an attached device when it's connected, but not my Xoom. I've tried holding down all combinations of power+Volume before running the command.

ETA:

Okay, got fastboot working by rebooting my phone into bootloader mode. I can get my Galaxy Nexus to show up when doing ./fastboot devices, but I can't get my Xoom to show up. Note that the only output from my Xoom right now appears to be the charging LED light that is usually white, but turns green after a few minutes being plugged in.

 

[elsworth1983]

Am no expert but if your charging it with a white light then a few minutes later it goes green the problem might be your battery has died completely (just a thought)

Sent from my Xoom using xda app-developers app

 

[Lyrrad0]

Am no expert but if your charging it with a white light then a few minutes later it goes green the problem might be your battery has died completely (just a thought)

Sent from my Xoom using xda app-developers app

I don't think this is the case. Green indicates that the battery is fully charged. When it died, the battery was about 50% full. It took a few hours for the battery to charge that the light to turn green. Now when I plug it in, it is initially white and then turns Green after a few minutes, indicating that the computer thinks that the battery is full.

Does anyone have ideas? Would getting/creating the special diagnostic motorola USB cable be of any help? How can I diagnose what's wrong? I don't mind disassembling the device if it would help.

I usually have limited access to parts, but I will be visiting the US in a few days so if you have ideas for useful parts that I can order that might help let me know.

Thanks.

 

[Terxxu]

I'm not sure if my fastboot is set up correctly. I'm having difficulty using it on my Mac running Mountain Lion (getting (ERROR: could not get pipe properties), when I'm doing the ./fastboot devices command)

However, when I run "./adb devices", I can see my Galaxy Nexus as an attached device when it's connected, but not my Xoom. I've tried holding down all combinations of power+Volume before running the command.

ETA:

Okay, got fastboot working by rebooting my phone into bootloader mode. I can get my Galaxy Nexus to show up when doing ./fastboot devices, but I can't get my Xoom to show up. Note that the only output from my Xoom right now appears to be the charging LED light that is usually white, but turns green after a few minutes being plugged in.

Do you got any response when you connect the XOOM to your MAC with standard USB cable?

Can you try it on Windows PC?

If nothing response, try to connect with "factory cable".

P.S. I bricked my XOOM, it's only recognized as APX device. After I installed drivers, It could be recognized as "NVIDIA USB Boot-recovery driver for Mobile devices". And then nvflash command could be executed and got some response. I hope I could got progress, but I still stuck here. All indicated that I need original "bootloader.bin", and BCT and config files. I also try to send it to different MOTO local service centers, they told me that maybe I damaged the hardware(?), if I want to repair it, the motherboard must be replaced. Anyway, hopes this information could finds you. And if you solved your problem, please just let me know how. Thanks in advance.

 

[majinzen]

Well, my Xoom did the same thing as described in the OP last night. Power button was unresponsive but could charge. Googled around and found that many people fixed this issue by pressing volume up + power for a few seconds. Tried it and worked. Xoom booted up, and I gave a sigh of relief.

 

[GT-Xoomer]

I feel you pain

I'm having the exact same problem that Lyrrad0 initially reported.I couldn't describe it any differently. It's great to see someone else is experiencing the same thing. A lot of posts that i see mention doing the power button + Volume up button fix, but this doesn't work for me and sounds like it doesn't work for Lyrrad0 either.
Like Lyrrad0 i also think the battery is fully charged. I saw a few chipsets that i could buy but it would be annoying if it didn't fix the problem still and i had wasted my cash.
Just wondering if Lyrrad0 tried to replace any parts? If so did they fix your problems?