Database Info

[Q] Touchscreen failing to respond to touches

I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.

GideonB234 said:
I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.
Click to expand...
Click to collapse
No fix. Have had exactly the same kind ot issue on a friend's Desire S,which needed replacement. Don't hesitate about restoring S-On and sending it back to HTC. That's the best course of action to take if you're under warranty...
Sent from a Desire S still looking for a good replacement.

Ah, I got my phone basically a year ago next week so I'm not sure if that means its not in warranty anymore.
Its working better now if I don't type really fast, but it is definitely a hardware problem then?
Sent from my Transformer TF101 using XDA Premium HD app

how to back to s-on?
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002

aarnoldaas said:
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002
Click to expand...
Click to collapse
Read the INDEX. Link in my signature. It has all necessary thread links for you to get back to S-On. Read about it and see if you get a hang of it. Then ask questions in the respective threads. Much easier that way than repeating everything all over again. 90% of your questions will be answered while reading the comments, and also some that you haven't thought of yet.
Cheers.

I think I'll hold out until I can get my hands on a Galaxy S or something similar (and then put MIUI on that and sell this phone or something)
Thanks for the help anyways
I'll tag this as solved (if I can)

[Q] Softkeys + Bottom of the Touchscreen not working

Hey!
About a week ago, after rebooting my device, the softkeys at the bottom of my screen stopped working as they´re supposed to do. When i tried to press a button, nothing happened. However, if i would press slightly above the actual button it worked fine.
But now (after flashing other roms in order to fix it), even that wont work anymore. In addition, when in Recovery(TWRP), a line of about half a centimeter at the bottom of the screen above the Softkeys is unresponsive too, preventing me from navigating back etc.
Don´t know if thats a possible cause but this happened some days after I installed a Rom with Sweep2wake for the first time. Worked fine until the problem appeared.
Things I tried yet: Flashing several different Roms(Cm9,Cm10,IceColdSandwich,FalloutEvolution,Andromadus), Factory Reset, Calibration (didn´t expect it to work but worth a try ^^),Using the Search-Function.
Specs: Unlocked SAGA PVT Ship S-ON Rl
Hboot 2.00.0002
Rom i used when the Problem appeared is Cm10.
If any additional Informations(Logcats,whatever) are required, just ask.
Help of any kind would be really appreciated!
Thank you very much and have a nice Weekend.

As long as you are S-On, you should maybe send it back to HTC if you have the warranty, since it is more of a hardware problem than a software problem (maybe the sensors are not in the right place). But before you do that you should change the hboot version to 0.98, since they can see that you unlocked your bootloader and the warranty would be gone. And you also should backup your data, so that you have a fallback positon,

Thanks for your reply!
I forgot to mention that I unlocked it via htc-dev. I didnt change the Hboot-Version, so why would you advise me to change Hboot?
PS.: Ordered at amazon,so thats where i would send it back to.

The reason you should downgrade hboot version is that they can't see if you unlocked it via htcdev or not. Normally if you would unlock it via htcdev you can see that the bootloader is unlocked and there is no way to put it into previous state (you can only put it into relock, but your warranty would be still gone). So I advise you to downgrade the hboot version to 0.98.00000 and flash a stock Rom, since HTC only accept stock Roms, S-On and locked bootloader.
P.S: You instantly get locked bootloader as soon as you downgrade and lose your S-off, just follow the steps in the Android Development section carefully
P.P.S: Does anyone know where the Desire S gets repaired when you send it back to Amazon?
Sent from my HTC Desire S using xda app-developers app

Is it actually possible that this has something to do with Sweep2wake? Just wondering, because this problem appeared while using a ROM with Sweep2wake for the first time.
EDIT:
I just activated visual touch feedback to see what happens when i touch the softkeys or the screen at the bottom 0,5 cm. The "visual touch response point" always appears centered at the top of the area not working. I made a picture with my old e71, very sorry for the horrible quality and my mad Paintskills . Pink arrows leads to the visual touchfeedbacl, green one to where i actually touched the screen.
EDIT2: Forgot, the picture, but im actually not able to post the link due to my low post count..
Isn´t that a sign that it is not hardware related?

