After applying my vans breaks a little abruptly my xda2 hit the deck and now is kaput. Here are the symptoms.
Radio started to fail and would not pick up service, then
Rom crashed and would not reboot.
Occassionally it reboots as far as the today page, memory is wiped and Activesync has trouble detecting device. Sometimes can log on as guest before the whole thing crashes again.
I am hoping the solution is to reflash the rom from hard reset, but unsure how to do that.
Further difficulty: It is a German xda2 with a Tmobile 1[1].60 WWE rom I flashed myself. I know for a fact O2 Australia will make me send it back to Germany because they aren't really that helpful. They will say they don't have the foriegn software. Aren't all himalaya machines the same regardless of origin?
Thanks for any replies or at least your condolences
I would have thought the repair centre would have access to all files, having said that I think they will probably replace the motherboard anyway.
Right i need some help, big style.
Had me phone now for nearly a couple of months and it's been fine. Then today it all went wrong. Firstly the phone just did'nt work no signal or anything. Tried everything to fix but nothing seemed to work. So hard reset. Now the phone boots up and goes thru setup etc.. (but no 02 option??) gets to my today screen but when I choose anything i get a msg saying did i want to run unknown program etc.. choose yes/no. I have chosen all the combinations to get it to work but the phone sometimes freezes so i have to soft reset to get going but then I'm back to square one. I've downloaded the backup o2 rom but when i run it i get an error saying it cannot create a folder??? So at the moment i can use the phone sometimes but sometimes it freezes up 9/10 i cant sync with comp.
Before you ask I only have tomtom installed and afew themes, and the xda worked fine before hand.
Any ideas please would be a great help. If not I'll be straight on the phone to o2 to get a replacement.
cheers
screen shot of the error msg i get
screen shot of the error msg i get
Right getting really annoyed now with my phone :evil:
managed to get it working again after downloading the o2 rom and re-flashing. Since i started this thread i have re-flashed rom about 3 times!!!! My phone just stops working. No network signal or anything!!! All the problems started after i install wisbar, phones never been the same since. stoped using wisbar and started pocket plus. phone worked fine until i soft reset cus it frooze. when it restarted nothingworked. I'm just about to flash again for the 4th time. Only gonna install tomtom and eten dialer and afew games thats it. I'll install in basic mode but wont delete any o2 files as normally do. If it goes again after this it's going back to o2.
cheers
Well, simply send it back for warranty repair, what's the problem? These things happen, I'm used to that... had to bring my Nokia 6600 back 2 times during warranty year... :?
does it damaged the phone if your constantly re-flashing the rom?
Sorry to keep posting but is there an anti-virus software or something cus i think there must be something on my xda cus even after flashing the phones still not 100%
cheers
Keep in mind, by the way, that flashing your rom with any ROM other than one provided to you by your provider is grounds for voiding your warranty
yeah I know i just thought that may fix whatever problem there is. I think i've just got a dud mini s. Worked fine for a month but now it's gone crazy. I think re-flashing with the o2 rom 5 times and still no joy means the phone will go back.
I'll ring o2 first thing in the morning.
cheers
I'm starting to freak out a little - everything was fine, and then about an hour ago, I pulled my M600 out and tuned it on - to my surprise, it went though the boot process as if it had been soft reset.
Then when it got to the blue Windows Mobile screen, it seemed to be loading (with the 4 coloured circle) and then it pinged and stayed there.
I took the SD card out and tried again. Same thing. then I tried a hard reset. Same thing. This is when I started getting worried.
Has anyone else experienced this? My phone isn't on contract, so it's not covered by insurance. Is there any way I can get it repaired?
**Update** May be a dodgy battery. So there was no real need for a hard reset, and I've lost all my stuff. Ah well, I'm happy that my phone works.
Can you elaborate more on this?
I have seen this problem several times on my S200 and the only way out is to hard reset the device. That's why I always keep my backups updated as often as possible.
But even then, there are several things that do not restore, like contacts, appointments and sme today plugin settings.
Any ideas?
I've just had an Imate Jamin do this - the only difference bing that it doesn't get past the HTC splash screen so isn't getting as far as yours. Tried everything I can think of to no avail. It is now being sent back to Imate for repair.
In your case you might be able to try reflashing the device from an SD card. I could still get the Jamin into bootloader, yours might be the same. However for me as it is only a month old it is still covered by warranty.
I'm using VZW's official 6.1 rom.
This problem started two days ago when i changed the text message settings from threaded to classic. Did a soft reset, and got stuck at tri-color bootloader screen.
I am using the titan exit bootloader program to get myself out of it, but I get stuck again on every soft reset.
I was able to successfully re-flash the official rom, so I thought my problem would be fixed... but it turns out soft resets STILL put me in bootloader.
I'm not sure what the problem is. I have no third party programs installed...
Help?
I had something similar happen on my Verizon X6800, I installed Delorme mapping software and it worked and then after the first run it started going to the bootloader (gradient color screen) with only TITA100 showing. The only way I could rebooot was to remove the battery for several hours and then start it up again and it would work for a short period of time but then eventually go back to the bootloader screen with nothing functioning. I managed to get all my personal info off the phone but that was about it. My phone was within warranty and I was able to exchange it through Verizon, but they gave me a load of crap and repeatedly kept saying you cannot load third party software on the phone or it voids the warranty (I said, you're kidding me, that's why you buy this phone is to make it do tricks other phones can't). I had to take it into a Verizon store and have a "tech" look at it before they would process the exchange. The guy kept saying you can't install 3rd party software, eventually he explained it looked like I cooked the ROM trying to modify the ROM. I had no intention of doing that. I think the ROM was faulty not to mention it zapped my 4 gig SD card.
I have a UK supplied Touch HD from Orange and it`s going crazy!
Problem 1:
Backlight switches off without warning, touchscreen still responds but obviously you can`t see anything! Multiple hard resets will eventually coax the backlight to wake up, but the delay between power button pressed and the "first buzz" of life is around 20-30 seconds. Started happening when it was about 2 months old. Initially it was infrequent and I put it down to an installed software problem, but now every few hours. Other symptoms include the charging light failing when the backlight fails and there is usually an increase in heat around the case. Strangely however when I use it as a sat-nav and it is permanently charging the backlight never fails. I have tried a new battery, desktop charger, turned off fast-sleep, autolock, light sensor, full reset and removal of all my software and it still does it. Sometimes its OK for 5 days, other times it goes "dark" after 10 minutes.
All ROMs updated to latest versions. NB This started happening with the original Orange installed ROMS
My original solution to the problem was to run bootloader which forced the backlight on, but the long delay between on/off and start means this doesn`t work anymore.
Problem 2:
Screen display appears inverted and mirrored after pressing power button during operation. This is an infrequent problem but may be connected.
I live in Thailand now. HTC Thailand will no doubt take it and charge me $250 for a new motherboard whether it needs one or not. I can`t easily return it to the UK and I just hope somebody somewhere has some ideas?!?
I was just talking to another user with completely bizarre issues. What you are experiencing is totally abnormal. Just to make sure it's not a software issue- what SPL version shows up in your bootloader? Also, what rom are you currently running?
Please read next post
Please read next post
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
jamesmclean said:
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
Click to expand...
Click to collapse
So is the phone working properly again with the factory Orange rom? All I can tell you is that if you want to run the 2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship rom you must have a base SPL of 1.54.0000. Even if you use USPL to flash the rom to bypass CID-locking you still need to upgrade your SPL because the new 1.56+ roms are not compatible with an SPL version less than 1.54.0000. Read the guide in my signature for more information.
I see cRaCKwHoRe is on your case, so your in safe hands. I'll leave it to him.
One suggestion though. Instead of creating new posts and saying 'Read Next Post', why not just edit your first post and state 'EDIT' or 'Update' with new information below. This way thread remains short and easy to follow
Just an idea mate!!
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
jamesmclean said:
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
Click to expand...
Click to collapse
Most virus scanners show a false positive that USPL and HSPL are trojans or viruses. This is based on heuristics and how these utilities work. They are tried and tested and are most definitely safe.
And again I stress that you cannot run a 1.56+ rom on an SPL version below 1.54.0000. Since you are running SPL 1.14.0000 this is why you are having such issues. You need to flash a newer SPL version!
After the hardspl back to original Orange ROMS:
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
I had 2 dark events. I wondered if there could be a problem with the memory card, so I took it out. My reasoning being, after it goes dark and is reset, something was causing it to wait 30 seconds before "smart mobility" and/or buzz (if the screens still alive). When my PC does that its usually because there`s a memory card or external hard drive confusing it. Took out the card and it was OK all night. Formatted the card this morning and had no problems all day.This is a guess, I am an idiot! But the memory card is the only ongoing part of my phone; internal storage and ROMs has been cleared or upgraded every month.I dont doubt my feeble attempts to upgrade to 1.56 and bypass HTC`s no upgrades for Orange handsets policy may have been a significant contributory factor. Interestingly, Orange are actively discouraging purchase of the HD, they have had too many problems with their handsets.
Going to keep the phone empty for a few days, no software, no sat-nav and see if I have any more events. Then I think will read your HARDSPL instructions far more carefully and retry the ROM upgrade. Excellent work by the way!
The odd thing about this telephone (apart from the inversion and mirrored display problem, which still occurs) is that following the nuclear option of total clearance and ROM upgrade/downgrade it will behave for an number of days and then the backlight dies again. It could still be hardware!
Going to keep my eye on things for a few days.
But if anyone else has had these problems with their HD or Orange handset, please tell! Maybe you aren`t crazy! To help this is a list of symptoms:
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Thanks!
Looks like a SPL problem only. It is responsible for the boot events and mismatched display drivers between SPL and the ROM most likely did it. Anyway interested in knowing updates once U flash a new SPL 1.54. and ROM..
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
jamesmclean said:
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
Click to expand...
Click to collapse
That's really unfortunate. Seems you have bad luck, consistently
Most people really like HTC devices. They do actually make some pretty decent stuff. Seems you've just gotten rotten luck.
Taken it back up to 1.56 with Hardspl as suggested. Installed Dutty 3.4. And it worked... For one night! Dead again today. I think now it is a hardware fault. So I suppose she`s off back to HTC and I will have to pay some money.
I have been very unlucky with HTC products. I said before I had to have 4 HTC Hermes, thought it would be interesting to tell what was wrong with them:
1. Orange SPV3100 WM5. First generation Hermes 100, hopeless wifi, buggy, returned to store and refund.
2. MDA Vario 2. WM5 Upgraded radio version, better wifi. Decided it didn`t like being a telephone anymore and the radio died after 3 months. Returned to store.
3. MDA Vario 2. WM5 Factory replacement. Dead memory card reader, didn`t make it out of the store when I went to collect.
4. MDA Vario 2 WM6 (Hermes 300). Working wifi, a much better operating system. A real telephone. Lasted 18 months! 2 weeks ago, complete power failure for no specific reason. Won`t charge or do anything now.
But before Nokia and iPhone customers get too smug. I also had an iphone when they were first released in 2007 (1.02) and that was a bug infested piece of junk as well. Got stolen in Bangkok. I really do miss having to reinstall the OS every 2 weeks! And my brother`s Nokia N95 has spent more time with Nokia than with him. 8 visits to Nokia care.
And now I have a broken Touch HD, probably with a power supply issue!
All these phones have one thing in common. They were (with the exception of the Hermes 300) first generation examples. And just before you rush out and pay big bucks for the latest telephone from HTC or whoever... Think, was this phone ready for release? Or was it just rushed out to keep the shareholders happy?
Think about it...
Hell! finally I found someone with the same problems. But I have bought it just some days ago!! The only thing I have done since then: installing tomtom on my sd-card and setting this gps-signal thing to the value 3000.
when I bought it i tried to run it in the store: after turning on, black screen but still vibration when i pressed some button, so it must have been on. Then it suddenly worked, installed the system, everything perfect. yesterday i installed tomtom, today it probably "died" around 20 times. everything the same like already described, screen messed up, after turning on vibration after 30 seconds, god!
is there anything i can do? i just bought that thing
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Click to expand...
Click to collapse
Sounds like you have the exact same problem as my HD: inverted screen, screen blank but still functioning etc...
http://forum.xda-developers.com/showthread.php?t=520781
I am waiting for mine to happen more frequently before sending it away for service. Otherwise they will just return it if they can't reproduce the problem.
Pretty sure it is a hardware problem. I am in Australia and have the original stock ROM.
We may be onto a new fault here. Just noticed 2 more threads with the same screen issues. My phone has been OK for a few days, but today screen won`t wake up at all. Hooked it up to Pocket Controller Pro and it`s reporting a "microp version mismatch 0" in its dark state. Been checking on other websites and this seems to have been a problem with Touch Diamond previously. There doesn`t seem to be an update for microp firmware. One user tracked it down to a loose connection between screen and motherboard. I don`t know! I just wish it would work!
Any suggestions for MICROP issue?
Currently running Dutty 3.4 with 1.56 Olinex. But this has been a problem long before this ROM version.
Fallen Spartan told me this:
"Have you tried going to Start > Settings > All Settings > System > Power > Advanced and making sure device isn't set to turn off after a period of time?"
Until now my phone works without problems, I will report again after some days
Yup, tried that one. Doesn`t work. You will notice after you end a call, the screen will be dim. This is the warning of imminent backlight failure. It is not power management dependent. My problems with the phone started in Feb. Initially intermittent. Now constantly.
Sometimes the thing will work for a few days for no reason. Only way to guarantee no failure is permanent USB power. Pull out the USB and watch it die, instantly! That`s with the original or the new battery.
New motherboard may be the only solution. But it is worth noting that when I had problems with my Hermes and it had to go back to HTC 3 times, each time a new phone was sent. On the service report "New motherboard" was reported. The guy in the T-mobile shop told me they`re too expensive to repair so it`s easier giving you a new one. They still hold onto the old one for 3 weeks though!
Might try to repair the Touch HD, I still have my Samsung SGH. (It`s very slow!) but I think I will wait for ASUS or Toshiba phones with snapdragon processors. Had enough of HTC and don`t want another iphone.
This is a hardware issue. No if's, and's or but's. It is caused by a disconnection between the screen and the motherboard. A faulty motherboard or a loose / broken connector is the usual culprit. I would say 7 out of 10 times it is due to a loose connector. It is a poor design to begin with and after being dropped or roughed up enough it tends to break or get loose. HTC typically just replaces the motherboard in a warranty repair situation.
If you are lucky and just have a loose connector and are comfortable with opening up the device yourself, you can disassemble the device and re-connect or re-solder the 2 port connector that connects the motherboard with the screen. Of course this will "void" your warranty so I wouldn't recommend doing this unless you are comfortable working on micro-electronics. If your case is the type where it is intermittent and it works sometimes and then sometimes not, then you have a loose connection and it just needs to be reconnected or re-soldered.
I have seen and fixed a couple of these now.