Hi.
I have an old HTC s710 and like it. Problem is recently it acquired a mind of its own. It types symbols without any reason, when i lock it i cannot unlock it short of rebooting it, it keeps losing time. Keypad appears to be fine physically, all keys work, until it starts typing stuff on its own. I can lock and unlock it manually, but if i leave it locked for long i cant unlock it.
Initially it had WM6, updated to WM6.1 and later to WM6.5. It was working fine for a year on 6.1, i have upgraded it to 6.5 today to see if that would fix the problem - it hadn't. One new symptom on 6.5 is that it goes to dimmed screen and i cannot un-dim it by pressing any key, i have to lock it and unlock again to get a bright screen...
Any idea what it might be ?
Thanks
Hmm, very weird but my phone used to do the same kinda thing.
You could try to do a hard reset, but i guess as you flashed it with a new rom, i guess it won't help.
you should try another RADIO ROM!
this might be the problem
or you've a problem with your flexcable?
or is your motherboard damaged(by a drop)? mine is so some keys on quertz keyboard have malfunktion sometimes they work sometimes they wont.
you might have a damaged and sofor useless vox but may a simple rom change(radio) could heal
whats the newest/best radio nowadays ?
Haven't been following vox scene for about a year, since i had to learn to flash my phone.
What should i flash it to ?
current radio on my phone is 4.1.13.54_03.10.90.
Related
Bonjour
I upgraded to WM6 (pdaviet) 2 months ago (I guess..), and problems started to appear a few weeks ago. First it just was hard to boot sometimes, had to reboot several times to get it up and running, but when it could start everything was fine. Then since yesterday, it became harder. And today, couldn't start it at all. Tried several times, and everytime the screen went melted, corrupted, like if it couldn't stand an o/c, but it always runs at normal speeds. I guess it has something to do with the battery and the way WM6 handles it (or at least the implementation we have on our prophet).
I tried to hard-reset, I left it a long time on the format screen (before the actual HR) and it handled it for long enough, but the same thing started while setting up WM.... too bad !
While writing this message I tought I could try to downgrade, and I did using AKU3.3-Jester-b1.
I had no problem while the phone was in guest mode after the HR.
Everything went nice during first step upgrade, but on final reset it did the same thing, and now..... it cannot start at all !!!!
Someone has an idea ? I own a G4 and it has the following roms :
IPL 2.10, SPL 2.20, GSM 2.47 (or something like that)
It won't charge (but my batteries are full, I've got an external charger), it won't start from battery nor from power, even if the battery is removed.
Damn, at least I guess I can return it like that to orange, since it cannot start one can't see the modified rom...
If anyone has a suggestion, it is more than welcome ^^
Thanks !
Niko
huh !
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
lastnikita said:
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
Click to expand...
Click to collapse
Hey LastNikita,
I had the same problem ! The white scanlines thing just after re-updating a WM6 version (pdaviet), because I was tired of the constant reset issue.. suddenly, the update went wrong, and I stupidly followed the "recovery" process, which tells u to remove the battery... bang ! screen went corrupted !
Like you, I tought it was over... but I noticed that if you connect your phone and PC with USB, and keep pressed power (ON/OFF button on side) + camera after reseting (little hole on bottom - press during 5 sec!), the PC recognizes a USB device (not the usual phone drivers...) at this moment, I launched the Jester 3.3 (step1) update, in order to downgrade from the ugly WM6 pdaviet... My phone was not yet fixed (still with white scanlines), but at least, I could hear again the WM "start" sound, the scanlines would also "move" across the screen borders when I touched the screen, which made me imagine I was on the calibrating process... also, while connected to PC, after a while, ActiveSync would launch, asking for 1st time synch... this kept me confident as the phone (software) seemed to be reacting fine although HW prob...
I completely charged the phone again (till green light) then kept on reseting the phone (until I hear the WM sound) hoping the lines would finish scanning and come back with the normal .. and guess what, it did !!! Of course, PIGHEAD as I am, I wasn't totally happy it recovered with WM5, so i digged for a better rom, and I can tell you I'm very happy with the smart1 (wizard version) which works fine, but still has some minor bugs as Live Messenger not working... but runs fine (specialy when pressing the ON/OFF button !
PS: Make sure the ALWAYS completely switch off your phone (ON/OFF for 3 secs) before removing the battery... it did happen again... when I stupidly trusted the "recovery" process, again !
DUHHHH !!!!
PS: at least, now you ALL know !
Kokiri
Finally ok for warranty )))
Thanks for sharing mate
I finally managed to downgrade to my original Orange rom, and I'm in the process of putting the original Orange splash screens back (I made the nk.nbf but I can't find the right utility to upgrade... "Update utility cannot open the requested file").
BUT I still have that HW problem afterall.... so I guess it still has to go back to warranty right ? This isn't a big deal since Orange is VERY prompt (I guess I'll get it tomorrow or monday morning, the delivery guy brings a new one and goes back wiv my phone, quite nice !), and I have a button which is stucked (from the begining) anyway ^^
While I'm writing this my phone is docked and synced, and it seems fine.... but, I guess, as soon as I will reset it will start over again.... I'll keep you posted.
Anyway, I'm no longer desesperate and that's good news (for me ^^)
++
niko
yip
ok, everything's back to original.
Actually, it works well when docked, but it freezes/melted screen as soon as I tried to use it on battery, so that I'm quite sure it has something to do wiv WM6.... I'll post that on some crossbow threads this weekend if I have time enough (there are so many of them now !)....
But once more, if YOU read this, keep that in mind.
Hope you guys won't have that kind of failure while trying it.
++
niko
confused
I am having the same problem except the screen showing white scanlines everything else is working on the handset. Could it be a LCD Problem?
Me too...
I have the same issue (black/colored vertical lines and a white screen). I think it has to do with upgrading to WM6 or with overclocking with batteryStatus, not sure. This are the suspects in my opinion....
Now I downgraded to WM5 but the problem seems to persist, I disabled batteryStatus and will see if the situation improves... crossing fingers
Uhm ... possible Overclocked!
I have read 3 threads with same errors!
how much was your highes clock? do you use it for navigation? long time on highest clock or only for speed up?
i dont have a problem with scan lines but with my prophet i use the scaling option and go max to 234 i also set to 234 when using certain apps.
is this damaging to my prophet?
at the moment trying to upgrade to PDAViet 4.0.0.0.3 with a world of pain but thats another topic!
Hi all,
I read through a lot of threads and downloaded tons of ROMS for my TyTN II. Most of them were from dutty's or no thrills. Problem however is that everything seems to work, it is also very fast.
However after a while my (hardware) keyboard and also the buttons (e.g. sliding wheel and keypad on the front) does not respond anymore. When I click any of the hardware buttons the light goes on so it does react on the buttons, however it just doesn't do anything...
Did anyone else experience this issue? I will no try to switch back to the original HTC rom (6.0) since I have no choice but if anyone knows how to fix this?
P.S. I just noticed that all my buttons do not work, it is no hardware issue since It does work after a hard reset, might be caused by incompatible applications? (e.g. SPB phone or SPB theme)
Kind Regards,
Nico van der Linden
If a hard reset fixes your problem each time, then it sounds to me like a bad flash. I would try reflashing the ROM you are currently running. Make sure to hard reset immediately after the flash also.
ok thanks, I'll try to download the ROM flash again , and perform an hard reset directly after the flash. Hopefully this times the ROM update will go better.
Regards,
Nico...
Just my 0.02$:
I think this is related either to WM6.1 builds or to a hack/fix/setting that most custom ROMs use.
I flashed Dutty's Apr 01 ROM and i had this issue. Then i flashed Mobile Vista 1.3 and it happens again . So it's not present in just one ROM, or just in ROMs cooked by a certain chef.
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
EDIT: Oh, and i got flamed and ignored whan i reported this here: http://forum.xda-developers.com/showthread.php?t=385080
EDIT2: I have a feeling this will get a lot of attention soon, just like the time i noticed the Tytn II is underperforming, and the fact that's it's missing 3D HW support
RPG0 said:
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
Click to expand...
Click to collapse
The quickest way to get out of that situation is turn off the backlight and turn it back on again, aka power button...and your screen will work again.
Also I noticed that if I flash the radio again my screen taping problems go away.
Also sometimes flashing to the original shipped ROM and then flashing back to a WM6.1 ROM also works.
Well I do not have an problem with the touch screen, this always keeps working (although the device does get VERY slow sometimes) . 'Only' my hardware buttons do not work anymore (including the hardware keyboard). It is strange that it does work after a hard reset or an install of another ROM. However, also then it stops working after half a day or so.
It might occur as soon as I change the hardware button assignment but I am not sure about this yet.
However, if anyone knows a ROM where this does not occur (e.g. an original HTC WM6.0 ROM dutch or english) then please let me know which one. I just want a working Tytn II back and I do not care anymore which version .
Kind Regards,
Nico...
Ah by the way, when this problem occurs it does not go away anymore when I turn of the device. I also tried removing SIM, memory card and battery but after it is started again the problem remains. Only a hard reset solves it....
But I am a bit confused? Is there nobody else who get these issues???
yeah...
i can confirm all of your bug...
with Vega R8 italian ROM from UDK
Hello forum members,
would you please help me have the BT HTC S710 Original ROM? I have only seen the BT HTC S620, which when I tried to flash with to rebrand, blanked my HTC S710 screen. When I turn it on, only the two green lights come on either side of the phone ear piece.
It means that a hard reset is not visible on my screen, there is no tri-colour display either.
I have tried other ROMS, and get invalid id errors and error 270. I have tried Dr Gonzo and related ROMS.
It's now three days, no phone no pim, I am lost.
Thanks for your attention.
YOSEFE.
PS. You may PM me if convenient.
Hi YOSEFE,
I have the same problem
I tried the 620 rom and just have the 2 green LED's. I cannot get a bootloader screen and attempts to flash new roms get to 3% and then I get errors.
Did you ever sort this problem out?
Paul.
Have you unlocked ur USPL in ur phone?
You tried to flash a S620 ROM to a S710???? Look in the Wiki, there is a link to the official ROMs on the ftp...
frauhottelmann said:
You tried to flash a S620 ROM to a S710???? Look in the Wiki, there is a link to the official ROMs on the ftp...
Click to expand...
Click to collapse
Yes, I'm afraid I did, by mistake, flash 620 ROM to the 710 [feels rather stupid!]
Not happy with BT’s [mobile operator] own ROM and software that went on the phone, I successfully flashed Dr. Martin Gonzo’s Windows Mobile 6.1 v1.1 and have been using it for a couple of months but when BT launched their new phone software, I decided to try it but because it won’t work with WM 6.1, I needed to then revert back to BT’s old ROM and this was the only one available that I could find [feels rather stupid again].
The screen is completely black; only green LED's on each side of the earpiece shows any sign of life.
Connecting the phone via ActiveSync shows “HTC-S620 Connected” and I am able to browse the files on the phone but not having a display on the phone, I am limited to what I can do.
I have tried running RUU_Vox_HTC_WWE_1.34.405.1_4.1.13.54_03.10.90_Ship.exe but ActiveSync connection is lost and I hear the Windows hardware removed sound shortly after the progress bar is shown.
I’m at a loss as to what to try
Paul.
Shut it down, then hold down camera button and plug in the usb cable. The boot screen should appear and you should be able to flash the normal ROM!
I cannot get the boot screen, or any screen for that matter.
I have tried taking the battery out to make sure the phone is off. Reinserting that battery then holding the camera button down and then inserting the usb lead. The keypad lights up for a few seconds then goes out. ActiveSync then connects but the screen is still black
Paul.
[Edited: Sorry duplicate post]
Sorry for replying to my own post but a quick update...
I have managed to bring the phone back to life and reinstall Dr. Martin Gonzo’s Windows Mobile 6.1 v1.1 on it again.
This is partly assumption and not particularly accurate but the original poster (YOSEFE) might find this useful.
By installing the S620 rom on the S710, not only did I make the screen go blank, I think all the keys ended up remapped and mixed up, therefore any attempt to install Gonzo’s rom ultimately ended in failure because when the phone beeped and wanted a keypress to continue, pressing the left softkey for ‘OK’ or ‘Yes’ did not work because it had been remapped to do something else.
What worked for me is that when the phone beeped during the uspl_116_jockyw.bat install, I pressed the X or C key (I can’t remember the exact one now). One of these keys must have been the ‘OK’ or ‘Yes’ key after the S620 rom muddled things up. I only know this by trial and error over the period of today.
To my glee, the backlight lit up on the display and after a bit of tinkering, I’m back in action again
I won’t be installing a rom designed for another model again!
Paul.
Bat 'n' Ball,
sorry for not returning here to see your post. I will remember the possibility of pressing "X" or "C", should I make the same mistake as before, although like you, I should never do that ever again. However, technology being what it is, who knows?
In the end BT got me sorted out.
Thanks for sharing.
question
not all the keys on my htc s710's keyboard are working all the time. for instance the dot, the letter b and letter k do not always work. strangely enough, sometimes all the keys work for a while, and then for no apparent reason the same keys do not work anymore (always the same keys) i tried several roms, with all the problem exist. when i do a cold restart, and try the keys most of the times the will work for a while, but after a while they stop working. same if the power drops (battery drops below a certain percentage), the problem is more persistent and the keys fail more often than with a fully charged battery. i already checked the connection cable on the mainboard, that appears to be seated fine.
any idea's and suggestion (no warranty off course, since i opened it up myself)
Not working
Ive got same problem here.
Cap/Sft and fn isnt working in text message mode.
they work in home screen though..
Please help us out!!
thats why i dont open my phone ...
anyway... if u think u are good with hardware and breaking things apart an take them back together... u can try the htc vox service manual...
i dont recommend anything...
but here it is
http://www.maritime-billeder.dk/uploads/file/VOX_SM_A01 _GENERIC_.pdf
read before u do anything and remember if something dont work, stop, think.. DONT use violence
oh.... opening the phone works in the case some buttons dont work anywhere... otherwise its software.. maybe hard reset, reflashing?
Its definately not hardware.
Because when I Updated from orginall Vodafone Rom to WM 6.1 the keyboard started to decline.
So does someone has a solution for this?
I dont have much knowledge of this, but managed to update my HTC S710 to WM 6.1.
(sorry for my english)
Hi all,
I bought a second hand Raphael on eBay. The previous owner said he flashed WinMo 6.5 and a HardSPL. Something seems to have gone wrong somewhere, because WinMo starts up and shows the welcome screen and then the touchscreen alignment dialogue over and over. As soon as I touch all five points, the alignment process starts again.
I have already re-flashed WinMo 6.5 an 6.1 with the same results. I have also added a WELCOME.NOT file and tried a soft reset. The file just disappears after the reboot.
The boot loader says as version numbers:
R 1.14.25.05
R 52.63.25.34u
D 5.00.00.00
I'd be glad for any pointers. Maybe a pre-calibrated rom?
Also, I actually want to run Android on the little fellow. Could I just try to flash LightNHB and run Android from there?
Thanks for your help.
Regards,
Kevin
That's not the bootloader screen numbers, but I don't think that's the problem. It may just be a crappy rom on there. Getting to the alignment screen is a good sign that the device isn't bricked. I would say just flash another rom; use one of the android-starter roms if that's what you want on there.
Thanks for the answer, unfortunately it seems the touch screen is broken
I managed to install Android using LightNHB, worked a treat. Androids calibration screen seemed to take all five poinst, but the coordinates it printed out where all on the same y-coordinate. The touch screen doesn't work in Android after that (I mean, how could it ).
I'll have a look around to see if I can buy a new screen for cheap.