[Q] How to i change my CID and allow OTA updates

Hi,
i recently got an HTC One S phone (used, no warranty). The phone seems to have been "played with" as it had Super User installed. However it was acting wierd so i did a factory recovery using the boot menu. This meant Super User was gone.
I am totally new to the updating an HTC phone, i found doing firmware changes to Sony and Samsung phones to be pretty much more easier!
My needs are pretty basic ! which is i want to achieve the following
I want to change my phone to have a normal CID without depending on carrier delays for updates (my CID is ORANG1)
I do not want to install a custom ROM, i want OTA updates to happen
I want to have my phone get the OTA update for Jelly Bean
When i boot into the phone (volume - + restart), i see the following,
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.3150S.19_2
OpenDSP-v21.1.0.32.0314
eMMC-boot
Mar 15 2012, 23:37:23
Other facts
My CID - ORANG1 (using CID getter app)
Phone model - S4 Z520e
I hear the Jelly Bean update sorts the helicopter issue with the HOME button, though i am not sure if the restart issue when browsing with the stock browser has been resolved. The helicopter HOME issue is driving me nuts.
Appreciate if someone can provide me the steps about how i can go about getting my phone CID changed and the OTA udpates working for the new CID, as searching the forums have not really helped me nail the way i can go about doing this.

Before we get started I'd like to know your home country (sorry I don't know your flag) and whether you're on stock or custom recovery.
As I'm on this device from the very beginning and know almost any corner in this forum I'll point you out where to find the things and information you'll need and some advantages as well as some disadvantages of what you want. Also I'll point out an alternative.

rootrider said:
Before we get started I'd like to know your home country (sorry I don't know your flag) and whether you're on stock or custom recovery.
As I'm on this device from the very beginning and know almost any corner in this forum I'll point you out where to find the things and information you'll need and some advantages as well as some disadvantages of what you want. Also I'll point out an alternative.
Click to expand...
Click to collapse
Wonderful to hear a quick response.
I live in Sri Lanka (small Island nation located at the bottom part of India, last colonized by the British!). The situation is that i think i am in stock, as i got this phone used and though everything is functional the helicopter home button issue, phone freezing when i use the stock browser for over a few minutes, connection looses (all reported errors with 4.0.3 and even 0.4) means i need to get this to Jelly Bean to make the phone more usable as i love the size and speed of the phone.
To start of is there any way i can see if my phone is in stock or custom recovery? I just searched and found http://forum.xda-developers.com/showthread.php?t=2124349, does the instructions "Fastboot getvar version-main" work?
Another twist is that i have the much loved Windows 8 running on my PC, i am not sure if that will have any effect on any command executions.

Wait you got 1.06 Hboot I would not flash RUU or OTA if you got that because you can update what is needed or if needed for roms plus you don't have to piss about when flashing roms so if I was you don't do it.

