Hi everyone,
I have a TP2 Sprint & had to do a hard reset due to SENSE start up corruption (working fine with SENSE disable) but my screen alignment got stuck after reset so I did a bypass with Code Factory - Remote Screen Alignment with skip via PC sync. I tried to use a WIZA200.dat file with 1922,1957 3330,639 3317,3276 600,3230 609,677 or with 174,928,858,932,499,554,160,194,840,195 to calibrate from installing within C:/Program Files/Code Factory/Remote Screen Alignment but it still did not work ( I think by using the software & hitting SKIP option does not help installing the .dat file; the other 2 options on the software are to retrieve info & to run an alignment). The alignment seems to be upside down on screen.
Software option:
-Is there a alignment calibration file on the device that I can replace with? If there is, could someone please upload the Sprint TP2 file & let me know where to install?
Hardware option:
If any without replacing part like loose cable,.. I did have to
Thanks for your help!
Ethan
HTC TP2 Sprint
Hard reset to factory default
Why can't you just hard reset it again and actually go though the calibration process?
There used to be a way to force WinMo to calibrate as well, I can't remember what they key combo was right now...
arrrghhh said:
Why can't you just hard reset it again and actually go though the calibration process?
There used to be a way to force WinMo to calibrate as well, I can't remember what they key combo was right now...
Click to expand...
Click to collapse
I have reset many times. The calibration process is the problem (hardware; but it works fine before the reset due to SENSE software problem). It would keep re-calibrate in cycle. Thanks.
chutraiheo said:
I have reset many times. The calibration process is the problem (hardware; but it works fine before the reset due to SENSE software problem). It would keep re-calibrate in cycle. Thanks.
Click to expand...
Click to collapse
Oh, you have a hardware issue? Sorry... I'm not sure if I can help you then. Good luck.
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.
after phone working perfectly fine for a few weeks. i am not receiving constant signal. i am using radio 4.49.25.17. idk what can possibly be wrong any ideas?
i installed the ATT stock rom and left it for about 2 days and it started working again! idk if that fixed the issue but thats what i did.
is your problem anything similar to this? If so, I have been looking for a solution, but got no ideas so far =)
Edit: Oh yeah, forgot the link =)) http://forum.xda-developers.com/showthread.php?t=616426
Similar to what? I think you might have forgot to paste a link or somthing.
Any rate, if you have not loaded any new software to the phone I would sugguest the first thing you do is a hard reset. If that does not help you out then I would reflash the radio. This is all software and it can become corrupt for various reasons. It doesnt happen much but it does happen. All you have to do is read around this site to find out how many times a "Gremlin" has been removed with a hard reset.
how to perform a hard reset?
fyn3zt said:
how to perform a hard reset?
Click to expand...
Click to collapse
With the phone on:
Settings>System>Clear Storage
You know, this wipes out everything -- data and applications -- on your device, everything that's not part of the ROM (OS or Radio)
Can someone help me with a little problem ... Does anyone know if you can reset the timer on a HTC Touch Diamond ?
I mean if you can reset the calls receive minute and calls made minute ?
Thanks !
You can try to mess with HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\cumlativecalltimers\line_0 keys, but i'm not sure it will works.
Those values are probably stored into a flash proof memory of the phone (kinda CMOS).
bye.
Maybe no! that's because when you flash a rom the counters remain. Modifying the registry may not be the solution! try flashing a rom and check the counters from the 'Device Info' settings panel. I think it's, sort of, stored as 'hardcoded'!
kimo_ig said:
Maybe no! that's because when you flash a rom the counters remain. Modifying the registry may not be the solution! try flashing a rom and check the counters from the 'Device Info' settings panel. I think it's, sort of, stored as 'hardcoded'!
Click to expand...
Click to collapse
is not a solution if i flash a new rom, ( a use rom 6.5 on my touch diamond ).
a 3 solution, someone knows ?
Halvarez said:
You can try to mess with HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\cumlativecalltimers\line_0 keys, but i'm not sure it will works.
Those values are probably stored into a flash proof memory of the phone (kinda CMOS).
bye.
Click to expand...
Click to collapse
I think not destroy the phone if exchange the data
Its hardware based to stop people like you ripping other people off by faking that your phone is new and unused
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.