[Q] An issue triggers the Tab 10.1 touchscreen not responding. - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Please don't try anything mentioned below, if you are not familiar with flashing roms and programming ! You've been warned !
The following steps had been done in 4 sets of Galaxy Tab 10.1 (from different sources), all touchscreens become unresponsive within a minute. The system is still running, volumn keys are working, orientation sensor is operational, even the clock and wifi signal is fine. The only problem is the touchscreen. All 4 devices are not rooted, brand new, fully charged, and now returned to Samsung for inspection.
WARNING !!! The following steps may cause you trouble ! I share these steps only because I think some experts here may be able to solve it ! I'm also looking for some proof, if the same problem occurs to Samsung Tab 10.1 devices in different countries.
The steps to trigger an unresponsive touchscreen :
(1). Download and install any file manager from the Market (skip if you already have).
(2). Browse to "/sys/devices/virtual/sec/sec_touch/".
(3). Select all files (excluding folders).
(4). Copy and paste to any other location that have write permission (such as sdcard). Some of the files are not allowed to be copied, so just skip it.
And then, in a short while, the touchscreen will not respond anymore.
The files mentioned in step 2, are some driver files of Atmel mxt1386 (the touchscreen hardware). It seems that users of Acer Iconia also have touchscreen issue, turned out to be using the same hardware.
I know that there are also many users that do not have any touchscreen problem. This may only because those files are not accidentally accessed yet. I'd rather hope that you have a different version of the hardware driver that does not have such problem.
I'd like to ask for help from experts and developers here. But please don't try it if you are not absolutely confident to at least restore the system. Please don't blame me if your Tab becomes un-usable.
For those who are willing to try (at your own risk), I'm much appreciated. And I'd like to say thank you to all of you. Your effort may be helping a lots of users who have this problem.

Hey idsam,
have you got any ideas how to fix touchscreen broken this way?

Im sorry, I dont get this.
To me its like saying "I removed my battery and now my device won't turn on"
So, if I dont mess around with my system files and touch screen drivers, then my touch screen will be fine?
If you mean something else, please explain

Yeah, you got wrong.
Topic starter made too complicated example. The simple description is: if you try to read files from /sys/devices/virtual/sec/sec_touch/ directory - you'll got broken touchscreen. Looks like this operation damages touchscreen firmware, though this won't happen with properly configured/written (by manufacturer) system.
So who wants to read from those files? Any software for any reason. E.g. a lot of users have bricked their devices by doing a full system scan with Dr.Web for Android antivirus.

Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.

idsam said:
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
Click to expand...
Click to collapse
When the touchscreen goes unresponsive, do other parts of the device still function? For example, when you hold down the power button, will the shutdown menu appear? When you rotate the device will the orientation change?
I have had an unresponsive touchscreen many many times. I'm not sure it is the same unresponsive touchscreen you talk about here. When mine goes unresponsive I can still use the power button and if I rotate the screen a few times it eventually becomes responsive again.

Yes. The power and volume up/down buttons work, orientation sensor also works as a normal device. I tried to rotate the screen, discharge and recharge the battery, but it aside for hours and tried again, nothing helps.
And it is actually confirmed by Samsung that hardware replacement is needed. They said that they tried to recover the device by flashing rom, but failed.

so I have the same problem. Quite frustrating. Not only that, I've noticed that there is a vertical 1-2 inch area from top to bottom of the screen that doesn't ever respond to touch.
I'm sending it to Samsung

Hi Idsam, I'm from Russia and have a same problem. After full scan by Dr. Web the touchscreen not responding and now I don't know what to do, beacause I've bought my Samsung in USA in Bestbuy, but now I'm at home in Russia, no warranty, no service, nothing. May be somebody can give me advise?

