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.
Can you access the device via fastboot or adb?
tincbtrar said:
Can you access the device via fastboot or adb?
Click to expand...
Click to collapse
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.
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
elsworth1983 said:
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
Click to expand...
Click to collapse
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.
Lyrrad0 said:
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.
Click to expand...
Click to collapse
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.
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.
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?
Related
Hi guys!
I bought my new HTC One X on contract with three UK about 10 days ago. Been working great and I've flashed several different roms on it, the latest being the AOKP jelly bean.
I was in the middle of setting up my Go Launcher last night, when the phone suddenly died. I thought it must have just crashed following some rom/kernel issue, so I tried to turn it back on, no luck. Also tried holding the power button down but to no avail.
I supposed that it might have run out of battery, as it was fairly low at the time, so I left it charging on USB (with the indicator light flashing) all through the night (around 9 hours) and this morning it still won't turn on.
The screen won't come up at all, and the phone doesn't vibrate or make any noise but if I connect it to my computer it will sometimes be detected and I can see the device in ADB.
"adb devices" first shows the device as offline, then if I run "adb kill-server" and try again then it shows the device as "HT23YW105462 recovery".
I've then tried running commands such as "adb reboot", "adb reboot-bootloader", "adb reboot -p" but no luck. The phone seems to recognize the command as it disconnects, but it doesn't turn back on.
Any theories guys? I hope my new toy hasn't been bricked somehow! If this happened to my Desire HD I'd just take the battery out to make sure it was fully off and try again... is this a good idea here?
Thanks in advance for any help you can give! Many cookies will be given as reward. (sorry for the long post )
Not sure but I had a fairly similar problem which i barely got out of, hope it helps,
I was restarting my phone for some reason(while battery was low) and when it was turning back on, the screen was black at the time, i connected the usb cable for power and the phone never started. it stayed at the black screen, but in complete darkness you could tell the display was on, but in normal it would seem the phone is not even turing on.
I thought i bricked it for some reason, but what i did was charge up the phone a bit, combination of connecting to the computer and ac wall charger. The phone only restarted when connected to the wall charger so then in order to get into bootloader, i held the volume down and power, and plug the charger at the same time and after multiple attempts it finally managed to get into restart into the bootloader, than you just reboot into recovery and you should know the rest, factory reset or flash a clean new rom.
chrisoverson said:
Hi guys!
I bought my new HTC One X on contract with three UK about 10 days ago. Been working great and I've flashed several different roms on it, the latest being the AOKP jelly bean.
I was in the middle of setting up my Go Launcher last night, when the phone suddenly died. I thought it must have just crashed following some rom/kernel issue, so I tried to turn it back on, no luck. Also tried holding the power button down but to no avail.
I supposed that it might have run out of battery, as it was fairly low at the time, so I left it charging on USB (with the indicator light flashing) all through the night (around 9 hours) and this morning it still won't turn on.
The screen won't come up at all, and the phone doesn't vibrate or make any noise but if I connect it to my computer it will sometimes be detected and I can see the device in ADB.
"adb devices" first shows the device as offline, then if I run "adb kill-server" and try again then it shows the device as "HT23YW105462 recovery".
I've then tried running commands such as "adb reboot", "adb reboot-bootloader", "adb reboot -p" but no luck. The phone seems to recognize the command as it disconnects, but it doesn't turn back on.
Any theories guys? I hope my new toy hasn't been bricked somehow! If this happened to my Desire HD I'd just take the battery out to make sure it was fully off and try again... is this a good idea here?
Thanks in advance for any help you can give! Many cookies will be given as reward. (sorry for the long post )
Click to expand...
Click to collapse
What happened to me is that I forgot to put my one x on charge overnight and when I woke up in the morning it wouldn't turn on and it "wouldn't charge". What had actually happened here is that I fell victim to the charging issue as many will. But I shall cut to the chase, how to fix the problem. This seems to happen with a lot of android phones, but more so, a lot of HTC phones. The phone seems to charge excruciatingly slow until you actually get the phone on, so first things first, lets turn the phone on.
1. Plug you HTC status into your PC/Laptop via the USB charging cable that is turned on and leave the phone there until you see the orange blinking light.
2. Find you wall charger and QUICKLY unplug the USB cable from the PC/Laptop and plug it into your status. (the reason for the quickly is because the phone won't charge through the wall charger unless you get that orange light blinking) I made you change to the wall charger as it charges quicker.
3.Wait until the orange light stops flashing (or maybe it wont so wait about 15 mins) then hold the power button until the phone turns on. If it doesn't turn on after 15 mins continue to let it charge (one person had to leave it charge for an hour)
4. You're done! your one x is saved!
OK so the reason that we let it charge for a bit is because the one x seems to have an issue getting charged every once in a while, this trick gets the one x's battery to 2% and once you've turned the phone on, it can charge completely.
I hoped this helped,
Mantenner
This is a HTC One S unlocked and rooted with CM 10. Last night I was using the phone and out of nowhere powered off. I plugged it into wall charger and when I went this morning to turn it on I got nothing. The orange light indicating charging does not turn on. I have tried holding every variation of the power button with other buttons getting nothing. When I connect to PC the device is not detected. As of recently every time I connect the phone to the usb or to the wall outlet, the camera's flash stays on. As soon as I disconnect the phone the flash goes off. If I hold the power button while connected via usb or wall charger the flash will turn off after 10 seconds but once I let go it comes right back on and this does nothing to turn the phone on, the whole time its black. any tips?
alexd1 said:
This is a HTC One S unlocked and rooted with CM 10. Last night I was using the phone and out of nowhere powered off. I plugged it into wall charger and when I went this morning to turn it on I got nothing. The orange light indicating charging does not turn on. I have tried holding every variation of the power button with other buttons getting nothing. When I connect to PC the device is not detected. As of recently every time I connect the phone to the usb or to the wall outlet, the camera's flash stays on. As soon as I disconnect the phone the flash goes off. If I hold the power button while connected via usb or wall charger the flash will turn off after 10 seconds but once I let go it comes right back on and this does nothing to turn the phone on, the whole time its black. any tips?
Click to expand...
Click to collapse
update any time I plug the phone into the computer or wall charger the camera light comes on and stays on while plugged in. The charge light does not come on and the pc does not recognize a device is connected. The only thing I can think of to try is to take apart phone and take out the battery, but I do not have the proper tools maybe walmart eye glass repair kit may work with with a razor.
enrcipt largest
alexd1 said:
update any time I plug the phone into the computer or wall charger the camera light comes on and stays on while plugged in. The charge light does not come on and the pc does not recognize a device is connected. The only thing I can think of to try is to take apart phone and take out the battery, but I do not have the proper tools maybe walmart eye glass repair kit may work with with a razor.
Click to expand...
Click to collapse
Edit: took apart phone and disconnected battery and still nothing. just the camera flash on when plugged in via wall or usb! Any help guys!
Edit #2: took the phone apart completely there was nothing out of the ordinary and not damage of any kind. Put the phone back together and nothing. It's as if the phone has lost all of its software because it doesn't respond to the power button or any button as if the phone doesn't have a command for the button pushes. The only thing that has life is the camera flash that comes on when phone is plugged into a power source that's it.
Cant you bring it back to the store and send it in for repare?
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
Cant you bring it back to the store and send it in for repare?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I am sure the price of repair would not be worth the phone and there's no warranty
Never heard of this problem. You might want to try holding the power button down?
Update: out of nowhere I have the orange blinking light and the computer recognizes the device as a USB Composite Device. the phone does not power on nor will it go to the bootloader, Is there anyway to turn on the phone with the computer?
well fastboot does not recognize the phone and I tried updating the drivers and that didn't help. phone blinks orange and connects as a USB composite device but cannot power the phone on or access anything on it.
Hm, difficult.
You could try these commands in order:
adb devices
adb reboot bootloader
fastboot devices
fastboot reboot-bootloader
If it doesn't answer keep it loading for 24 hours or at least over night and then retry. Else it is bricked.
rootrider said:
Hm, difficult.
You could try these commands in order:
adb devices
adb reboot bootloader
fastboot devices
fastboot reboot-bootloader
If it doesn't answer keep it loading for 24 hours or at least over night and then retry. Else it is bricked.
Click to expand...
Click to collapse
seems to be bricked, it does not come up under devices and fastboot sits at the waiting prompt. well this sucks how random to brick while normal usage
My Sensation has passed by this afternoon.
It does not even turn on, does not react to anything.
The last days, battery started to fall down very quickly (from 100% to 0% in no more than 1 hour of use, when the previous day, it lasted well +24 hours as usual). Then it did not detect any sdcard in it. Then, common freezes with vertical and horizontal lines came across the screen, especially after playing some demanding game. Back of the phone was literally on fire. I had to wait several hours to reboot again, of it would freeze on the boot screen otherwise. From that final state it only lasted one more day.
adb does not detect it connected to any USB plug (no device found). I have tried with/without SIM, battery, swapping batteries, only connected to USB plug, with/without sdcard... with the same result.
Screen only lights on whenever connected to an USB plug, but it does not respond to anything. It does not sound like when Windows detect a new hardware found. adb tools does not work either.
My main question is. Phone was with bootloader unlocked, S-off, debranded and with CWM Recovery 6 and CM10.1 installed on it. I am going to send it to the HTC RMA service as it is within the two-year warranty period. Could they detect anythingof the above-mentioned even if the phone cannot boot?
Thanks in advance.
did you try to boot into bootloader?
probably they can see that the bootloader is unlocked(i am not sure)
did you try the unbricking project?
if you plug the device to the charger does the led show red?
rzr86 said:
did you try to boot into bootloader?
probably they can see that the bootloader is unlocked(i am not sure)
did you try the unbricking project?
if you plug the device to the charger does the led show red?
Click to expand...
Click to collapse
Hello, thanks for the input.
The led does not show in any color. The screen just lights up a bit when connected to an USB plug. But it does not react to anything, power button, power+vol down button (for entering the bootloader)...etc. Now it is like a paperweight.
I will have a look at the unbricking project. But i highly doubt I could do anything if It cannot enter the bootloader and/or respond to adb commands...
jfromeo said:
Hello, thanks for the input.
The led does not show in any color. The screen just lights up a bit when connected to an USB plug. But it does not react to anything, power button, power+vol down button (for entering the bootloader)...etc. Now it is like a paperweight.
I will have a look at the unbricking project. But i highly doubt I could do anything if It cannot enter the bootloader and/or respond to adb commands...
Click to expand...
Click to collapse
I had the same issue you did. Are u sure your battery isnt too low to start charghing? You can try to charge it a bit with a usb cable, you need to cut it and just take the red (positive) and black (negative) wires and touch the + and - of your battery for like 1 min. Then it will start charging. Give it a shot, worked for me and many others.
Zatorra said:
I had the same issue you did. Are u sure your battery isnt too low to start charghing? You can try to charge it a bit with a usb cable, you need to cut it and just take the red (positive) and black (negative) wires and touch the + and - of your battery for like 1 min. Then it will start charging. Give it a shot, worked for me and many others.
Click to expand...
Click to collapse
Hello and many thanks for the help.
I try to boot it up without the battery, just connected to the power outlet via the official HTC USB cable and charger. That way, it is supposed to boot up in normal conditions, isn't it? I wanted to discard the battery part, but anyway, I have another (non-official battery) and it does not boot either.
I think I really outdid myself this time, was installing an official firmware on my fiancee's phone(Blur_Version.98.50.26.XT925.Brasil.en.BR) trough RSD Lite (6.1.6) and at the end of the process the phone shut down and didn't finish the rebooting process. Since then I can't get it to turn on or access fastboot. Even connecting it to a charger wont turn the led on.
So, the hard questions to ask:
1. Is there anything I can do? Anything at all?
2. Even if I can't. What may have happened? I used RSD other times and I have modded half a dozen phones and a brick happened to me before.
Thank you so much, I am probably gonna get chewed since her work depends on it and we will have to get an other one, but any nudge in the right direction or cold hard truths will be appreciated.
Stephen
It almost seems like the battery died while you were flashing. What was the battery at when you started?
Sent from my HTC6525LVW using Tapatalk
I would try a Motorola Factory Adapter or mod a USB cable to act like one. If it still fails to boot then your looking at a hard brick.
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
Quick update,this morning when I connected to a power source it turned the green light on(left ir connecting for the night). Tried connecting to my pc and it will play the connected/disconnected sounds over and over again. Still can't fastboot it.
I imagine it might have been some sort of battery issue but it was over 60% when I began installing the firmware and the process took less than 10 minutes.
Sarmatios said:
Quick update,this morning when I connected to a power source it turned the green light on(left ir connecting for the night). Tried connecting to my pc and it will play the connected/disconnected sounds over and over again. Still can't fastboot it.
I imagine it might have been some sort of battery issue but it was over 60% when I began installing the firmware and the process took less than 10 minutes.
Click to expand...
Click to collapse
Flashing will kill battery. You should always try to do it with a full battery. Anywho, does anything show up in the device manager on your PC when you connect the phone?
Sent from my HTC6525LVW using Tapatalk
Nope, my pc will make sounds as if it was being plugged and unplugged repeatedly.
Also when I press the power and volume buttons to reboot in fastboot or recovery (the cell was unlocked, rooted and had the latest JB philz recovery ) the green light will flash but the screen wont turn on.
Nothing shows up at all? That sucks. Hmmm, leave the phone on the charger overnight and then see if you can get into fastboot.
Sent from my HTC6525LVW using Tapatalk
Howdy!
My phone doesn't work anymore, and I try to assess what's going on. I searched before posting, and I decided to post here because I found mixed answers.
Context:
I bought my phone in January 2014. I took extra care of it, it has never fallen on the ground from high, no scratch, nothing. Regarding the battery, I tried as much as possible to charge when it was close to 0%, I wasn't a heavy user of my phone, and I was turning off a lot of things so that the battery would not deplete quickly (Wifi, localisation, Bluetooth, auto-typing, et cetera...).
However, recently (the last month), I was feeling the battery was weak, depleting more quickly than before. I also felt the phone was warmer than usual. Sometimes the phone would turn off suddenly when I was short on battery (under 15%) and using a "heavy" feature (photography with flash, video game).
A week ago, the phone suddenly turned off, never to turn on again. The phone died. I was just typing a message, the phone was charging and the battery was around 60%. I was surprised.
As of today, the phone doesn't turn on. Plugged on a wall outlet or on the USB port of my computer is the same.
I tried many combination of buttons to fastboot, reboot, reset, or whatever, nothing sparked any life in my phone. (I tried holding power key for 30s+, 15s+ ; I tried holding power key + volume up for 15s+ ; power key + volume down ; power key both volume ; in fact whatever combination I could read here on XDA forums, on Reddit, on Google Forums...).
My first insight was: it's just the battery. I can buy one off the internet, and voilà!
However, when I plug the Nexus 5 on my computer via USB, the computer reacts with the sounds when you connect something. Is it just the battery then?
At first, it was saying: "QHS_USB BULK", and the computer was trying to install whatever to make that peripheral work.
When it was done, it read "Qualcomm HS-USB QDLoader 9008 (COM4) has been correctly installed.
Hum, okay.
Still, nothing shows in the peripheral.
I continue to hear the plug in plug out sound when I... plug in and out my phone in the computer, but that's the only thing.
With all that, I can't really tell if all the phone is dead, something grilled inside or I don't know what; or if it's just the battery that is dead and the phone is unreachable and unrecognizable when "there is no battery" in it.
I'm not sure if I shall invest money into buying a new battery.
Do you guys can light my lantern on that matter?
I would greatly appreciate it.
Thanks,
Cheerio!
If I may just address a little bump on this very subject of particular interest to myself :3
Cheerio!
Any insights on this? mine´s doing the same. Doesn´t turn on or go into bootloader, when i connect to charge it red light blinks for like 10 sec and then goes off. Nothing happens after hours of charge.
Did you try replacing the battery as you mention on the post?
Sorry, but have to say this with caps: BLINKING RED NOTIFICATION LED MEANS ITS DEAD BATTERY. Can't be 100% sure, but usually it means that the phone doesn't have enough power to boot up. Mine did this when it drained to the absolute 0%
edit: There can be other problems with power going to phone, but if you are lucky its just the battery.
So i changed the battery. When i plugged it to charge no red lights came on, just the typical white battery with the light bolt appeared for a few seconds, after that it went on with screen off (or at least i thought it did). After 3 h of uninterrupted power charge i went to turn it on. Nothing happened. Can´t turn it on or go into bootloader.
Nothing happens on my pc when i plug it. No sound and nothing on Device manager (no drivers for nexus 5 installed, don´t know if that matters for windows to recognize it as any device even if its not as android device).
Edit: yeah, i got enlightened and literally unplugged the battery and plugged it back in and it worked like charm. I get stuck on the intro animation but i can get into bootloader and recovery just fine. Just gonna install those drivers and flash something. right? Thanks to everyone that read and even more to those who replied!
qaleq14 said:
So i changed the battery. When i plugged it to charge no red lights came on, just the typical white battery with the light bolt appeared for a few seconds, after that it went on with screen off (or at least i thought it did). After 3 h of uninterrupted power charge i went to turn it on. Nothing happened. Can´t turn it on or go into bootloader.
Nothing happens on my pc when i plug it. No sound and nothing on Device manager (no drivers for nexus 5 installed, don´t know if that matters for windows to recognize it as any device even if its not as android device).
Edit: yeah, i got enlightened and literally unplugged the battery and plugged it back in and it worked like charm. I get stuck on the intro animation but i can get into bootloader and recovery just fine. Just gonna install those drivers and flash something. right? Thanks to everyone that read and even more to those who replied!
Click to expand...
Click to collapse
Yeah, search from youtube how to flash factory image nexus 5. It should make it work. And try to find video with using adb instead of toolkit, adb is way more stable/trustable. (ADB is the android debug bridge, it may look like very hard and confusing but in the end its just typing 1 command and it flashes everything needed) If you need help in flashing the image, just ask!
Try this, it installs only tools needed for adb (also drivers) http://forum.xda-developers.com/android/software/tool-platform-tools-adb-fasbootdrivers-t3061441
Edit: This should work https://www.youtube.com/watch?v=5ka5dnPghzI