[Q] Flashing Colors on screen - Xoom Q&A, Help & Troubleshooting

Hi folks! Long time XDA lurker (Nexus 7, 10, and Samsung Galaxy Tab 2 7 forums), first time poster.
I picked up a XOOM off of EBay last week. The device ran well once I got it charged, it did software updates and was running on 4.0.3 with no issues until last night. I went to pop in a micro SD card, and when I pressed the power button to get it out of sleep mode, the screen began flashing colors, cycling between all colors, a checkerboard test pattern at one point, gradients from light to dark, etc. I did a bunch of Google searching last night and found one link where someone had the same issue, but no solution was mentioned. I have also looked here, but no luck. The one link I found last night seems to indicate it's some files from ICS getting corrupted during the update to 4.x, but it wasn't really clear whether that was the case or not.
I have tried the power+vol up button trick; that turns the screen off after a second or two, then the light show begins again. I can't find a way to shut off to be able to get it into recovery mode, and I have tried installing the Lord AIO tool but on running it, it seems to be stuck at the 'list of devices attached' section. Any ideas, other than letting the battery run down to nothing, then maybe it being able to get put into recovery mode? The place I bought it from on EBay does have a 14 day return policy, so I have a few days still to figure this out, but not sure how long it'll take to run the battery down. The light show on the screen does time out after about a minute or two, but I obviously can't keep hitting the power button every two minutes until it does finally drain the battery.
I really like the XOOM, it feels like you're actually holding something real & solid, compared to other tablets, and want to get this back up & running again. Any ideas what I can do next?

Related

[Q] Nexus One (2.3.3) display turns off during boot

Hey all,
So I bought an essentially unused Nexus One about 2 months ago. It came with froyo, and a day or so after I got it and turned it on (T-mobile btw) it updated to 2.2.1-partial or something. A couple weeks later it notified me that system update 2.3.3 was available (woot!). So download.....install.....reboot......problem.
So basically, now almost every time the phone boots up, it shows the static X for a bit, and then when it tries to switch to the animated particle-attractor X, the display just shuts off and nothing shows up. It apparently boots ok and everything else works fine: I can press the power button, and swipe-unlock...even answer phone calls....but the display stays off. I can eventually coax it into turning on the display again by numerous rounds of taking out the battery and reinserting with luck and random voodoo sprinkled in, but I have no idea what's going on or how to fix it. I've found a couple other cases by googling around, but no fixes.
So is this something people are aware of? Will the 2.3.4 update fix it? I would try to root/install CM7, but while I can get into fastboot, going from there to recovery is a crapshoot because of the display issue. So any help would be awesome, thanks in advance.
To re-emphasize, this is completely stock Gingerbread on a never-rooted/modded Nexus One.
2.3.4
Just got notified of the 2.3.4 update today, downloaded, rebooted......same problem.

P6810 suddenly won't turn on

Anyone come across this? I put it on standby last night after reading a bit of my book on it, and it had around 50% power remaining. This morning, it was totally unresponsive; pressing the power button does nothing at all. I've charged it for 12 hours in the meantime.
I've done the following all with and without the power attached:
- Pressed and held power for 15 seconds through to a minute
- Pressed and held volume up with power to attempt to get into recovery for up to a minute
- Pressed and held volume down with powerfor up to a minute
- Pressed and held power while touching screen (read that one off another forum)
I guess potentially it could be on and in a crashed state and unresponsive to the power, so maybe in a weeks time when it runs out of juice, I'll be able to charge it and power it back up, but in the meantime, I'd welcome suggestions.
A few weeks ago I updated it to the official ICS build that was released, but did the update myself rather than using KIES, as KIES didn't even recognise my Tab's firmware original version. It's been absolutely fine before the update, and since. I only mention it because I've read about the Samsung build of ICS being prone to self bricking itself, but I couldn't determine what the symptoms of this vulnerability were.
Thanks for any help offered,
Will
did you try connecting USB cable and plugging it into your PC? did u get any activity? can ADB recognize your tab?
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Had the same problem while on holidays. Once the battery goes below a certain level, you won't be able to charge it through USB any more. Instead you need to use the wall charger.
I think it's bad enough that the 7.7 doesn't have a micro USB port, but things like that are just stupid and Samsung made a big mistake here. It don't think it's the same with the newer tablets though. It's also not possible to just buy cables or chargers for this strange Samsung port, so when you forget your wall charger at home at some point you won't be able to use your tablet any more.
As long as you charge with the USB cable early enough, you can avoid it though.
A few months ago I experienced the same thing, the Tab just wouldn't turn on anymore.
I tried all there is without any luck.
Contacted amazon and they replaced it with a new one in less than 48 hours.
So far not Problems with the new device.
I have the P6800 and this morning I took it off charge. Put it into standby and only used it for about 20 mins then left in standby all day. It had about 95% remaining when I did so.
Picked it up this evening and the lower left area of the screen was warm and it would not switch on. Didn't think of the ADB idea but will try this next time but I had to reset it and when it powered on tonight after the reset, it was down to 15%. Within about 2 mins of checking stuff it was down to 3%.
Something is running when it is in standby but as I can't switch it on I can't check with BetterBatteryStats or CPUState to know what is wrong.
It does this every day. I am tempted to do a factory reset and reinstall only limited software.
Dave...
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Cluey said:
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Click to expand...
Click to collapse
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
TeeeJaay said:
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
Click to expand...
Click to collapse
hhmmm, interesting.
I was having trouble with wifi just before this happened. Both my GS2 and this have been claiming to connect to my wifi but aren't actually getting an IP address from it.
I can't remember if it was last night or the night before but I manually set an IP address, the signal strength is fine as my abode isn't very big.
After it has recharged I'll have a poke and see what I can find, thanks for the reply.
So my device seems to be working fine again. It had gone SO flat that the date and time were incorrect!
After I could power it on I had a look at Better Battery Stats and nothing looked wrong so I have no idea what happened. None of the apps I'd installed the day before it played up had long wakelocks and weren't running when I turned it off.
For reference they were:
My Tracks
MyTrails
Google Earth
AndSMB
I'd turned both of the GPS tracking devices off before I turned it off for the night.
It hasn't played up since but it hasn't been long so I'll see what happens.
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
A similar thing happens to me every once in awhile. The way i check to make sure everything alright is to see if it boots into download mode. I just leave it plugged in for a couple hours and it eventually comes back on.
someth1ng said:
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
Click to expand...
Click to collapse
this is why my 7.7 is the last tablet/phone from Samsung i'll never trust them they are just bombarding the market with new devices and leaving the old ones to dust
^thats what I thought too but that gs4 is really tempting. I've heard worse about HTC in that regard anyways so that why I'm not going with the one.
Finally.. i bought Sony xperia Z.
I'll sell my galaxy tab 7.7. I.m very disappointed with samsung.
Sent From XPERIA Z
kishd said:
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Unbelievable! ... this trick still works ... thank you very much for you help ...
^^ yo, this 'trickle charge' trick did NOT work on my (long) dead P6800... any other suggestions??
Quite strange because my Samsung GT-P6800 tablet was fully charged, it went completely blank dark as if it was off. To my amazement, SMS keeps dropping and calls kept coming in. Yet it is still as blank as though the tab was off. I pressed the power button and the volume up bottom for it to reboot. It rebooted without the screen coming up. It has been blank for two days now. What could be the cause? And what possible solution can be given?