To be honest, it seems that Samsung doesn't have a solution yet. And probably worse, Samsung did not modify the driver at all, which means Atmel is responsible to fix the problem. No matter what, you can wait, but who knows how long it takes.
I think Best Buy has refund policy. You should discuss with them asap, as this kind of policy is normally time limited. You may consider to pay for delivery, in order to minimize your lost. If they refuse to refund for you, then you may need to contact Samsung Russia. I'm sure they know about this issue, and perhaps you may discuss with them. Still, you may need to consider to pay a little more as repair service charge.
BUT, I'm not saying you should pay more for what they've done wrong. It is only a suggestion, in order to speed up the process and at least minimize your lost.
The last option, I think, is to wait until Samsung announce a solution. If the method to fix it doesn't require hardware exchange, perhaps you may get information from Samsung and try to solve it by yourself.
As I know, when the touchscreen issue occurred, the Android system is actually still running WITHOUT problem. It means that you may still control the device by using ADB via USB. So, if Samsung can provide a patch, it may be easily fixed. I'm not sure if it is possible or not, just hope it will be as simple as that.

I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works

Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
---------- Post added at 07:28 AM ---------- Previous post was at 07:23 AM ----------
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
No, it doesn't help. Only one method left - use the hammer.

oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
AlexNovoross said:
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
Click to expand...
Click to collapse
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.

idsam said:
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
Click to expand...
Click to collapse
I hope Samsung can patch this up when they update to 3.2 if that update comes

Does this mean i Lost my Tap if that patch did't come out..
!!!???

Honestly, only Samsung can answer your question. But my steps can help you to show proof to them that it is a design flaw, and force them to admit that it is their responsibility to provide solution.

This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)

I have the same problem with my Galaxy Tab P1010. I can get into download and recovery mode i can move the selection using the volume button but i can't press the power to enter my selected option. I have already tried re-installing the latest available firmware for my device using ODIN 1.7. Eventually everything seems to be ok until i reach the point where you select the language. I can't select any option mainly because the touchscreen is unresponsive. All along i thought this problem is only software? Hopefully somebody can find the solution to this.

sp3dev said:
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
Click to expand...
Click to collapse
It seems that the second link is invalid. Besides, it is necessary to root the device and flash CWM recovery first, right ?
I mean, it may be a bit risky. I read your post before, but not sure if it is the same issue. If it is not, and the device is rooted, the official warranty may be voided too.

I have updated the links but the recovery image is only valid for the Iconia tablet. I mean, one could try using the attached driver sources and add them to the kernel but that will require at least flashing custom kernel. Samsung seems to be releasing a firmware update to fix this issues but people familiar with linux kernel development may try experimenting with the driver from acer.

Related

[Q] Galaxy GIO (S5660) bricked, I am unsure.

Hello everyone,
Firstly, I did not find a board dedicated to the S5660. So I posted it here.
Today, I tried to backup my current installation of Android to my SD. I used
a guide on androidpolice(dot)com, while searching for "complete android backup" in Google.
My phone had to be rooted, which it was, so I went on to download and install Clockworkmod's ROM Manager. I opened it up, fixed the permissions and made a backup. Before I could make one, I had to pick a phone model. However, these were all very strange types or brands I never even heard of.
I randomly picked one, and my phone NOT being listed should have served as a warning but alas, and the app started backing up. After it was done, it all seemed normal so I pressed "home" to go back to my main screen and pressed the "lock/power" button so my screen would turn off. I put the phone in my pocket.
Exactly 2 minutes later, I pull out my phone and I notice the screen is black, I push the lock/power button: nothing happens. I hold the lock/power button in the expectation that the phone will boot up since it might have been shut down accidentally. Nothing happens.
I remove battery, re-insert battery. I repeat this over a dozen or so times to no avail. I try the download or safe boot key-combinations (volume down + home + power) and nothing helps.
It's as if either all the keys are broken, something went seriously wrong in the interior hardware or hopefully, (the most simple possibility) my battery gave the ghost.
I went to the shop where I bought the Galaxy Gio and told them about the issues I had, they said they were going to send it to a Samsung Service Center for repairs. After I went home and had browsed the Internet for some possible solutions, I returned to the shop to try out several of the tricks that were listed (inserting battery on the exact same time when you press the buttons), nothing worked.
Does this smell to bricking or just a dead battery?
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Theonew said:
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Click to expand...
Click to collapse
It happened while I was at school, I immediately went to the shop and the guy helping me said he had plugged it in for a short while. I guess I believe him since I did not see it but he said the phone did nothing.
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Darmvlinder said:
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Click to expand...
Click to collapse
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Theonew said:
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Click to expand...
Click to collapse
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Darmvlinder said:
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Click to expand...
Click to collapse
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Theonew said:
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Click to expand...
Click to collapse
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Darmvlinder said:
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Click to expand...
Click to collapse
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Theonew said:
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Click to expand...
Click to collapse
I just sat through a Live Chat session with Samsung. Even though Google does not oppose rooting, Samsung effectively makes a deal out of it. I told him the same story, that an update through Kies made several things pop up on my phone which I did not understand etc. etc.
I am hoping for the best. But I am befriended with someone working in the store that sold the phone to me. He said most techs won't bother with low-budget smartphones (as in trying to grab you by the balls) and will much rather flash the phone with Samsung stock ROM.