Thank you and welcome to this forum!
Your bootloader is still at version 1.06. Which is very good, as yours and version 1.09 allow you to flash nearly everything (kernels, radios, etc.) from within your device. Bootloader versions higher than 1.09 don't allow this anymore. For flashing kernels and radios you then will need to get into the phones fastboot mode and use the Android SDK on your pc, typing things like 'fastboot flash boot boot.img'.
Let's get started with recovery. To root your phone you usually need to flash a custom recovery. TWRP is the only one working bugfree atm. You can download it here.
To flash it and doing other usefull things try to get comfortable with the HTC One S All-in-one-toolkit.
So why do I mention this, also you wrote that the only thing you want to do is udating straightly to JB?
After the OTA update you'll be on bootloader version 2.15. It's just one more thing from htc to lock their devices even more, as at this time they don't behave very friendly to the dev community. Downgrading the bootloader is kind of pain and not easy so, unless you're familiar with linux (I did it succesfully several times).
Also stock JB from htc has one more surprise: Your system folder will be kind of write protected, which means, also you seem to have full root, after a reboot your formerly deleted (you thought so) files wil be back. Also added files in that folder won't be present any more. That crap is hardcoded into htc's JB kernel and sources are not available atm. But this problem was solved by flar2, who wrote a kernel module to bypass this.
So your hardware issues are left. As I'm not concerned by this I can only summarize what I read about these in the forum. They are obviously hardware related and therefore independant from software. Somebody wrote, a new radio had helped, others write different. In summary you'll have to check this out for your device.
Let's resume at this point:
Your device is unlocked and at 1.06. It needs to be relocked for the JB update and it will have a less comfortable bootloader version afterwards and it will be hard to get rid of the crapware in your system folder, as you'll have to unlock and root again for doing so. And it's questionable the JB OTA update will fix your hardware issues.
So I'd recommend the following procedure (you could still do the OTA update at any time, I'll help you then):
- use the all-in-one-toolkit, flash latest TWRP
- Flash latest EU radio 1.11 from here with twrp
- restore JB from my nandroid backup (download 3.16)
- if you experience troubles with your wifi connection, flash these wifi partitions
- check if your hardware troubles have been resolved
- to get root use all-in-one-toolkit again and flash elemental kernel (by flar2)
It seems a lot of work, but it's worth it. PM me, if you need additional help or decide to do the OTA update.

wow, thanks so much for all the info. I will give this a try tonight as i have the phone @ home, using my One X as the regular phone until i get the One S sorted. Then i will hope push out the One X and keep the One S as my regular phone. I prefer the One S size which is more ideal for one handed operation, shame that HTC opted for a pentile display that took out the sharpness.
Also based on your suggestions would it be better for me to opt for a custom ROM than HTC standard to resolve my issues?

[Q] HTC One X (At&t, evita) believed bricked after ruu update