[Q] Tab2 7.0 won't reboot after hard reset

First post. Tried searching for the desired info, to no avail. Braving any potential flame spray and asking anyway. Besides... this may entertain you. I've also posted this same question to a couple other forums, to no avail.
I have a P3113 that I had on me when I was caught in a rain storm. I was wearing a rain coat, and the tab was in one of the pockets. The pocket was zipped closed, so I thought the tab would be safe. It wasn't.
I did the regular stuff of turning it completely off right away, then put it in a bag full of rice for about 16 hours or so. When I tried to restart it, no dice. About a day later, it did turn on. It stayed on for about an hour letting me play Fruit Ninja. Then it shut itself down on low battery. I couldn't get it to charge at all during this period. I left it on the charger over night... didn't charge. At that point, I sort of wrote it off, but didn't pitch it.
Fast forward about 2 years. I get bored one night, pop the back off and wire the outermost wires to a freshly charged 3.7V battery from an OG Droid phone. Hit the power button... and it booted up!
While it was running, it wouldn't get very good WiFi, even sitting next to my router. It wouldn't open the Play Store app, and when I managed to log into Play through the browser, Play wouldn't recognize the device. That kept me from being able to download any app updates or any new apps.
Then the machine started running v e r y s l o w. At that point, I decided to throw caution to the wind (I did, after all write this thing off about 2 years ago) and do a factory reset.
Now, when I have the device in recovery mode, and I tell it to reboot, it will shut off and never turn back on. If I manually power on with the power button, it starts up in recovery mode.
The device isn't rooted, and I can't root it at all. At this point, I'm not even sure where the data cable is, not to mention it would never interface with a PC after the initial incident. I have, still, tried to do "apply update from external storage," using a few different roms I have found here and elsewhere. Most recently, I used Tab2Lite_P3113_RC2.zip, but it failed at about 75% complete and gave me a "signature verification failed" error message. In fact, I get the same message for every rom I've tried.
Anyone have any idea at all how to recover this thing? I'm only curious if I can get it running just to play games. I plan on getting a Tab 4 8.0 in March.
So you are using a different battery?
shsagnik said:
So you are using a different battery?
Click to expand...
Click to collapse
Electrically speaking, I'm running 2 batteries in parallel. The OG Droid battery is wired to the factory Tab battery. I can disconnect the Droid battery and the Tab still runs, but still doesn't reboot as it should.
When I select reboot, it powers down, and stays that way until I push the power button. Then it boots right into recovery mode.'
Sorry I can't help you as I don't have requisite knowledge
Sounds like you have a Frankenstein tab,you need a new tab. Time to put it out of its misery.
Pp.

Nexus S [CM11] - hardbricked, no vigration, no computer detection!

My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/

Help! Possibly bricked my tablet?

I have had the p900 for about two years now. Rooted it some time ago and installed CyanogenMod without any problems. But just recently, when I tried to reset the tablet, it got stuck on twrp. I thought I would let the battery drain and see what would happen afterwards, but now I can't get it to turn on anymore, even though I let it charge. The tablet really doesn't do anything anymore, can't go into download mode and it isn't regocnized by my computer either. So I think it's bricked, but since I'm not really the most tech savvy person, I thought I'd ask here... Could anyone tell me if this sounds like it really is bricked, or if there is still hope?
I'm wondering if your battery discharged too far down, basically killing it. Once that happens, it no longer holds any charge. I've seen that happen on an older battery (actually happened on one of my laptops!). You could try removing the back of the tablet and disconnecting the battery and reconnecting it after a few minutes, then putting the charger back on and see if you get lights. (if you're going to do that, might as well have a new one in front of you and just replace it - easy to do, and Amazon has batteries for a decent price from a few different vendors - just did that to my Note Pro last week. Youtube it for directions, it's easy if you are patient. I used this one, http://www.amazon.com/dp/B00N4KRSVW and it is working well - even got rid of the flickering screen around 50% power and below...

Categories

Resources