[Q] Unbrickable Mod bricked

My Fascinate had an unbrickable mod done a few months ago. I tried flashing CM to it, and now it doesn't boot or go into recovery mode. Download mode is ok so far, but only with a jig. Windows and Odin can't see anything. On Linux (Ubuntu physical box not virtual) the 'unbrickable resurrector' (team hummingmod) doesn't find the device. Heimdall only prints a pit file after it first goes into dl mode, then just detects it but fails the loke handshake everytime until it goes into dl mode again. USB drivers were installed (libusb). Almost everything online says that the phone should be recoverable (like from a soft-brick) but the phone's not even getting detected. The place I mailed it to seemed to know what they're doing, but I'm wondering now if the mod was not done perfectly and if that could be causing this weird issue now. This is my main phone, and none of us are getting any younger so let's get some ideas on this asap.
Mainly, I'm wondering how to turn this from a paperweight back into a phone?
I would contact the people that did it and see what they say.
Unreliable repair site?
ndowens said:
I would contact the people that did it and see what they say.
Click to expand...
Click to collapse
I sent the repair place several messages, and they didn't respond. It's Mobile Tech Videos. When I first got the mod done a few months ago, they seemed ok. Now it's like they just don't even want to hear about the possibility of there being an issue with their work. I have friends that fix these locally, and they've also tried getting it to work using different boxes and setups so it doesn't seem like the problem is on my end (not saying it's definitely not, just doesn't seem so). I sent them messages asking whether they've had any similar issues, and if it's possible to rule out the original mod as the issue. Nothing, not a courtesy response. Nothing, like they just decided to ignore the whole issue. I actually left them some good feedback for them (originally), now I'm wondering if someone else will read that and think that this place is a reliable repair shop -- I'd feel guilty for steering them to the wrong place based on feedback that's no longer current. I could understand if they had assisted a customer in using the mod (that I paid them to do) and then that customer just didn't want to do anything, just complain, then yes I could understand that they'd not want to deal with that. But I actually just started by sending a message that there was an issue, and if they've got a workaround. Since I paid them to do this, I thought they'd at least respond. Nothing. So that could make a person wonder if they know that there's an issue with their work and just don't want to say. Personally, I'd say a business owner with integrity should either stand behind their work or issue a refund in good faith. That's the problem is that there's not enough accountability in these issues.
The phone seems pretty well bricked right now, and since A) it's one of the older original androids and B) this no one's responded here with any ideas and C) I don't know any one locally who I can trust to jtag it -- it seems more and more likely that this is a real brick.

[Q] Q/Help please read and dont be rude