Earlier today I tried to update my HTC One X's firmware to 3.18 in order to install the latest cyanogenmod nightlies. First, I was confused at why the latest cyanogenmod nightly would not flash so after looking it up and figured out I needed to update the firmware but to do that I would have to relock the bootloader. Second, I had issues trying to relock the bootloader, eventually got that (did not know adb was updated). Third, after believing my nightmare was over, I quickly decided I would try to flash the latest evita ruu, which completed without any errors and I clicked finish. (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed) straight from HTC's website. Finally, after a few minutes I noticed that my phone did not have a notification led, nor was it booted into the lovely (opinions may differ) HTC sense 4.1.
That is the story of how my phone got to the state it is in. The state being no lcd in any way, no notification led, but I can still hear the phone being plugged into windows and can hear it shut down and turn on (with the windows usb sounds) when holding the power button and pressing it as if it worked and I was doing a hard reboot(about a 10 second press to shut down and get the usb disconnected noise). (Tried both adb devices and fastboot devices neither showed a device). Never have I seen this before and if I can get it working hopefully I will never see it again. Hopefully XDA's member's genius can make up for my stupidity. (most likely my fault being too hasty and skipping a step :silly.
Any questions about what I did or how I did it. Please ask!

Hey bud,
sorry about your troubles. I myself have just updated to ruu 3.18 and hboot 2.14 in order to flash the xylon rom. I'm not an expert at this: I'm just another person trying to get the best (vanilla) experience from his phone! Here's a couple things I noticed in my 9 hour trial & tribulation in going from 3.17 ruu + 1.09 hboot to the latest updates:
my pc also did not read my phone on a couple of occasions. Some parts of the process, I believe you have to be on your regular screen and the phone will reset into fastboot on its own. Later on, I had relocked my bootloader before I was supposed to, and was unable to write much. I just went back to step 1 and re-did everything (had to dig up a thread on unlocking my bootloader via htcdev).
my best friend helping through this was the hold power + vol down button. i kept going to stock recovery & rebooting my phone OR into fastboot and see which place I was supposed to be at.
as for your LCD being completely dead...I haven't come across that issue. The closest thing was when I was in RUU mode and there was only an HTC logo on the screen.
if you'd like, pm me and I can msg you the xda threads I used to get through it. I'm not sure how to approach the dead LCD, but I hope it all pans out for you.
I just wanted to share my experience, as a non-dev nor extremely savvy techie, I feel your pain brother.

Its not that the lcd is dead (unless it died after the ruu flash finished along with the notification led), more like it just wont turn on, along with the notification led, Where it would usually be on when plugged in, it just no longer turns on. Anyway thanks for your sympathy, I managed to jam the nano sim into my HTC arias micro sim slot without an adaptor (cyanogenmod 7 is its latest), so yeah at least I have a phone for the time being XD.

You flashed 3.18 with supercid and s-on. If you have supercid you need s-off before ruu to 3.18.
Sent from my HTC One XL using xda app-developers app

In other words, if you RUU'd with SuperCID and s-on, you're probably bricked.
Sent from my Evita

So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .

Starfrog6 said:
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Click to expand...
Click to collapse
Jtagg is probably the best option, if you're within a year you can try sending it to HTC, if they figure out how you bricked, which is possible, they will charge you ~$200USD to replace the board.
Good luck.

If you ran the RUU with SuperCID and S-on, its bricked. JTAG is likely your only option to get the phone running again. You can look into the unbricking thread in General, and the JET tool in Development. But to my knowledge, nobody has been able to unbrick from this condition (SuperCID + S-on + RUU or OTA), short of JTAG. Yes, Mobiletechvideos has been mentioned on here as on JTAG option. Can't vouch for them personally, but others on here might be able to.
If you phone is less than a year old, you can likely get a warranty replacement from AT&T. Ethically, its a bit of a gray area IMO. I'm usually not crazy about people making warranty claims for failure to read, and as a result of you having modded the phone (which SuperCID is). But in reality, it shouldn't typically be expected for RUU plus SuperCID to brick the phone (past RUUs have run fine with SuperCID).
HTC is typically less forgiving about warranty issues. So no reason to try with them over AT&T. AT&T will pretty much honor the warranty for anything but obvious physical damage. They don't care if the phone has been modded, or bootloader unlocked (not that they would even be able to tell in your phone's current condition).
http://forum.xda-developers.com/showthread.php?t=2181929

I was bricked too.
I tried to relocking my bootloader and flashing the offficial jellybean without doing S-OFF first and bricked mine. I tried everything here at XDA with no luck. I gave up and sent it back to HTC and they had it back to me running the official jellybean update in 2 weeks. and without any charge. I even got it back on my birthday. It is running smooth and fast with no lag at all.

HTC One X+ AT&T Version
Hello there,
I tried updating my phone from Android Version 4.1.1 to the latest Android 4.2.2
But after installing my phone has stuck in the HTC logo and its bricked.
Please advice me for further proceedings.
My phone details :
Updated ROM image from 1.15.502.1 to 2.15.502.1
***RELOCKED***
EVITARE_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.73.0000
CPLD-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-BOOTMODE: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Sep 30 2013,17:16:15
I have installed the RUU file which you have shared in the link above.
Please help me I need my phone in the working condition.

You're in the wrong forum. This is the HTC One XL forum, you want the HTC One X+ forum.
But, have you actually attempted to run an RUU from this section? Any RUU you find in this section is not for your device.
Sent from my Evita

Is this soft brick?

