Database Info

Xoom touchscreen "has gone mad"

Well guys, I don't know how to describe better this think
These are the facts: this morning I received my new Xoom WiFi from Amazon; I'm in Europe so another courier shipped my Xoom from US ground to my home.
After unboxing it, I charged it and then started playing with it. After a while, I waked up the Xoom from sleep mode and I noticed that there were several "fake touches" per second on the screen, or to better explain, I could see on the display the same reaction that would be if one touched repeatedly and very fast on the screen. This made the tablet completely unusable, or even "dangerous" (it clicked a "Like" button on facebook and sent a nonsense email all alone, without any intervent by me). The first times, I just waited and this abnormal acting disappeared. After a while, a reboot was needed to fix this condition. At the beginning this problem showed up only after locking and unlocking the screen (waking up the Xoom from sleep mode), but after some hours of use it has slowly deteriorated: at this time the Xoom does this always, from when I turn it on, to when I turn it off (and believe me, it's really hard to turn it off) and the tablet it's COMPLETELY unusable.
For now, the problematic part of the screen it's only the left column (holding it in landscape, with the front camera on top).
What can I do?
P.S.: I buyed it on April 5th.
P.P.S.: obviously the Xoom is "virgin", with no hacks of sort, completely stock

Have you tried doing a factory reset? See if that helps if not then you might have a defective unit.

crxtasi said:
Have you tried doing a factory reset? See if that helps if not then you might have a defective unit.
Click to expand...
Click to collapse
How do you do a "factory reset" on the Zoom?
"Xoom the Monster" The beatings will continue...

If the protective plastic cover is still on the screen, it could be causing problems. Other wise I'm inclined to think there is a static charge involved. It might sound silly, but try holding a metal water faucet with your other hand while you touch three screen.
-Total speculation on my part.

Yes, I did a factory reset: the only result was loosing the songs that were included with the Xoom
Psychokitty said:
If the protective plastic cover is still on the screen, it could be causing problems. Other wise I'm inclined to think there is a static charge involved. It might sound silly, but try holding a metal water faucet with your other hand while you touch three screen.
-Total speculation on my part.
Click to expand...
Click to collapse
It's what I thought too. There's no protective plastic cover anymore: I removed it before turning on the Xoom. However, I've tried with a calorifer before, and I got a shock. Now I tried with a water faucet, touching it for a while and the malfunctioning seems to be gone (for now), but now the touchscreen it's not so precise (or so it seems). However it seems strange to me. I never had such problems with any capacitive touchscreen before. Is it solveable? Is there a way to be sure that this is solved? It's a defective unit?

Ieracos said:
Yes, I did a factory reset: the only result was loosing the songs that were included with the Xoom
It's what I thought too. There's no protective plastic cover anymore: I removed it before turning on the Xoom. However, I've tried with a calorifer before, and I got a shock. Now I tried with a water faucet, touching it for a while and the malfunctioning seems to be gone (for now), but now the touchscreen it's not so precise (or so it seems). However it seems strange to me. I never had such problems with any capacitive touchscreen before. Is it solveable? Is there a way to be sure that this is solved? It's a defective unit?
Click to expand...
Click to collapse
Ok, it was a temporary solution: the malfunction came back. Then the "holding grounded metal" trick worked again, and then the malfunction came back, and so on...

I have also problems with touch screen, but my problems are much stranger. On my Xoom there are two possibilities if I turn it on, I ether have touch controls or not. Forced reboot is the only things that gets me touch controls at all.
But back to your problem, have you looked if dmesg output shows any errors? Download Terminal emulator app and write dmesg.

Ieracos said:
Ok, it was a temporary solution: the malfunction came back. Then the "holding grounded metal" trick worked again, and then the malfunction came back, and so on...
Click to expand...
Click to collapse
I suggest you return it. The components are so sensitive to electricity and there are two huge potential static generators; the battery and the flash capacitor. You could toast it at any time, and might'vs already baked a sensor for all you know.
Take it back fora new one.

Psychokitty said:
I suggest you return it. The components are so sensitive to electricity and there are two huge potential static generators; the battery and the flash capacitor. You could toast it at any time, and might'vs already baked a sensor for all you know.
Take it back fora new one.
Click to expand...
Click to collapse
Well, I tought about it, but I buyed it from Amazon US and I'm in Europe: I really don't know how to return it; I don't even know how long the returning period is. However, you could be right, so I'll try to talk with Amazon or with Motorola support service.

poisike said:
I have also problems with touch screen, but my problems are much stranger. On my Xoom there are two possibilities if I turn it on, I ether have touch controls or not. Forced reboot is the only things that gets me touch controls at all.
But back to your problem, have you looked if dmesg output shows any errors? Download Terminal emulator app and write dmesg.
Click to expand...
Click to collapse
Forced reboot (not just a reboot) seems to help here too, but only temporary, because after some time (or if I lock and unlock the screen) the malfunctioning come back.
I caught the dmesg log. Here it is an extract during the malfunction coming out
Code:
<6>[ 481.175897] request_suspend_state: sleep (0->3) at 469616632000 (2011-04-15 18:35:13.421781000 UTC)
<4>[ 481.195695] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=20
<6>[ 481.300258] active wake lock PowerManagerService
<6>[ 481.300356] active wake lock cpcap_otg
<6>[ 493.685066] request_suspend_state: wakeup (3->0) at 482125794529 (2011-04-15 18:35:25.930943528 UTC)
<6>[ 493.971463] qtouch_force_calibration: Forcing calibration
<6>[ 494.004810] do_cmd_proc_msg: Self-calibration started.
All I did here was to press the lock button (locking and turning off the screen), press it again and unlock the screen. It seems pretty normal to me. However I have the whole dmesg log (from turning on to force reboot) of that session. I can post it if it can be useful.

The part you posted is normal.
I would be interested to see your dmesg output after a forced reboot, to compare it to mine.

poisike said:
The part you posted is normal.
I would be interested to see your dmesg output after a forced reboot, to compare it to mine.
Click to expand...
Click to collapse
I'll try to get it. Do you want the whole dmesg output or just a specific part?

faced with similar issue. Randomly some fake screen touches are taking place. Only pressing the on/off key helps to get it back to normal state. Do anyone have any suggestions or ideas?

ogray said:
faced with similar issue. Randomly some fake screen touches are taking place. Only pressing the on/off key helps to get it back to normal state. Do anyone have any suggestions or ideas?
Click to expand...
Click to collapse
I've had the same exact issues on the stock rom when I purchased it at release day. Issue has never come back after flashing tiamats roms
Sent from my Nexus S using XDA Premium App

ryan562 said:
I've had the same exact issues on the stock rom when I purchased it at release day. Issue has never come back after flashing tiamats roms
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Flashed with Tiamat ROM but the issue still remains. Xoom is going crazy.
I'm afraid it's kind of hardware problem, maybe something related with static electricity. Not strong in this.
Can't return it to Motorola as it was bought it US by another person
Anyway, thank you, ryan562
Any other ideas/suggestions are welcomed

ogray said:
Flashed with Tiamat ROM but the issue still remains. Xoom is going crazy.
I'm afraid it's kind of hardware problem, maybe something related with static electricity. Not strong in this.
Can't return it to Motorola as it was bought it US by another person
Anyway, thank you, ryan562
Any other ideas/suggestions are welcomed
Click to expand...
Click to collapse
BINGO!!! When my ionic air purifier is on, my touch is out of control.

Charlie_Don't_Surf said:
BINGO!!! When my ionic air purifier is on, my touch is out of control.
Click to expand...
Click to collapse
Well, I don't have any potentially dangerous devices at home neither in office. It gets crazy randomly (as far as I can tell)
Sometime I can use for couple of hours, but sometimes I have to switch on/off every 5 mins

Tried newest Tiamat ROM. Still got the same. Seems it's really hardware issue

ogray said:
Tried newest Tiamat ROM. Still got the same. Seems it's really hardware issue
Click to expand...
Click to collapse
Have you applied a screen protector on it that required liquid to install it?
My Xoom touchscreen briefly malfunctioned the other day as it kept thinking I was touching the lower right part of the screen. A power cycle cured it for now, but I hope it does not return.

I applied screen protector, but not very carefully. Leaved some air bubbles. I thought they were causing the issue and removed the protector completely.
Right now there is only silicon case. I was able to reproduce the problem without case

My Transformer is DEAD [email protected]#%^$&

History: It's a 2-month old B40 16GB TF w/o the Dock. It had some issue @1.6GHz but no prolem @1.5.
It had been on PrimeROM from day 1. Recently I tried Clemsyn'sROM_3Final: 1st day was no
issue at all (PimmyCPU locked to 1.4Max). On the 2nd day the battery drained (16hr sleep w/50% battery left)
This is the 1st time I've seen this.
I plugged it in and the TF didnot turn on automatically but it charged to 98% (from 3%) after a few hrs.
I uninstalled PimmyCPU and reloaded SetCPU, set for 1.2GHzMax and went on to read an eBook. After 30min my TF
just hang. So I turned it off (holding the Power-button) and it never wakes up again.
Debug: * Plug & unplug doesn't turn it on automatically (I tried a different charger&cable, I have two TFs).
* Tried different ways to turn it on w/o success. My PC doesn't see it (USB-mode) and I did checked HMDI-to-TV.
* Can't get to CWM.
* I can only get my PCs to see it thru APX (Power & Vol+ works). Remove&replace USB driver multiple times even
tried on a different PC. I attempted NVFlash many times: my PCs could see the device but hung-up at "waiting for
bootloader.ini to initialize". I could see the TF didn't go into APX server-mode (nothing on its screen).
Now: * Just wait for the battery to drain completely, may take days. Don't know if this would help.
* To RMA I need to NVFlash it back to Stock, but can't.
I will take the blame for rooting but don't think it's the cause.
I may do the RMA and hope they change out the dead board and never know it was rooted.
If they found out and refuse the warranty then they can just throw it in the trash-bin for me.
Sorry for this long post. Any comments ? Thanks.

If the board is dead, then they won't find out about rooting (unless they want to go through the trouble of getting at the onboard storage even though the board is dead). I would suggest RMA'ing it and hope that they don't go through that process.
I'm sure they won't because of all the repairs they have to deal with anyway. People just hate those little imperfections

You might have cooked the cpu.
Don't throw it out, you can still use it as replacement parts (like speakers, screen, battery etc..)

makec3rt said:
You might have cooked the cpu.
Don't throw it out, you can still use it as replacement parts (like speakers, screen, battery etc..)
Click to expand...
Click to collapse
Good idea ! But..but, if the RMA isn't going thru it would take $$$ to get it back for spare-parts.
I don't actually need to overclock, I felt my TF was fast enough. I might only OC for a day or two and usually undervolted (max was 1100mV). My TF spent most of the time here running @1GHz.
So far, I don't think the battery has drained yet. No progress. I will wait a couple more days before filling out the RMA form online.
Anyway, I really miss my TF. Luckily, my GTab came to the rescue. Besides the bad viewing angle, this thing is built like a tank. Everything just works as expected. Running Gingerbread blows HC out-of-the-water, maybe due to bloated OS. It's a speed demon even @1GHz.

This is going to sound stupid, but you unzipped the rom into the nvflash folder right (im sure you did, but that is the only thing that came to mind)
hyperxguy said:
Good idea ! But..but, if the RMA isn't going thru it would take $$$ to get it back for spare-parts.
I don't actually need to overclock, I felt my TF was fast enough. I might only OC for a day or two and usually undervolted (max was 1100mV). My TF spent most of the time here running @1GHz.
So far, I don't think the battery has drained yet. No progress. I will wait a couple more days before filling out the RMA form online.
Anyway, I really miss my TF. Luckily, my GTab came to the rescue. Besides the bad viewing angle, this thing is built like a tank. Everything just works as expected. Running Gingerbread blows HC out-of-the-water, maybe due to bloated OS. It's a speed demon even @1GHz.
Click to expand...
Click to collapse
About gingerbread, i wish someone would port that over. I mentioned it once before and everyone was like, why would you want that?

Thanks for the suggestion. I've used NVFlash a few dozens times (mostly with my Gtab) so I could do this while sleeping. I have multiple nflash folders for different devices & situations (root, unroot, root w/ROM1 ....).
I think my TF is 99% dead. It appears that it could get into APX (seeing thru my Win7PC). But it can't turn into APX server-mode. It stuck @bootloader.bin which isn't a part of the ROM.

Mine is dead too as of this morning. I got a splash screen briefly and then the screen went blank. After multiple attempts to reset / long power hold I managed to get it into APX. tried to reflash and got this output from the pc:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 976013/976013 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
usb read error (75): Value too large for defined data type
bootloader failed NvError 0x0
command failure: bootloader download failed
I'm going to try later with an older bootloader but if that doesn't work then this has to be RMA'd.
Ironically my dock is being collected today for the MobileDock Battery Saver issue.
I'm not happy with this product anymore and I'm seriously considering selling and going for another tab.

Oh no, Roach, this suxx, how you gonna provide the best ROM now ? Got a spare one ?
Don't give up on us after so much hard work

Sorry to hear about your problem, Roach. At least you got a little further than I did, my nvflashes would stay at "waiting for bootloader to initialize" forever.
The unit is on its way to Asus for repair.
I hope you hang on to supporting the TF. I was hoping I will get my unit repaired and ready for your Prime1.7 ROM (HC3.2).

Roach's is now working, let's hope he shares how he did

Have you tried using the bootloader.bin that matches your rom? I.e., if you have a 8.4.4.11 rom, use the blob.EBT from the 8.4.4.11 update.
However, the downside, is that I think this will only boot once. When you shut it off, it will be bootloops or APX mode only.
I think nvflash is like a fastboot boot command, and only uses the bootloader to load the system. I don't think it actually writes partition 4. The only way that I found to write partition 4 is use the --create command, but that will wipe your TF completely. If you have backup images, you can flash them by updating the flash.cfg file with all the file names. I wasn't able to flash /data (part 12_USP), but CWM restored it after I restored with nvflash.
I think this tablet is unbrickable, short of a dead cpu. For grins and giggles, I flashed the nvidia android developement ROM- what a nightmare! It was an android zombie! It's set up for hardware buttons and a different screen size. Luckily, APX mode still works and it's back from the dead.

gee one said:
I think nvflash is like a fastboot boot command, and only uses the bootloader to load the system.
Click to expand...
Click to collapse
I could be wrong, but I'm pretty sure that the NVFlash functionality (APX mode) is baked into the Nvidia chipset itself. You can hose everything (including the bootloader) and still be able to bring it back from the dead. I refuse to hack a tablet without it anymore, as it saved my bum from all the times I screwed up flashing my GTablet.
I think all phones, tablets, and other devices should have this mode (or something similar) standard, it would keep noobs from being able to brick their devices and pester the manufacturer for a replacement under warranty (which they shouldn't get).

bud77 said:
Roach's is now working, let's hope he shares how he did
Click to expand...
Click to collapse
Nothing was actually 'wrong' with mine. I had a n00b moment, that's all I'm saying.
I hope that the others in this thread with real issues get them worked out soon though.

Final status
Just got the TF back from RMA, they concluded the case as NoTroubleFound ?!?!
The unit was dead with PrimeROM + OCkernel (I had no way to clean it).
It appears they openned the unit (new frame which no-longer creaks). Everything was wiped clean with stock 8.4.4.11 (except my customed bootanimation is still there but only runs the first portion).
I just did a NVFlash straight to Prime1.7 and everything is great (my customed bootanimation is now gone). I'm back in business (dogged a bullet there).

LS996 Keeps boot looping

At first starting to use a new charger the phone would have the screen go black in the charge was low, but now it keeps on rebooting.
The phone allows me to enter the Android system recovery but even after a factory reset the phone will continue to act in this manner.
No OS updates were applied prior to this and the device is still locked and hasn't been tampered with.
I'd really appreciate it if I could get some help with this.

Exactly the same happened to me 2 days ago,i cant get pass the LG logo,even if i can it will restart after 1 minute of use. I sent it to service for repair. Reinstalling OS might help at some point,but if it keeps restarting like mine i dont think its possible,but if you can access recovery then do it. I will give info after i get it back. If you wanna do that,just download LG UP and kdz somewhere from xda,you can get it on xda easily.

We have that issue discussed in Q&A session. There's two possible root cause. Easier one is caused by the controller chip on the battery gone crazy. That one can fix easily by replacing the battery. The more unfortunate ones have got issue with the CPU Chip Solders disconnected. (G4 users also faced that issue quite a lot). For those ones, there's no way but to replace the whole circuit board. Someone suggested about baking (yes, baking the chip in the oven) and let the solder reflow to reconnect. But no one tried it yet. (Linus TechTip tries on a dead Nvidia Graphic Card and it works, but beware that the phone circuit boards are more delicate than the PC graphic cards).

My Lg G Flex2 h950 is having similar problem. I cant get pass the LG logo. It just keeps restarting. How can I solve this?

Mi Mix 3 Bootloop after screen replacement

Hi, I'm new to the forum and to mobile operating system troubleshooting in general. I'm hoping to gain some insight into an issue I'm having.
I broke the screen on my mi mix 3 and after waiting for 2 months it finally arrived from Shenzhen. Yesterday I disassembled the phone, connected the new screen, turned it on, and it just went into a bootloop. I've never changed any part of the operating system on the phone before so I just assumed something was making a poor connection. I unplugged all the leads and plugged them back in again, checked that everything was firmly in place, and ended with the same result.
Fastboot will run sometimes for 10+ minutes and then the phone will just shut off, normal booting it will switch from "Mi" to "MIX" and the animation at the bottom of the screen will freeze after a couple clicks and it will loop back to restarting (but twice it has just ended with an all white screen). Rebooting from Mi Recovery mode results in the same.
From what I've seen I'll just need to follow this and flash the phone : https ://c.mi .com/thread-2504118-1-1.html?t=1590725045909
But my question, is there any possible way to try to fix this issue without loosing all my data and without using a back door method that may just brick the phone?
Thanks for any help, btw I still have the back glass off (I've tried with the fingerprint scanner plugged in, nothing) just in case it could somehow be a hardware issue.

So I've given up on trying to save my data, I don't really care much about that to be honest. I just really like this phone and would like to use it. I tried to flash the phone using Miui's official instructions but I can't unlock the bootloader because I can't download the app Miui's flash tool is requiring me to download on the phone to authorize it.
I guess I'll keep looking for a work around.

TheUnibomber said:
So I've given up on trying to save my data, I don't really care much about that to be honest. I just really like this phone and would like to use it. I tried to flash the phone using Miui's official instructions but I can't unlock the bootloader because I can't download the app Miui's flash tool is requiring me to download on the phone to authorize it.
I guess I'll keep looking for a work around.
Click to expand...
Click to collapse
I changed my display too and it's bootlooping. Did you solve this problem?

I changed my Display too...everything worked fine when I tested it. I unplugged it again to clean the phone and to bring on the glue..when I had the Screen on I restarted and had a black screen...so tried to remove the screen which then just broke...so I ordered a new one and a new display flex cable - I didn't glue the screen yet because I either experience black screens when the screen gets pushed against the backplate or the phone ends in a bootloop -> for the bootloop thingy I just waited for about 10 minutes and then it started normally so there must be something with replacement screens...I don't know whats going on -.-

Hi
Has anyone managed to get this fixed?
The screen works initially but after a while it goes blank, reboot I get the Mix logo not mix 5G. The replacement is a LCD.
Looks like it is stuck in bootloop as inserting sim does phone does not ring when I call it nor front face camera clunk when I slide it

Question Black Screen of Death

Have any of you gotten the black screen of death with your P7P?
Over the weekend, my screen appears to have bit the dust. I was playing a game and the screen went weird. I saw snow, chunks of different apps and such, and then the screen went black. I tried rebooting and googled the issue. Tried all the suggested solutions and none worked.
My screen is completely dark, even from boot. No google logo during boot.
Phone appears to be running as I get haptic responses to the buttons when it's on, just nothing on the screen and no responses to touch.
ABD sorta works, but sees the phone as unauthorized (worked fine on that laptop before). Only thing I could do was get into fastboot. Tried the A and B slots with the same results.
Google told me to take it to a warranty center as I'm outside the return period. Fortunately I have one close by. It's just annoying that it died after barely two weeks.

Superguy said:
Have any of you gotten the black screen of death with your P7P?
Over the weekend, my screen appears to have bit the dust. I was playing a game and the screen went weird. I saw snow, chunks of different apps and such, and then the screen went black. I tried rebooting and googled the issue. Tried all the suggested solutions and none worked.
My screen is completely dark, even from boot. No google logo during boot.
Phone appears to be running as I get haptic responses to the buttons when it's on, just nothing on the screen and no responses to touch.
ABD sorta works, but sees the phone as unauthorized (worked fine on that laptop before). Only thing I could do was get into fastboot. Tried the A and B slots with the same results.
Google told me to take it to a warranty center as I'm outside the return period. Fortunately I have one close by. It's just annoying that it died after barely two weeks.
Click to expand...
Click to collapse
This has happened on other devices; the 5a apparently had a significant problem with this. The fortunate thing is, fixing it usually just takes a few hours, although the repair center might need to wait for parts.

If you can get into fastboot then use Google's Android flash tool to reinstall. I had something very similar and I was fine after reflashing

Have you enabled systemless hosts on Magisk? Can you boot in to the safe mode?

miimaa said:
Have you enabled systemless hosts on Magisk? Can you boot in to the safe mode?
Click to expand...
Click to collapse
Yes. No.

miimaa said:
Have you enabled systemless hosts on Magisk? Can you boot in to the safe mode?
Click to expand...
Click to collapse
I'll take a look at it if I have time tonight, but have an emergency dentist appointment after work. May just end up taking to Asurion in the morning in case it is hardware.

V0latyle said:
This has happened on other devices; the 5a apparently had a significant problem with this. The fortunate thing is, fixing it usually just takes a few hours, although the repair center might need to wait for parts.
Click to expand...
Click to collapse
That's what I'm wondering since the phone was released only a few weeks ago.

First shop in my area I called said they didn't have parts and couldn't get them yet.
The other one was familiar with the problem with the 5a's and had a 7P screen in stock, thinking it was likely hardware. I'm taking it over tomorrow morning.

Superguy said:
Yes. No.
Click to expand...
Click to collapse
I blame systemless hosts.
My device freezes up when I enable that. There are few users with same problem. But there are majority who have no problems.

If fastboot mode is also blank, its hardware fault.

and you've tried to turn it off by holding power and both volume buttons together for up to 30 seconds and then turning it on?

engage4 said:
If fastboot mode is also blank, its hardware fault.
Click to expand...
Click to collapse
Yeah, that's what the problem typically has been with the 5a. No idea what causes it; my wife was just scrolling through social media when it froze up, then the screen went black, and the phone wouldn't turn on again. It was visible via USB as as a QPST target (Qualcomm 9008 bulk something or other) so my assumption was the bootloader somehow got corrupted. I'm not sure how, since this was not during an update. Fixing it involved replacing the mainboard.
Generally when a display fails, you'll get artifacts on the screen but the device will still work, more or less.

If a qualcomm phone switches to 9008 mode in the middle of operation its either EMMC fault. Either emmc is damaged or emmc to cpu connection break.