Model: One X (Endeavor)
CID: HTC__203
Branding: None
Region: FR
Language: EN
Firmware: 1.29.401.7
---
When using some applications (terminal emulator and connect bot so far), I notice the OSK comes up with the letters in uppercase and the shift key doesn't change the case for me. Has anyone else had this issue or know of a possible quick fix?
Additional note: this does not always seem to happen, but when it does, even closing and reopening the program does not fix this. This has not occurred in any other program.
Factory Reset.
TommUK said:
Factory Reset.
Click to expand...
Click to collapse
Is that the only solution? I'll do it if I have to, it's just I have everything configured the way I like it >.<.
try another keyboard see if same symptoms exist
Had this issues aswel. After 2/3 reboots it gone away.
xmoo said:
Had this issues aswel. After 2/3 reboots it gone away.
Click to expand...
Click to collapse
Sounds good, i'll try those and if all else fails, i'll reset to factory.
Related
OK I think I just did a stupid thing!
I thought that a Radio only upgrade didn't require a Hard Reset (i.e. to Factory defaults and losing all your local data / program installs).
So I went from 1.09 to 1.11, hit the 'reset' button on completion and the stupid thing did a hard reset!
So where did I go wrong - well I think it is because I did the radio upgrade as a standard upgrade just by running the normal update files with only the new radio ROM file present and no other ROM files.
What I didn't do was to enter the BootLoader manually first I left it all up to the RUU files to do the job :roll:
Is it this (not manually entering the bootloader first - like the Wiki tells you to - mind you it also tells you to hard reset) which caused the hard reset which was beyond my control :?:
I'm sure I've changed the Radio ROM only on my old BA without all this hassle - just can't remember what I did differently.
From what I remember, you are supposed to press the reset pin hole while pushing down on the ON/OFF button. This would cause it to soft reset according to the on-screen instructions, and it did on mine when I tried it. But of course, I also performed a backup to be on the safe side.
Really not my day today - Whilst reinstalling and going through reset cycles my Exec turned into a brick :shock:
Stuck at boot-screen with ROM versions showing
Hopefully the Wiki resolution to this one is going to work..
Ever wish you'd just left the thing alone
Whenever I've done a radio upgrade, I've simply pressed the reset button with the tip of the stylus - that's it.
I've done about 6 up/downgrades, I would guess, and not had any problems. I hope you get yours sorted out.
Cheers,
Steve.
StevePritchard said:
Whenever I've done a radio upgrade, I've simply pressed the reset button with the tip of the stylus - that's it.
Click to expand...
Click to collapse
At least I'm not going mad then - That's exactly what I did before this all went pear-shaped.
Did you upgrade whilst in the bootloader or just from WM5 running normally?
dpayea said:
Stuck at boot-screen with ROM versions showing
Hopefully the Wiki resolution to this one is going to work..
Click to expand...
Click to collapse
De-Bricked
dpayea said:
dpayea said:
Stuck at boot-screen with ROM versions showing
Hopefully the Wiki resolution to this one is going to work..
Click to expand...
Click to collapse
De-Bricked
Click to expand...
Click to collapse
Good to hear!
dpayea said:
StevePritchard said:
Whenever I've done a radio upgrade, I've simply pressed the reset button with the tip of the stylus - that's it.
Click to expand...
Click to collapse
At least I'm not going mad then - That's exactly what I did before this all went pear-shaped.
Did you upgrade whilst in the bootloader or just from WM5 running normally?
Click to expand...
Click to collapse
WM5 running normally - to be fair, it sometimes took a few attempts for the upgrade to "take", but once it was going, I've had no problems - glad to hear you manage to de-brick it.
Cheers,
Steve.
dpayea said:
dpayea said:
Stuck at boot-screen with ROM versions showing
Hopefully the Wiki resolution to this one is going to work..
Click to expand...
Click to collapse
De-Bricked
Click to expand...
Click to collapse
Good to hear!
hello all. i have a big problem if you can help me. i have installed windows 2006 and everything is ok (with each version) untill i take off the battery. after i put it back, i power on and the screen is white and remains that way. only thing that i can do is hard reset or another update. why is happening that?
ady_uaic said:
hello all. i have a big problem if you can help me. i have installed windows 2006 and everything is ok (with each version) untill i take off the battery. after i put it back, i power on and the screen is white and remains that way. only thing that i can do is hard reset or another update. why is happening that?
Click to expand...
Click to collapse
Which kind of hard-spl do you have?
the problem was solved. it was the fault of Igo, i think that it has a virus. i've deleted and put a safe and known version, and is working perfectly. The problem was that each time i've hard reset the device or reinstall windows, igo window appears and ask me if i want to install it. anyway, deleting that version of igo, and install another one was the solving matter. thank you all.
Today I had several reboots on my Desire. After the third I decided to do a hard reset.
Since rebooting the Android Market has been REALLY slow.
It will find apps and let me install them, however the screen doesn't change after the install - it keeps saying installing. The only way to remove the "installing" message is to reboot
I have tried several reboots, reflashed the stock T-Mobile UK ROM and I have formatted the SD card, but none of these have fixed it.
I get the same using WiFi or mobile internet (vodafone UK)
Anyone having the same issue, or got any ideas how to resolve it??
Cheers
Zippyioa
Delete please..
See below...
Try THIS!
If not then just wait as the Market on googles servers needs time to catch up with the diffrent build numbers changed, since a flash i belive
Mine took personally after everyflash at least a hour to start even working a bit.
EDIT: Maybe if it carries on being very slow, maybe something happened in the flash whilst in recovery, and has written some data to some bad sectors, causing this issue << only spectulation tho!
zippyioa said:
Since rebooting the Android Market has been REALLY slow.
It will find apps and let me install them, however the screen doesn't change after the install - it keeps saying installing. The only way to remove the "installing" message is to reboot
Click to expand...
Click to collapse
Thanks for the link, but I tried that already (after searching for this issue!)
It didn't resolve either issue for me (the slow market, or the installing issue) nor did other threads, hence me starting this one.
Any further help would be appreciated
Zippyioa
potter1984 said:
Delete please..
See below...
Click to expand...
Click to collapse
Please don't!
See above.....
zippyioa said:
Please don't!
See above.....
Click to expand...
Click to collapse
Lol, i ment delete my post
Then referred to my second post.
Soz for the confusion
Still having this issue.
I have tried the close market place and clear cache/data idea, but no joy
I have now re-formatted (after a factory reset and clearing storage in bootloader) but it still sticks on installing in market even though the app installs fine.
Please help!
Slow for me today as well, stock Desire.
Maybe give it a day?
Okay, its been a few days now and I am still having the never ending install and slow market issue.
Surely I cant be alone??
Hi all,
The Verge reported that other Android devices may have the same issue as the S3 did (Samsung has pushed a patch out).
Yesterday we reported on a vulnerability on Samsung phones that could allow a malicious website to wipe a user's device, but new details are coming to light that indicate the issue extends beyond Samsung's product line — and that the dialer in some versions of Android may by the cause. Dylan Reeve writes that he was able to replicate the same behavior on both a HTC One X running HTC Sense 4.0 and a Motorola Defy running a version of CyanogenMod. The Next Web has confirmed the issue also exists on the HTC Desire running Android 2.2.
The problem appears to be the Android dialer itself. Websites are able to link characters with a special prefix in order to pass digits to the dialer in a phone — the same functionality that allows you to initiate a phone call from a site, for example. However, the dialers in phones also support specialized strings of characters that can do anything from displaying a phone's IMEI code to wiping the device itself. In devices vulnerable to the attack, the dialer treats these special codes the same as any other phone number, allowing a website to initiate a reset without the user authorizing it to do so.
Click to expand...
Click to collapse
http://www.theverge.com/2012/9/26/3412432/samsung-touchwiz-remote-wipe-vulnerability-android-dialer
Based on the article above, there is a link to a page that you can load it on your browser and test it. Loading this page on your desktop/laptop won't help.
Load it on your mobile browser:
http://dylanreeve.com/phone.php
If your device is susceptible, the page triggers your phone dialer and displays your IMEI number.
On my One X, Sense 4.1 with Android 4.0.4, the device is still susceptible. Apparently, HTC needs to update the dialer software to fix it.
You can read more about it here as well as look up some makeshift solutions:
http://dylanreeve.posterous.com/remote-ussd-attack
Let's see how long HTC takes to push out this patch.
========================
These are some key responses for those lazy to scroll through the thread.
theliquid said:
Simple fix for remote exploit: https://play.google.com/store/apps/d....voss.notelurl
Article concerning exploit-fix: http://www.heise.de/security/meldung...s-1717765.html (Sorry, only in German - try to Google Translate it)
Another exploit-check website: http://heise.de/ussd
This fix works!
Click to expand...
Click to collapse
leppie and diamant-x informed that the code is available and can be triggered BUT it will require user permission first which reduces the threat tremendously.
The main problem is that samsung provided a built-in code to factory reset without notification, that is a silly programing thing.
HTC didn't, so although we can get USSD codes executed via browser, there's not a lot of problems about it as we won't have our phone erased or something like that.
Click to expand...
Click to collapse
I guess it is our job to bring the awareness to htc
Sent from my HTC One X using xda app-developers app
No problem on CM10. Opened the dialer but didn't show imei
Michealtbh said:
No problem on CM10. Opened the dialer but didn't show imei
Click to expand...
Click to collapse
I think Custom ROMs will be fine because its quite an easy bug to fix and Custom ROM makers respond very very quickly.
Stock (manufacturer based) ROMs could be another story.
Stock ROM is fine too.
I tested it with the factory format and erase codes last night and they did not work. Things like DIAG's you can still get up.
leppie said:
Stock ROM is fine too.
I tested it with the factory format and erase codes last night and they did not work. Things like DIAG's you can still get up.
Click to expand...
Click to collapse
Have you tried the link posted on the 1st post of this thread? It tests whether your device is exposed to running codes through the phone's dialer.
Your HTC device was not affected by the reset code that was posted yesterday because it's a Samsung specific code, however, if your device isn't patched for this security breach it can run a reset code that works on HTC devices as well.
junialum said:
Load it on your mobile browser:
http://dylanreeve.com/phone.php
If your device is susceptible, the page triggers your phone dialer and displays your IMEI number.
On my One X, Sense 4.1 with Android 4.0.4, the device is still susceptible. Apparently, HTC needs to update the dialer software to fix it.
Click to expand...
Click to collapse
I'm on stock ROM as mentioned in the first thread and updated to the latest firmware (2.17).
I also did perform a hard rest 3 days ago (to resolve battery issues).
The One X's latest released stock firmware is susceptible.
junialum said:
I'm on stock ROM as mentioned in the first thread and updated to the latest firmware (2.17).
I also did perform a hard rest 3 days ago (to resolve battery issues).
The One X's latest released stock firmware is susceptible.
Click to expand...
Click to collapse
The reason that no-one is too worried about the HTC One X is because apparently it does not have ANY codes that force a factory reset by dialing a number - hence the worst an attacker can do is make your IMEI number pop up. Personally I cannot understand why anyone ever thought it would be a good idea to allow you to do a factory format by typing a number into the dialer that you didn't have to press the call button to execute in any case - don't worry - no-one will be tricking you into a factory format of the HTC One X anytime soon.....
wkd2639 said:
The reason that no-one is too worried about the HTC One X is because apparently it does not have ANY codes that force a factory reset by dialing a number - hence the worst an attacker can do is make your IMEI number pop up. Personally I cannot understand why anyone ever thought it would be a good idea to allow you to do a factory format by typing a number into the dialer that you didn't have to press the call button to execute in any case - don't worry - no-one will be tricking you into a factory format of the HTC One X anytime soon.....
Click to expand...
Click to collapse
Are you sure the reset code posted in this thread does not work?
http://forum.xda-developers.com/showthread.php?t=1683634
I'll quote the codes that wineds has kindly linked:
theliquid said:
HARMFUL CODES
BE CAREFUL WITH THEM!
*#*#7780#*#* = factory reset !! BE CAREFUL!
##4772579# = reset GPS - working?
*2767*3855# = factory format !! BE CAREFUL!
*#*#197328640#*#* = service mode? - after two tests seems to be NOT WORKING
Click to expand...
Click to collapse
I am on slim bean 2.5.0 and its susceptible to the bug..
Sent from my HTC One X using Tapatalk 2
I posted it in the Secret codes thread. The main problem is that samsung provided a built-in code to factory reset without notification, that is a silly programing thing.
HTC didn't, so although we can get USSD codes executed via browser, there's not a lot of problems about it as we won't have our phone erased or something like that.
I tested the codes and recorded it, and nothing happened:
http://forum.xda-developers.com/showthread.php?p=32082049#post32082049
Jaan of viperx solved it..
http://forum.xda-developers.com/showthread.php?t=1907797
Sent from my HTC One X using Tapatalk 2
diamant-x said:
I posted it in the Secret codes thread. The main problem is that samsung provided a built-in code to factory reset without notification, that is a silly programing thing.
HTC didn't, so although we can get USSD codes executed via browser, there's not a lot of problems about it as we won't have our phone erased or something like that.
I tested the codes and recorded it, and nothing happened:
http://forum.xda-developers.com/showthread.php?p=32082049#post32082049
Click to expand...
Click to collapse
And this is what I saw too. Not sure why they still think anything harmful can be done.
Simple fix for remote exploit: https://play.google.com/store/apps/details?id=com.voss.notelurl
Article concerning exploit-fix: http://www.heise.de/security/meldung/Schutz-vor-Fernloeschung-von-Samsung-Smartphones-1717765.html (Sorry, only in German - try to Google Translate it)
Another exploit-check website: http://heise.de/ussd
This fix works!
update:
English Version: http://www.h-online.com/security/ne...martphones-against-remote-wiping-1718531.html
Thanks theliquid. I'll append that to the OP.
Hello guys,
I searched for this issue on the forum but it seems that nobody encountered anything like this before.
To begin, I would like to mention that I am running the latest CyanogenMod 11 nightly on an HTC One X (Tegra version).
Since somewhere right after the latest M release, I've been having a couple of issues with the phone:
#1: From time to time, I get a "Lockscreen" isn't responding dialog and it asks whether I want to "Wait" or "Close". Well, if I click on "Wait" the phone becomes unresponsive, as if something was running in the background so hard that it would eat up all the ram and would choke the CPU;
If I click on close, it's a hit or miss situation: sometimes it restarts the lockscreen and takes me back to it, even though I previously unlocked the device and sometimes the phone becomes unresponsive as before.
#2: Besides what I mentioned above, the phone sometimes becomes unresponsive without warning and every time this happens, it always looks and feels as if something is chocking the ram and CPU.
Have any of you guys encountered something like this before and if yes, what can I do to fix it?
If not, is there a way in Android, to pull up a log similar to the Windows Task Manager, that would tell me exactly what was running in the background at a given time and how much memory/CPU cycles it was actually using?
Thank you in advance.
Try your stock rom for a while.
Mr Hofs said:
Try your stock rom for a while.
Click to expand...
Click to collapse
Thank you for your reply however, I haven't used sense roms in a while now, plus, it's a downgrade from KitKat, which is why I am not that fond of this option.
On a different note, I just installed the latest nightly "clean", namely with a full factory reset from recovery, flashed boot.img in fastboot and installed the latest GApps from PA.
I don't get the "Lockscreen is not responding" dialog anymore, but from time to time, the lockscreen still closes and now it either resets on its own, or it forces the OS to reset, after which com.android.systemui starts force closing indefinitely and the phone afterwards requires a hard reset.
Has anyone else encountered something similar? Any help?
I'm saying to use the stock rom for a while just to rule out hardware issues !
Mr Hofs said:
I'm saying to use the stock rom for a while just to rule out hardware issues !
Click to expand...
Click to collapse
Cool, will try that. Thanks.
What kind of hardware issues do you think could cause an issue like this?
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Mr Hofs said:
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Click to expand...
Click to collapse
Fair enough! Thank you!