Hi, I was having issues so i ran a RUU by suggestion and reset my device. afterwards I unlocked, flashed twrp 2.6.3 (2.7+ doesn't work, just boot loop) and then i upgraded to hboot 2.14 so i could install the roms i wanted. since upgrading to 2.14 i was getting new errors so i tried to wipe the device and restart and now I did that all the files are missing.
I cannot mount anything or boot, so i can't install via recovery or sideload at all, because it can't mount to anything. I can't restore or do anything else because it can't mount the cache, data etc.
I tried running the RUU again but now i am getting error 117 and it can't detect the phone, and since it has no OS installed it doesn't go far enough to register with the RUU application, or so i believe.. the phone does work fine, can access fastboot and recovery, i just can't mount or install anything else.
I am currently
Unlocked
S-OFF
HBOOT 2.14 (TextRemoval)
TWRP 2.6.3.0 (Anything higher doesn't work, will just show htc logo(20s), then go to black screen(15s or so) and bootloop
CID:111111111111
Some suggestions would be great. I've run out of ideas and spent the whole day trying different things to fix it.

When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita

On twrp 2.7,aren't we supposed to delete the .twrp .twrp in twrp folder by using a file explorer? I remember reading that in pandasas twrp o.p
Sent from my Desire HD using Tapatalk

I didn't need to do that, but yes, if you experience problems that's the first thing to do. Reading the OP is essential, and reading the last few pages of a thread is strongly recommended.
Sent from my Evita

timmaaa said:
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
Click to expand...
Click to collapse
Firstly, thanks for your help timmaaa.
The RUU i used was:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed.exe
I simply went to the RUU list and picked the most recent one of my carrier.
I installed it and it worked and booted, however the touch screen did not work. This confused me more because the reason I did a RUU was because the 3 softkeys were no longer working prior, and I was trying to fix it.
I was then having issues flashing roms because of the hboot, so I upgraded the hboot to 2.14 to solve this, using the method and 2.14 Textremoval file in the thread here: http://forum.xda-developers.com/showthread.php?t=2156686
After installing the hboot fine, I then went back to install candykat (to be honest all i want is a working phone, any rom works for me) and then was met with the error that it could not mount E:cache. Now i was also having issues where the bottom buttons in the Recovery menu would not respond (not the softkeys under the screen) and so i tried fixing permissions to this. Either way I got it working again - but was just other strange thing.
I just formatted the phone after mounting it in twrp 2.6.3.0 so now its ready to continue. Not sure what RUU or rom or what to go with next.

You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita

timmaaa said:
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
Click to expand...
Click to collapse
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.

xlmama said:
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
Click to expand...
Click to collapse
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita

timmaaa said:
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
Click to expand...
Click to collapse
I was able to get the RUU working and the 3.18 at&t is now installed and working. However I'm now back to my old issue of the 3 capacitive buttons at the bottom not working.
Is there anything software related to fix this or is it likely a hardware failure? When i tap any of the 3 keys, at best it will activate a touch at the lowest portion of the screen on that particular y axis. Example: I press the home key; instead of going back to the homescreen it does nothing, and at most sends a touch command just above at the bottom of the actual touch screen area.
Also, if you think it is a hardware issue, would it be the digitizer? I see they are $30 or so on ebay and figured i could fix up the phone. Everything else works fine except the damn cap. keys
http://www.ebay.com.au/itm/Genuine-...gitizer-front-panel-replacement-/261100897324

During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita

timmaaa said:
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
Click to expand...
Click to collapse
At most the cap. buttons will light up / flash when the phone does a particular action, but no actual response or input of the cap. buttons registers. I'm going to order the digitizer from the link above and hope for the best. It doesn't clearly say it, but I'm assuming it does come with the digi + screen in one.

I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita

timmaaa said:
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
Click to expand...
Click to collapse
Hmm, thats a bummer.
On another note. I just picked up the phone and unlocked it and it started vibrating like crazy, opened up the message (sms) app and started inputing random keys on the onscreen keyboard. Definitly something malfunctional with the screen. Bottom cap keys not working and random bouts of the screen randomly inputing.

The vibe crazy thing sounds like what happened to me on an inspire. Flashed wrong firmware
Sent from my HTC One X using Tapatalk