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?
Related
Hi everyone
Phone: HTC Desire S
I downgraded my hboot from 2.00.0002 S-ON to hboot 0.98.0000 S-ON following this guide http://forum.xda-developers.com/showthread.php?t=1318919 and now my touch screen is close to not working at all. To large stripes in the middle (above the "options"-key, running top to bottom) are not responding to touch. If I touch in those areas the behavior is unpredictable. Sometimes the touch is registered, sometimes it's not, sometimes two touches instead of one are registered and so on.
When I come to think of it this problem was there right away, after i flashed to 1.28.401.1 using RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.08 0 5U_38.03.02.11_M_release.exe.
I was about to blame CyanogenMod (which was my end goal to get on the phone), but when I come to think of it the Android 1.28.401.1 had touch issues to. I only used this version of Android to turn usb debugging back on before moving on to flash Cyanogen. So I didn't thoroughly check the touch functionality at that time, but I remember it jumping between menus, checking options I didn't press and so on. So the touch screen stopped working before CyanogenMod.
The phone had no glitches before the hboot downgrade.
Are they software related? Can I fix them? Any suggestions?
So I tried a ROM called SHADOW HAWK V2.1. It is build on the Saga Europe 2.10.401.8 base/official ROM and the problem with the screen is still there.
Should I try to revert all the way back to stock (remove clockwork mod, replace the revolutionary hboot with the official one, use an official RUU and do all updates available on the air) ?
Okay, so I'm not back to
Android verison 2.3.5
Software number: 2.10.401.5 (sense 3.0)
S-ON, HBOOT 2.00.0002
Re-Locked
and still the same issue. I would like to believe it is a hardware problem, that the dying of the screen simply coincided with my decision to try out cyanogenmod (which caused me to downgrade, flash, unlock etc).
But the phone just got back from repair where the replaced the screen, so it should be a brand new screen. The repair note said: "Display module replaced".
Could this software tinkering have physically damaged the hardware?
EDIT: Could some kind of synaptic driver / firmware be missing or in need of being flashed manually ?
No one who has experienced something similar?
The touch screen (or some other hardware) malfunctioning after flashing new roms? After all the hboot downgrade took the flashing of a new rom, so maybe the topic should have been "touch screen problem after flashing rom"...
Thanks again
Wuhtzu
i believe that it could be a hardware problem ... i have never faced problem like this after downgarde Hboot ... i did it without any problem
sorry my friend i would like to help but i have no solution for that isuue but i will try to search
odda said:
i believe that it could be a hardware problem ... i have never faced problem like this after downgarde Hboot ... i did it without any problem
sorry my friend i would like to help but i have no solution for that isuue but i will try to search
Click to expand...
Click to collapse
Thank you for your reply Odda. I was not looking for a solution. All I hoped was that you would say "I downgraded like you did and my screen did not stop working"
Since that's pretty much what you have said I'm kind of glad because it makes it more likely that it simply was a hardware failure not related to the downgrading
wuhtzu said:
Thank you for your reply Odda. I was not looking for a solution. All I hoped was that you would say "I downgraded like you did and my screen did not stop working"
Since that's pretty much what you have said I'm kind of glad because it makes it more likely that it simply was a hardware failure not related to the downgrading
Click to expand...
Click to collapse
Completely agree with ... i downgrade my Hboot for my desire S . and my screen working normally
You were all right. The screenproblem had nothing to do with the hboot downgrade. It was a hardware failure. I got the screen replaced by my telecompany (I had a insurance via them against smalla accidents).
I Don't Have this Touchscreen Problem,
Hi guys this is my first thread so i hope i have posted in the correct section, and posted the right info.
a couple of days ago, i bought a HTC Sensation XE off of a online website.
it is an unlocked phone, and i am using it on telstra.
the reception on it was poor, so i thought i might flash a x.xx.401.xx baseband to it, and see what happened.
so i unlocked the bootloader with HTC Dev. then i flashed clockwork recovery mod 5.0.0.2.0 onto it using ADB. i then flashed Android Revolution HD 6.6.3 onto my phone. this was without it being S-OFF and it was not rooted.
i was really excited, but none of the features i had hoped for came with it (likely because i wasnt rooted) so i decided to flash a stock ICS rom onto it.
so, i have done all of that.... AND NOW MY WIFI DOESNT WORK!!!!! I LOVE MY WIFI! when i try to turn the wifi on, it just says "error", to the left of the on/off toggle at the top of the settings screen..
any ideas on how to fix it?
please help to try and fix it
the_gingerbread_man said:
Hi guys this is my first thread so i hope i have posted in the correct section, and posted the right info.
a couple of days ago, i bought a HTC Sensation XE off of a online website.
it is an unlocked phone, and i am using it on telstra.
the reception on it was poor, so i thought i might flash a x.xx.401.xx baseband to it, and see what happened.
so i unlocked the bootloader with HTC Dev. then i flashed clockwork recovery mod 5.0.0.2.0 onto it using ADB. i then flashed Android Revolution HD 6.6.3 onto my phone. this was without it being S-OFF and it was not rooted.
i was really excited, but none of the features i had hoped for came with it (likely because i wasnt rooted) so i decided to flash a stock ICS rom onto it.
so, i have done all of that.... AND NOW MY WIFI DOESNT WORK!!!!! I LOVE MY WIFI! when i try to turn the wifi on, it just says "error", to the left of the on/off toggle at the top of the settings screen..
any ideas on how to fix it?
please help to try and fix it
Click to expand...
Click to collapse
It's probably the HTC-DEV unlock that made this error. Try to unlock your phone (bootloader) via the Revolutionary method. Then reflash the firmware (last one). And finally, flash your favorite rom. This will solve your problem. Feel free to post additional questions.
Read those topics:
Guide for s-off, root, flash, ...
Solve wifi errors
i cant flash it via revolutionary.... my hboot is 1.27.0000
sorry, i mean unlock by revolutionary.
also, now that i check, my gps does not work correctly, so i am assuming this means i have the wrong radio flashed onto my device? any suggestions?
Maybe radio or kernel but if you have an HTC RUU (original rom) this won't happend. So it's most likely a wrong unlock bootloader error, if this means something. Have you tried to unlock the bootloader via htc-dev again? Maybe you should use the new way to s-off (unlock bootloader), the one called jaggerbear or something like that (have a look in the dev section).
Sent from my Sensation using xda premium
nah.... Juopunutbear completely voids ur warranty... dont really want to risk that
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?
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
after coming back to stock rom(by ruu) and relocked bootloader my touch screen something not working well frezee sometime
keyboard types wrong key sometimes
kindly provide me a solution
htc explorer
May I just ask why did you locked the phone like that, asking just from curiosity.
The only thing that I can suggest is to try with factory reset, after the ruu it shouldn't make issues (not 100% sure, but somewhere around high 90's)