Hello everyone!
It is obvious I did something REALLY wrong when experimenting with my Atrix 4g, and I would like to know if anyone here is willing to offer some guidance.
I must confess I am not VERY knowledgeable regarding Android phones (I have done it in the past with HTC’s running windows, so it’s been quite a while since then, but definitely similar to androids), BUT I learn VERY quickly and I know how to follow instructions (98% of the time)
So I think I might’ve soft brick it, and perhaps deleted files I should not. Anyway, also I would like to point that if I am NOT in the right thread, inform me where is the right place… in order to keep on going with my posts.
Once senior members/moderators consider this is the right spot for me, I will describe with further details what I have done.
I just can tell you, everything started without upgrades nor flashing the handset or anything alike… suddenly wifi and bluethooth stopped working. And since I could not pair it with my computer even after trying to use the USB cable, (I don’t allow my google account to handle my contacts) I decided to indulge myself and buy a new phone… and I bought a Moto RAZR but I like my Atrix and I want it working again
If you think you can help, or you are willing to help, feel free to ask what I have done, the steps I have followed and the threads I have revised. I have a little log of the things I have worked with and I know I have missed, surely, few important steps.
Thank you in advance for reading
Wow... This is got to be the longest list of disclaimers and precursors to an actual post EVER, lol.
You're asking a question. This is the Q&A section. You're good. Proceed at will.
For future reference, this kind of lenghty introduction and waiting for approval is hardly necessary. Just asj the question, the mods will move it if necessary, and you will only get lashed out at if the question is really trivial (so the solution can easily be googled) or has been answered enough times already (so the solution can easily be found by using the XDA forum search). Your question does kinda sorta fall into the second category, but since you're new here (and such a scardycat), let's let this one pass.
Based on your (very minimal) info, it kinda seems you have that dreaded problem where the wifi/bluetooth chip just dies all of a sudden... Unfortunately if that's the case, there is no known solution as that is most likely a hardware failure.
Yoy might want to go check some other threads (I'm on the phone so can't look for them now), some people have had limited success in dealing with this by applying pressure at certain points in the phone, usually by sliding a piece of thin plastic strip such as an old credit card.
You might however also want to describe your problem further, because it might not actually be this...
description of issues
ravilov said:
Wow... This is got to be the longest list of disclaimers and precursors to an actual post EVER, lol.
You're asking a question. This is the Q&A section. You're good. Proceed at will.
For future reference, this kind of lenghty introduction and waiting for approval is hardly necessary. Just asj the question, the mods will move it if necessary, and you will only get lashed out at if the question is really trivial (so the solution can easily be googled) or has been answered enough times already (so the solution can easily be found by using the XDA forum search). Your question does kinda sorta fall into the second category, but since you're new here (and such a scardycat), let's let this one pass.
Based on your (very minimal) info, it kinda seems you have that dreaded problem where the wifi/bluetooth chip just dies all of a sudden... Unfortunately if that's the case, there is no known solution as that is most likely a hardware failure.
Yoy might want to go check some other threads (I'm on the phone so can't look for them now), some people have had limited success in dealing with this by applying pressure at certain points in the phone, usually by sliding a piece of thin plastic strip such as an old credit card.
You might however also want to describe your problem further, because it might not actually be this...
Click to expand...
Click to collapse
Im sorry, if my disclaimer was a little too lengthy, but I detest to intrude in areas where I am not supposed to be and, even worst I dislike to be told "you are not in the right area" makes me feel moron... but thanks for the support... following you will find a detailed description of what I have done and my results
Motorola Atrix 4G MB860 from AT&T unlocked for other markets
handset suddenly stop working wifi/bluetooth
actions taken and results:
1: hard reset
wiped out all information contained in the handset but it DID NOT made the wifi/BT antenna work
2: apparatus left for aprox 8 hours without battery, then wifi/BT antenna seemed to be operative, at least for 8 hours, tuned it off and on...displayed error message.
3: after consulting several threads posted in this very same website and in this area... no information helpful was found, other than flashing a newer ROM.
4: second hard reset using, tried the HR found in settings... unsuccessfully, handset rebooted with everything in it as if I didn't hard reset it
5: third hard reset: using power button and volume button (for one strange reason I have to press not only the volume down button, but both, in order to start the RSD protocol) but it does not move beyond that point, so after some research.. I found out it has been softbricked, handset operative, but the aforementioned issues still going on.
6: after some research, here
http://forum.xda-developers.com/showthread.php?t=2277112
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?p=42407269
http://www.xda-developers.com/tag/fastboot/
http://forum.xda-developers.com/showthread.php?t=2262869
I found I could flash a newer ROM, specific for my equipment, downloaded it and followed the instructions provided in the threads
http://forum.xda-developers.com/showthread.php?t=1975893
followed the instructions, et cetera, deleted cache and ran the command fastboot erase system -w and, tried to flash the .zip file, handset recognised it, however displayed an error saying "no android info.txt" there were 3 messages total, all of them displaying the same file extension .TXT
I guess thats where I messed up big time... so whensoever you have a chance to reply let me know what could have been wrong..and pelase, let other geniuses out there in the forum whats going on and if they are willing to help me in this.
I will try to keep a concise log of the do's and dont's and what to do in case someone else share the same problem
thank you in advance to the XDA delopers team
So if I got it right, your phone is SIM unlocked but not bootloader-unlocked? Does it have "Unlocked" in the top left of the screen when booting?
If it does, I'd recommend installing MROM (not MROM-ICS as you suggested because that is a testing ROM). If the bt/wifi error happens there as well, then it is most likely a hardware failure and no software will help. In that case, I'd suggest trying a hardware method as described here.
If it doesn't, then I guess I'd try flashing a full SBF. Be warned however that flashing SBFs is potentially very dangerous, so be sure to read all the guides and select a SBF that is appropriate for your device (based on the OS version it had installed previously).
ravilov said:
So if I got it right, your phone is SIM unlocked but not bootloader-unlocked? Does it have "Unlocked" in the top left of the screen when booting?
If it does, I'd recommend installing MROM (not MROM-ICS as you suggested because that is a testing ROM). If the bt/wifi error happens there as well, then it is most likely a hardware failure and no software will help. In that case, I'd suggest trying a hardware method as described here.
If it doesn't, then I guess I'd try flashing a full SBF. Be warned however that flashing SBFs is potentially very dangerous, so be sure to read all the guides and select a SBF that is appropriate for your device (based on the OS version it had installed previously).
Click to expand...
Click to collapse
heheheh thats the one I downloaded and tried to flash.. unless i have picked the wrong file.. please let me know which is the one I have to download and I will try to install it... there are few options.. I just want to make sure I pick the right one
thank you!
There aren't actually many options. Just download the latest ROM package (not the update) and the gapps package. Flash ROM then gapps. That is all.
Thanx
I havent had a chance to follow up my work with the phone...
but anyway I have to thank you for all the attention and help
I will resume my work on it this coming days
and I will keep you posted on whats going on

