Related
I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.
OK, let me start by saying I am NOT getting the bootloader, I am NOT getting stuck on a startup screen, and I am NOT new to loading HTC ROMS (but I am new to the titan - former owner of Hermes). With that out of the way....
I bricked my Titan - It won't startup at all. Plugging it into the USB port generates a red LED and nothing on the screen. The only USB activitey seen on the computer is the HTC USB modem (no other communciation appears to be possible - no activesycn, no response to ROM updates etc.
This is the order of the bricking
1. Started with Default Verizon install (less than 4 days old)
2 unlocked with olipro 1.20
3 attempted install of Sprint 3.35 update to get radio (failed and rebooted device at 11%)
4. attempted intall of radio 3.27 (sucessful)
5. installed NexVision 3.35 cooked rom
6. ran into some stability with the rom (phone remained "Unactivated") and reverted back to ruu_signed_verizon stock ROM
7. Booted OK (phoen remained "unactivated"
8. reattempted install of sprint 3.35 (thinking rom instability was due to radio version) device rebooted itself at 11% and failed.
9. installed olipro 2.4 thinking it might circumvent the 11% reboot issue on Sprint ROM.(appeared sucessfull) phone never came back after that.
Now I'm dead in the water... Pulled the battery, Tried a hard reset (2 softkeys under screen/press soft reset) - no change in the device.
are there any secrets to unbricking a Titan?
Starting with the default Verizon ROM, updating to olipro 1.20
Hold off for a little bit, at the moment there is no unbrick, but ImCoKeMaN and jocky are working on this. Your phone now is booting into Qualcomm download mode and it is recoverable. It's just a matter of a patched loader to get a new spl on it...
thank (fingers crossed)... even tried the relocker by ImCoKeMan and it's not detecing the device either...
Time to be patient and wait for CoKeMan to come to the rescue.
just to make sure...
when you tried a hard reset... sometimes people dont know to hold the soft keys for a couple seconds (this is my experience anyway)
jsut for kicks try this again... press and hold the 2 soft keys, press reset button, keep soft keys held down, release reset button, wait a couple seconds then release the soft keys.
Hmmm I remember someone else with a similar problem not too long ago. He thought he had bricked the phone too and was getting the same red led when he plugged it in, but nothing else. His problem was that he had a defective battery. If you could get your hands on a spare battery I'd say try that...I'm not 100% sure it's the battery, and if it's not then I hope cokeman comes through for you...but if you can check that out, I definitely would.
gcincotta said:
Hmmm I remember someone else with a similar problem not too long ago. He thought he had bricked the phone too and was getting the same red led when he plugged it in, but nothing else. His problem was that he had a defective battery. If you could get your hands on a spare battery I'd say try that...I'm not 100% sure it's the battery, and if it's not then I hope cokeman comes through for you...but if you can check that out, I definitely would.
Click to expand...
Click to collapse
Was just about to post the same thing, red LED is definately an indicator of a battery issue, could be defective or just totally dead. If you unplug the battery and reinsert it and then plug in the usb charger without turning it on do you get a green LED? If so I would say battery is 100% discharged and wait for it to charge (I have had this happen). Otherwise if it is still red after that I would say replace the battery (I had this happen on my first titan, it was doa due to defective battery).
jjlwork said:
Was just about to post the same thing, red LED is definately an indicator of a battery issue, could be defective or just totally dead. If you unplug the battery and reinsert it and then plug in the usb charger without turning it on do you get a green LED? If so I would say battery is 100% discharged and wait for it to charge (I have had this happen). Otherwise if it is still red after that I would say replace the battery (I had this happen on my first titan, it was doa due to defective battery).
Click to expand...
Click to collapse
Exactly, all the roms downloaded from HTC recommend having at least a 50% charged battery.
Yup, battery was at 99% before the upgrades. with or without the battery in it reacts the same, with or without the USB in it reacts the same.
I left it plugged in all night, no change.
Solved (but not really)
Since the phone was brand new, Verizon techs took it back as a "faulty phone"... thankfully the Red LED to them means "bad battery" too and when they replaced the battery and it didn't fix itself they exchanged the phone.
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
wow, i didn't (i did-but not reallly) know that it was really really possible to brick your phone, i thought there would more or less always b e a way out. pretty scary!
Shadowmite said:
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
Click to expand...
Click to collapse
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
Click to expand...
Click to collapse
Ok well then I guess you could call me a naysayer then. And I assure you I am no dummy myself, in fact, I'm a Computer Engineer and work with embedded systems alllll day long. I don't doubt your knowledge about the bootloader and the SPL, but before you doubt MY knowledge explain this one to me. Stock battery, no bootloader, no nothing...just red LED. Replaced battery and all of a sudden phone boots...both normally and when forced into the bootloader.
I have the exact same problem. I don't remember exactly how it happened, but was similar scenario to previous posts. I believe I was trying to get the 3.35 radio installed for use with dcd's 3.0.1 kitchen, although I can't be positive.
QPST shows that it is seeing a Qualcomm device in download mode. Here is the exact model# it displays:
Q/QCP-XXX (Download)
Hope this info is useful to those that don't have a titan stuck in this mode.
Yep, that is a brick currently, but a method to fix it is being attempted.
Basically the phone has a dual core cpu with 1 core running the spl, and wince; and the other runs the oemsbl, qcsbl, and amss (the radio). Your spl is missing so the operating system core is doing nothing. However the phone side is still up and running. (this is mostly theory)
So we need to have a patched bootstrap to send in download mode (notice qpst software download actually sends over a bootstrap 7500.hex file found in your qpst bin directory) which will load the spl back into the correct areas of memory. I don't believe we can jump to it because we are on the wrong core.
Do you know which address range the SPL sits in memory?
JTAG ?????
Shadowmite said:
Yep, that is a brick currently, but a method to fix it is being attempted.
Basically the phone has a dual core cpu with 1 core running the spl, and wince; and the other runs the oemsbl, qcsbl, and amss (the radio). Your spl is missing so the operating system core is doing nothing. However the phone side is still up and running. (this is mostly theory)
So we need to have a patched bootstrap to send in download mode (notice qpst software download actually sends over a bootstrap 7500.hex file found in your qpst bin directory) which will load the spl back into the correct areas of memory. I don't believe we can jump to it because we are on the wrong core.
Click to expand...
Click to collapse
Hey Shadow, I think you are correct, and also possibly do you think that JTAGing it would work ? Grad the image from a good one and load it into a dead one. I do not yet have one to take apart yet to try, but if i get a bad one to take apart I might just get it.
It would be great to see this issue resolved as this same problem happened to me last nite and the "friendly" folks at Bell Mobility took one look at the phone and told me it was water damage. I've had the 6800 for about 20 days and it has not been close to water. Anyways, that's besides the point. I look forward to seeing some kind of resolution to the matter....thanks!
Do you see same in QPST ?
Escobar600 said:
It would be great to see this issue resolved as this same problem happened to me last nite and the "friendly" folks at Bell Mobility took one look at the phone and told me it was water damage. I've had the 6800 for about 20 days and it has not been close to water. Anyways, that's besides the point. I look forward to seeing some kind of resolution to the matter....thanks!
Click to expand...
Click to collapse
Do you see this same thing they report with the QPST also ??? Man I would not break mine to fix the problem, but would love to have one to poke at too.
Yes I am having the same problem phone basically dead....
Shadow may fix it, but,,,,
Escobar600 said:
Yes I am having the same problem phone basically dead....
Click to expand...
Click to collapse
I am not going to take mine apart to look for it, but i am sure there is a JTAG port inside these as there is every other I have seen.
Have HardSPL installed on phone. Got phone on eBay - has very few hours. Came with a Rom that displayed TEST ONLY which was WM5. GSM radio worked, Bluetooth worked and Wifi worked. Tried installing shipped HTC WM6 Rom - did it through ActiveSync - should have used MSD card. - Rom installed though everything was ok but didn't install a SIM card to test phone - used it as PDA and WIFI for a week no freezes. Now this morning wanted to switch phones over and inserted SIM - saw NO GSM on boot - never really noticed it before.
Checked in ABOUT section to see if a radio was loaded - comes up blank. Read some things about NO GSM errors - got a little nervous - so I thought I'd reflash entire ROM tonight with SD.
Followed directions and get into update process and it seems to freeze at GSM with progress bar at about 15% - for about 30 minutes.
Removed battery and it boots to TRICOLOR. (I freeked out at this point)
Put a HardSPLv7 on SD card and did the above - update was successful
Phone boots up to OS still with no GSM
Tried the update process again with the same ROM - still has problems and never gets past the same point as before. Will try another ROM but I'm a little doubtful. If I can recover it back again will try just upgrading radio to see if it makes a difference.
ANY SUGGESTIONS or is the hardware fried?
Thanks.
OK, think it may be back and I was able to reflash using a wm6 stock HTC ROM. Think either my original flash of the same ROM was bad - downloaded a new file and flashed with the SD - originally did it via ActiveSync.
To get it to work I did a couple of hardspl reflashes and got into the OS. DID a couple of hard resets and magically GSM appeared. Turned phone off and then NO GSM appeared again. Did the hard reset again - came back. Not taking anything for granted put in a SD card and reflashed. Held my breath and for some reason it did a complete flash and never really hung up for more than a minute or two. Soft reset - GSM was there. Turned phone off and on a few times and its still there. Phone now finds the GSM radio much faster than before. Can make and receive calls (does wake out of sleep) - signal strength is same on my other Cingular 2125. Will try out tomorrow and see how it goes. Either the reflash does it or something is loose in the hardware but if it works a few hours tonight it should be good.
Will be a little hesitant to reflash after this but will see after a stress test.
Hold both softkeys and hold the power button
You can also hold both softkeys and put the stylus into the reset hole. Tell me if that works.
Initially no. When I attempted to flash the HTC Factory Rom it froze. Prior to that I did a couple of hard resets using the two softkeys and reset pin. With the resets couldn't get the GSM radio to turn on. Tried the ROM flash but it froze (about 1/10 of the way) - so I basically OS bricked it by removing the battery when it was at this stage. Got to the bootloader screen. Tried to flash OS again with SD card - still froze. SO I thought reflash HardSPL and the OS magically appeared and did the steps above.
After a couple of hours - call made, turned off and restarted device no problems still have GSM radio. Can receive a call when in standby. May try to do another hard reset and see if it still works after a day or so of testing phone but I want to try it for a few days by turning it on and off and making and receiving calls. If I can do another hard reset and everything works I think it was just a bad initial flash through ActiveSync. May get bold and flash another ROM as a test.
Since the phone worked with the TEST OS when I got it I think the only factor is the WM6 flash that I did. More than likely the hardware is OK but only time will tell.
I don't believe you will recover your radio rom now as you interrupted the flash. It generally takes 30 MINUTES to flash a complete rom. You stopped it during the radio rom flash, BIG MISTAKE....
If you can find the SHIPPED STOCK ROM or the original radio rom then you might have a small chance at recovery, we're talking about you winning the lottery 10 times in a row chance...
If you try to flash anything but the original radio rom then you can kiss the phone functionality goodbye....
Good luck finding the right roms...
Cheers...
Its not bricked. In my post said I did a full recovery and its working with the stock HTC WM6 ROM with the HTC radio. I can receive and make calls. Able to ActiveSync with the PC and have hard reset a few times just to make sure all is well. I believe there is still a hardware problem - either a loose connection inside or something else is going on but I think its definately hardware. When the stylus is out of the holder EVERYTHING works fine - have a signal - can sync - can charge it - no issues. If I put the stylus in part way no problem - push it in all the way during a call it will still say connected yet will hear nothing and can't disconnect. Pressing end has no effect yet the phone will still function - just the in call symbol stays and the green led still flashes.
Turn it fully off and back on with stylus out - shows GSM radio code and phone will now work.
Have to check the service manual to see if the stylus holder when the stylus is inserted pushes on anything vital. Can't imagine thats it. But so far with the stylus out everything is ok. Will attempt to use it tomorrow see if thats it.
Know it sounds stupid but thats what I'm observing so far. Its late here see what happens tomorrow
Thing is running and can use the phone (no static, three bars) but last night had a few no GSM messages during a cold boot. Ran it all night and it seems to be working - booted a couple of times, charged it, sync'd it and actually put the stylus in (don't know if thats the problem) and still working. May be a loose connection that is currently ok but who knows when it will stop working. Other possibility is heat or a failing radio. Could also be battery but thats doubtful. Could have messed up the stack during the initial flash so I'll see over the next few days. This one is starting to drive me a little crazy because it works then for no reason it will stop then resume after a hard reset or reset. Could also just be the version of the ROM I'm using but it came from the repository on XDA-Developers. Just rebooted it when I was typing this and it still finds GSM radio.
Tried it for a day and I think the radio is fried. Started out finding GSM then when driving around with my Bluetooth heard a bleep which indicates loss of signal - saw it hunting then it finds the signal. During a call for about 3 minutes just drops call and on the screen the dialer won't let you disconnect the call.
Rebooted got the NO GSM message - eventually found it - briefly then NO GSM again.
Tonight opened it up and reseated and cleaned motherboard contacts including radio. After hard reset got GSM again - briefly. Then no GSM
Tried upgrading and downgrading radio via SD card - no go would only hang up Tried complete with OS - same thing. Tried through ActiveSync method SSPL and got same.
So I think the phone is pretty much not really a phone - can still boot into OS. May try some more but I think its definately a motherboard issue. Shouldn't be that hard to flash and the GSM should at least be stable.
When I bought it on eBay and first turned it on saw a TEST ONLY message on boot with a WM5 Rom. The seller was a little vague just said it freezes sometimes. Got it cheaply thankfully so I'll keep hunting around for another unless someone has a suggestion?
The Radio seems to be the touchiest part of the Hermes. When it fails theres nothing that seems to be able to fix it. Look for another cheap Hermes. At the very least you will have spare parts.
how weird is this I have just gone through just the same problem and took a day to sort it out . ok here is what I did in the end . now what you need is any official rom pref wm5 . I can send you a link if needed to the one I used ... now try flash it from the pc it will stop at 12 percent ....... now take battery out and boot in bootloader mode .... now flash any rom that's wm6 etc .... devise will restart .... now take battery out and re boot it may take two or three boots to get it working prop without the no gsm error but trust me it will boot . when its booted up flash the original wm5 shipped rom run through the rom sequence and when its waiting to flash saying zero percent manualy put your phone in bootloader and wait 30 odd min tadaaaaa phone is now perfect ... now flash any rom you like as the radio is fixed . its something to do with the 12 percent bit it hangs on .??!!! sorry its long and complicated but I have my hermes back to life through doing it ................... let me know how you get on bud. if needed 07832999919 uk . so its 0447832999919 oh I have hard spl 1.40 spl 1.1 or something lol can't remember . anyway good luck
Ok, think I initially really messed up my flash and the WM6 which was the official HTC version may have been corrupted but showed full flash. When I tried again I would also get the 12% even with a SD flash. So I tried flashing just a RADIO ROM which did complete. The NO GSM message still would pop up maybe 50% and not necessarily everytime.
When to MTTY.EXE and did a bad block check - no problems
In MTTY did a FORMAT/CLEAR.
Left everything alone and again reflashed just the RADIO - things seemed to be better - less NO GSM.
Tonight - just before you posted I successfully did a complete reflash with the HTC WM6 rom with Radio 1.48. Very surprised it worked this time - no hangups except during the GSM part which only stopped a minute or two.
Complete reflash in about 10-12 minutes with the SD card method.
SO far things are working - tried a reboot a few times and now radio is found every try. Will try for a few hours and try again tomorrow.
What I did have is a white screen/with image once - it was cleared by just pressing briefly the power button. So it may be heat related - don't know.
Keep me posted in this thread whats going on and I'll do the same.
What ROM WM5 did you flash to get yours to work?
Spoke too soon! Put in a sim card - powered up and it worked. Tried making test call and it worked. Tried again and it showed dialer and dialing and never connected. Could not use the dialer to hang up. Also showed drop in network. Tried turning phone radio off in dialer and back on - showed !X. With the phone off hook image at the top bar. Tried again - same thing. Expected to see no GSM when power cycled and it did show NO GSM.
Right now its working even after a few power cycles but honestly I think the successful flashes may be due to the GSM radio being found. If it doesn't find the radio and you attempt to flash thats why it hangs. If you phone works for a few days or day I'd be very surprised. The real test is to try it when moving from tower location to tower location. Thats where I noticed the radio was acting up. With a bluetooth headset it will beep indicating a drop in carrier. When its doing this the radio isn't working properly and can't lock on to a signal
If your phone does work PLEASE post what you did and what files were flashed.
For my phone I think its heat related. Possibly the heat from the circuitry is opening up or stressing out a component causing it to fail. I really think my motherboard is faulty and reading on the HERMES this isn't that uncommon. Being that the phone has so little hours I think it must have been a return or factory reject.
More than likely I'll have to purchase another phone needing a screen or one thats in poor shape to salvage the motherboard and attempt to put it in my case since the housing and screen are pristine with little to no use. I've been told that any 8525 motherboard will work but I doubt it since the Dpad is different and I have a front video camera.
No, ANY Hermes mainboard will work... Hermes are identical internally, even the 8525 is able to use the front camera, it just isn't included in that model.
Cheers...
Thanks, makes my life easier!
ok mate i used htc orig rom by orange uk google the words,,,, orange spv m3100 update ummm ok hang on il grab the link for you ...
http://www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_1007.exe then flash hard spl then update your rom to whatever you like ,,, hope this helps buddy
Might try it tonight but I really think I need a new mainboard. I am able to flash only when it finds the GSM and I think any hangups are due to the GSM radio circuity failing or some strange power flux on the motherboard. I am having strange multiple freezes/slowdowns as well as NO GSM errors. Tried a WM5 and WM6 specific for my HERM200 and no change. When it works it will work and make and receive calls but after a while without a load but under load - multiple calls, running excel or other things the radio will drop or it will attempt a call, not connect and will not let me hang up. No software update will fix this issue - it has to be hardware.
If I have successfully done base HTC ROM flashes - complete with radio phone should theoretically work. I have to face reality with this one which although looks pristine is a lemon and have to buy a working beat up 8525 and try the motherboard as long as the seller assures that the phone can make and receive calls without problems.
Also have other issues with screen fadeout which I know is tied to the dPad controller - but I can live with that for a while and I have a source for a part replacement and can try a quick fix to verify its just the dPad.
You got lucky so far - but if you try to use the phone all day running multiple programs or CPU intensive tasks your radio still may fail. You could also try upgrading the ROM again to something that is MFG and see if it takes.
It is possible to flash the OS without flashing the radio, It will be a cooked rom but they're better in most respects than a stock rom. Faster, leaner with all the bloatware removed.
No software change is going to fix this. Its not a software bug its a flaw in the hardware. Can't flash a radio Rom - thats a chip problem. Its basically a low level format and write to eprom. Thats pretty basic. Also making and receiving calls is also pretty basic. The dialer has been around for a while and is pretty stable.
Hi,
as already written in one of the WM6.5 threads I have some serious problems with my Hermes and it's not getting better.
I have tried to search a bit but I couldn't find the right answer to my problem so hopefully someone can help me.
I will try to write down as many details as I remember regarding the problem!
- Hermes was running fine WM6.1 till some days ago until GSM began to get crazy (not logged into network properly, device hang up etc)
Can't remember which ROM I installed before but GSM was 1.47.00.00
- Today morning I switched to Tai's Golden Globe V14.
Before I put the AT&T "fresh" ROM onto my device to make sure everything will run smoothly
After flashing to GG V14 I did a HW-reset and synched my Outlook stuff - everything looked fine so far
- Later on I tried to make some phone calls but the device stuck and did not react
I did a SW reset and from now on the journey began - the device did start sometimes till a blank startup screen and sometimes it just hang up while booting
I recognized it behaved differently e.g. if AC was connected it did not boot up till Windows but also HW reset did not solve the problem
- Back to the PC I tried to flash my device with different OS and Radio ROMs but without success
Finally I found the Vodafone DE ROM and it seemed to work fine again but just for one phone call. I tried to switch on my device approx. 5min after the call but it didn't work - I only saw the green indicator (GSM) but there was only the possibilty to do a SW reset
From now on the device got crazy again and if I try to make a phone call the device tells me a kind of error "Cannot make a phone call" or something like that or the antenna indicator disappears or the antenna shows an exclamation mark
Additionally maybe some more information:
- Herm100 device (originally O² Trion)
- Oli HardSPL 2.10 (did it a while a go)
- GSM often showed an exclamation mark and sometimes good reception but phone calls couldn't be done (sometimes yes, sometimes no, totally crazy)
I really appreciate your answers and if I forgot something to say don't hesitate to ask me.
Thanks
Sounds like the radio is fried or is dying. Have the same problem on my HERM200 (TYTN). Bought the phone used and it froze often. Never really installed a SIM card when I got it. Installed WM6 and I had trouble with the upgrade - got stuck a few times - lucky I had HARDSPL installed. When the radio appears it initially would only work a few minutes at a time - running applications and time seem to get the same errors you experienced. Took the phone apart and cleaned it with electronics cleaner. Left on desk on in standby for a week - checked it occasionally and still showed active radio. Rebooted a few times still ok. Took the phone out of the house for two days still worked. Battery drained down during period. Now have no GSM errors and I was only able to get it to get a radio 1 or 2 times. Reboots and hard resets do not improve. Reflashes won't improve situation because it can't find the radio or the chipset is fried and it can't flash.
Hi and thank you for your answer!
Sounds like bad news and I sadly can confirm my device is more or less nearly unusable!
Yesterday I was not able to make a phone call and even flashing AT&T ROM did not bring any improvements even my SIM was taken out of the device. Seems like the radio influences the whole device even it's inactive. I will try some other radio ROMs... it can't be worse
Sorry guys..I think this is my first post here..I tried to make I resarch on my prob but I haven't find nothing similar (correct me if I am wrong..)
By the way I was using Dutty crem de la crem for a month with no prob after that the following issue came up:
Once my phone is on if I keep it pressed the power off button the page with power,lock screen or terminate data options show up but at this point the touch screen is freeze doesn't work...only thing I can do is repressed the power button, switch off the screen and re and press for example the "answering" button and I can unlock the phone (in this case the touch screen is operable)
Same thing if is the phone is in locked and I press the power off button I can not operate the touch screen (and unlock the phone) and again...only thing I can do is repressed the power button, switch off the screen and re and press for example the "answering" button and I can unlock the phone (in this case the touch screen is operable).
I tried the following:
-change the rom to last energy and dutty v11,change couple of time the radio version, format the memory card,operate the phone without sim card and memory card but no change.
Last I installed the original rom from HTC...and still the problem persist...I start to think is something related to the hardware..could be???
Any idea?
Other question why after I installed the original rom I can still see the hspl 2.08 if I switch on the phone keeping the volume down?
Thx guy!
lane2m said:
...I start to think is something related to the hardware..could be???
Any idea?
Other question why after I installed the original rom I can still see the hspl 2.08 if I switch on the phone keeping the volume down?
Thx guy!
Click to expand...
Click to collapse
it has to be hardware if the problem occurs with different roms / radios. (a different though similar problem happened with me- eventually it all stopped working.) i would try to return it...
no matter what rom you have you can enter bootloader (like you said with volume down) and see what spl (or hspl) you have. if you flashed the original rom from your pc hspl will still be there; if you flashed from your sd card it is likely back to spl.
cheers.
yep it's a hardware problem. i know because this just happened to me last week, except that the start menu would pop up instead... i did multiple hard resets but nothing. t-mobile said it's a common issue with our phones though your the only other case of this happening that i know of... other than me lol. you'll have to get a new leo
so if I have properly understood your verdict is to flash original rom from the SD and return the phone to HTC get it fixed (it is obviously still under warranty!!),,,right?
How strange.
My HD2 has just started to do the exact same thing. When WinMo boots the screen works fine but when it has been in standby and i press a key to waken it up, the screen does not respond.
I have done a hard reset also and it is still not playing up.
Looks like i'll need to call the insurance company.
lane2m said:
so if I have properly understood your verdict is to flash original rom from the SD and return the phone to HTC get it fixed (it is obviously still under warranty!!),,,right?
Click to expand...
Click to collapse
yes.
flashing from the sd should get rid of the hspl so all should be back to normal (i would double check though with a quick launch into bootloader...)
good luck!
damn I have the same issue right now. i thought it might have been a bad rom that i flash. i have to reset my phone every time i want to you use it. I cracked my screen so I don't know if that would void any mfg warranty on it.
Sent my handset to HTC on 8th Sept. Got it back on 28th Sept with new screen and new outer case which had a few chps and scratches.
All working fine again. Long time to wait tho. A day off 3 weeks
I am having this exact same problem. I had a feeling it was the hardware after it started doing it in Windows as well as Android. If we didn't purchase the insurance from T-mobile do we send the phone back to HTC via our T-Mobile store. I have had the phone for about 6 months now. Is it a costly fix?