[Q] Touchscreen disaster - P7510

Okay. My boss gave me his tablet to fix and he noticed the touchscreen did not work after the ICS update in August 2012 and he missed his warranty by 3 weeks. I have been using these forums for all my phones since my HTC: HD2. I'm obviously not SUPER active and I know everyone wants you READ READ READ before making new threads. But I know how to research, flash, and apply fixes.
I used adb to push the mxt1386_fixer.zip the sdcard and I flashed it. The touchscreen remains in the same state.
MXT1386_Fixer.Zip
I read about the A1 Kernal learning that the fix was also incorporated in it and it also didn't work. I have read and read and read for over a month and nothing I flash helps. It seems that when this model updated to ICS, the problem occurred. I am currently about to downgrade to 3.2 Honeycomb as a last ditch effort because my boss is just going to put it in a drawer.
NOW. Sometimes, the touchscreen works in the home, task manager button area. but what can you do with that? Not a damn thing. There has to be something that can fix this. A lot of people simply got a replacement and I hate to recommend that he needs to just sell it for parts. I never ask for anything. [because I find the answers myself] but I need help for once.
I put CM 4.0.0.4 on it and flashed all I can find. HELP!
a_skyll said:
Okay. My boss gave me his tablet to fix and he noticed the touchscreen did not work after the ICS update in August 2012 and he missed his warranty by 3 weeks. I have been using these forums for all my phones since my HTC: HD2. I'm obviously not SUPER active and I know everyone wants you READ READ READ before making new threads. But I know how to research, flash, and apply fixes.
I used adb to push the mxt1386_fixer.zip the sdcard and I flashed it. The touchscreen remains in the same state.
MXT1386_Fixer.Zip
I read about the A1 Kernal learning that the fix was also incorporated in it and it also didn't work. I have read and read and read for over a month and nothing I flash helps. It seems that when this model updated to ICS, the problem occurred. I am currently about to downgrade to 3.2 Honeycomb as a last ditch effort because my boss is just going to put it in a drawer.
NOW. Sometimes, the touchscreen works in the home, task manager button area. but what can you do with that? Not a damn thing. There has to be something that can fix this. A lot of people simply got a replacement and I hate to recommend that he needs to just sell it for parts. I never ask for anything. [because I find the answers myself] but I need help for once.
I put CM 4.0.0.4 on it and flashed all I can find. HELP!
Click to expand...
Click to collapse
Downgrade proves ZERO touchscreen abilities. Upgrading again.
a_skyll said:
Downgrade proves ZERO touchscreen abilities. Upgrading again.
Click to expand...
Click to collapse
4.0.4 provides the best touchscreen capabilities this thing will allow and I realized the touchscreen immediately reacts to my touch on the left and right sides only. the middle is shot. Thought if I could install TouchScreenTune, I could mayyyyyyyyyybe help re-calibrate the dead area and aid this issue. But I think it's done. Because the screen is only dead in the middle, it may just need a new screen and digitizer. With this tablet being very old news now, I doubt it's worth it.
If you can open it, you may need to check if the digitizer is properly connected. What you are describing sounds like a case I came across once here which the owner solved when he opened it and discovered that the connection had somehow shifted and by simply reconnecting the digitizer more firmly, the problem was solved.
Cheers.
Sent from my GT-P7500 using xda app-developers app
It was the digitizer strip the whole time. The whole left side was hanging out of the port. I gave the tablet back to my boss for christmas. He was happy and although he didn't pay me a dime, I was glad to finally fix it. So thank you!

[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]

[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
bear.are.cool. said:
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
Click to expand...
Click to collapse
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
And NO, providing your device is S-ON you CANNOT BRICK IT
thanks
Lloir said:
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
thanks
Click to expand...
Click to collapse
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
bear.are.cool. said:
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
Click to expand...
Click to collapse
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Lloir said:
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Click to expand...
Click to collapse
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
bear.are.cool. said:
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
Click to expand...
Click to collapse
Probably
Sent from my Nexus 7 using Tapatalk
Lloir said:
Probably
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
bear.are.cool. said:
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
Click to expand...
Click to collapse
Just a question. When you replaced the display, did you tamper with brightness control? I mean were you able to change the brightness after your repair?
And secondly, logically, I think its a hardware fault. Whatever happened, might have happened over the week or happened that specific day. Maybe the wire connecting the charger socket to the phone's board got cut/damaged during repair but worked for a while, then it imght have touched another wire and short circuited maybe?
Or maybe something inside was loose, and something happened to the phone, it fell or something, and a component got broken?
I would suggest comparing your internals to the internals of another HOX+ whether on youtube or whatever. And try to check the wire connecting the charger socket to the board. Another possibility is the battery got damaged as you stated. The last idea is, (And I hope it didn't get to that), the wire short circuited and fried the board.
All my theories are just as stated.. Theories, which may or may not be true. If there is an HTC Care center, I would suggest that you go to them, atleast for debugging.
Best of luck

Categories

Resources