[Q] Compass not working - HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting

Hi,
since my Blackstone was stolen some days ago i own a HD2 Leo now.
But the digital compass does not seem to work.
It stays at 6076° N for about 2 seconds, switches to 101° E for like 0.5 seconds and goes back to 6076° N. I did like a hundred eight figures as demonstrated in the youtube Video by the iPhone-Guy... no results. I'm using Artemis v36 atm, did not test it with the stock rom unfortunately. Could it be a hardware failure?
Thanks for any hints...

i use also Artemis rom, and it is working fine.

I just removed the HSPL and flashed a Vodafone Stock ROM: Same behaviour, but now it starts at 5812° N, goes to 101° E and back to 5812°.
Guess i have to send it back to the Dealer.
...and another painful Days (or weeks...) without a phone.

Related

Radio sudden death issue knowledge consolidation

There have been multiple cases of Radios suddenly stopping to work lately. This is not related to NO GSM error as these occur while phone is in use and not while flashing.
Symptoms are as follows:
- Radio suddenly ceases to work (no signal with any SIM), or its condition deteriorates over the time.
- While trying to flash a different Radio ROM, the upgrade stops at 0% and bricks the device
- Devices can be recovered to operating state, however only OS is intact and GSM radio does not work.
- MTTY gives no feedback
- Information about device resembles these symptoms:
Radio Version : Nothing
Protocol Version: Nothing
IMEI : Nothing
Possible causes of this problem:
- Hardware fault
- Radio ROM corruption
- Bad blocks in NAND
This phenomena seems to be the new source of bricked Hermes devices and the number of occurences is growing.
Threads of people with this kind of bricks:
http://forum.xda-developers.com/showthread.php?t=346315
http://forum.xda-developers.com/showthread.php?t=345230
http://forum.xda-developers.com/showthread.php?t=347145
http://forum.xda-developers.com/showthread.php?t=346894
http://forum.xda-developers.com/showthread.php?t=338413
http://forum.xda-developers.com/showthread.php?t=322587
http://forum.xda-developers.com/showthread.php?t=325018
http://forum.xda-developers.com/showthread.php?t=343260
There also were some threads with this issue in the Hermes WM6 forum.
What we do not know is:
- What was the last radio version those people used?
- Did they use custom ROMs or did it happen with official ROMs too?
- What do these cases have in common?
- Is it really a hardware fault (no results from the service centers so far)?
- Can something be done to prevent this kind of bricking?
- Anything that might help those people recover the phone capability of their devices.
Please share your knowledge about this problem so we can know what kills our device's radio.
Common symptoms:
ROM with radio (both official and unofficial) - flash stops at 12% (magic number?)
Radio ROM stops at 0%
After reading a lot about flashing - upgrading the Tytn, i think the first question to be answered is:
Has anyone with an official untouched device had the radio death situation??
(i.e never had any cooked-baked-boiled rom or radio other than the official flashed on the device)
On every incident i have read, there was at least one mentioning of "Unlock, SuperCID, HardSpl, cooked XXXX-WM6 rom, and so on.
Is it a coincidence?
Dont get me wrong, i my self love this forum and have used tools and roms many times (previously on my MDA Pro and now on my Tytn).
my unit started the NO GSM syndrome just 3 days after i upgrade to 1.54.00 radio..
ROM without radio - flashes 100% working
ROM with radio (both official and unofficial) - flash stops at 12% (magic number?)
everyone else has thier rom + radio flash stop at 12%
I would add: http://forum.xda-developers.com/showthread.php?t=343260
First post updated with your comments&link.
I opened mine this week, cleaned the inside and also taken the metal covers inside off. One very small chip looks like it has a little brown spot on it, like it has gotten too hot.
Don't know if this is the problem or not, but i think it has to do with the radio and that it's fried
my radio rom was 1.54 something i believe.
and before it broke my phone started to hang short times for a few weeks and when it got back the radio signal was also lost,so i guess it was starting to break down
now it is just a pda, i connect it to internet through my old phone, but it takes 5 minutes after turning on before it will use bluetooth, some programms also refuse to start in the first 5 minutes.
I have been seeing what I think is the beging of this issue. It started about a week or so ago, my phone locked up on a call so I soft reset it. IT cam back and I was able to use the phone again. About ten minutes later it locked again and this time when it came up my passcode would not work. After trying to log in 8 time it hard reset itself. I let it reset and then I upgraded my radio from 1.48 to 1.54.07.00 as I thought the radio was hanging the phone. A few days went by and everything was fine. Then I started to notice the radio was completely loosing signal and seeminlgy locking the phone. The only fix seemed to be a soft rest (at the time) This went on for a few days and eventually my password died again after a soft reset. and it hard reset me. At this point I upgraded from vp3G 3.0 to schapps 4.20 and 1.54.30.10 for the radio. Again it helped for a day or two maybe but it has not started to loose radio signal completely (no service and modem disconted error etc were I always have signal) I have tryed a few diffrent rom and radios in additon to all of these and still get the issues. Last night I got some more clues after installing the new google maps with the my location "soft gps". I was playing with it on my ride home folling my trip etc and about 25 min in my radio started acting up. This time the only thing that fixed the issue was to remove the battery and sim card and put them back in. I am startign to think this is a heat issue in one of the radio components. I also have a ruberized cover which could contrinute to a heat issue. Also for the record I have IPL-1.04 and SPL-2.10-0lipro.
Can anyone comment on ROM botloader etc AT&T would want to see on the phone if I got them to replace it? It is only like 3 months old.
Ma
Great idea to open this post. Here's my experience of 2 issues I had this week:
First, I changed the ROM to HC Lite, and the Radio to 1.54.30 last week-end.Before that I never had an issue with GSM.
3 days later I operated a clean-up, using Oxios Close-Apps and Hybernate.1 or 2 hours later, the GSM signal disappeared, and the green button stopped responding. I also noticed I was unable to open "Contacts". Nothing would make it come back, not even a soft reset.
What I did is a Sprite backup, in case, then a hard reset. Everything was then back to normal, so I restored the backup, and it kept working! Now the sad part is that the exact very same event occurred today.
I'm a bit confused whether the issue is hardware related, or is it to do with the radio, the rom..? Anyway, I will right now change the Radio so as to see if any improvement. Your comments will surely be appreciated.
It seems to be related to the newer radio versions. I am running the 1.47 that came with the official Dutch WM6 Rom and have had no problems what so ever with Schaps Rom. So my guess is that it is related to the 1.54 versions of the Radio.
Anyone had these problems with the older radio versions?
Just thought I'd add some info to this topic. I have been running Radio 1.54.00.10 for about 1.5 months with Schaps 4.20 and vp3G's 3.62.3 and have not had any problems with reception, phone use, etc, but I ran 1.54.07.00 radio for 2 days and it was terrible.
It would hunt forever for a signal. If I went into a building and lost reception, I would have to soft reset to get a signal (after I left the building). I figured something was gonna get damaged(too much heat).
I don't know if anybody's experience with that version was as bad as mine, but I hope this problem can be narrowed down to a particular radio rom.
sbrown138 said:
I have been seeing what I think is the beging of this issue. It started about a week or so ago, my phone locked up on a call so I soft reset it. IT cam back and I was able to use the phone again. About ten minutes later it locked again and this time when it came up my passcode would not work. After trying to log in 8 time it hard reset itself. I let it reset and then I upgraded my radio from 1.48 to 1.54.07.00 as I thought the radio was hanging the phone. A few days went by and everything was fine. Then I started to notice the radio was completely loosing signal and seeminlgy locking the phone. The only fix seemed to be a soft rest (at the time) This went on for a few days and eventually my password died again after a soft reset. and it hard reset me. At this point I upgraded from vp3G 3.0 to schapps 4.20 and 1.54.30.10 for the radio. Again it helped for a day or two maybe but it has not started to loose radio signal completely (no service and modem disconted error etc were I always have signal) I have tryed a few diffrent rom and radios in additon to all of these and still get the issues. Last night I got some more clues after installing the new google maps with the my location "soft gps". I was playing with it on my ride home folling my trip etc and about 25 min in my radio started acting up. This time the only thing that fixed the issue was to remove the battery and sim card and put them back in. I am startign to think this is a heat issue in one of the radio components. I also have a ruberized cover which could contrinute to a heat issue. Also for the record I have IPL-1.04 and SPL-2.10-0lipro.
Can anyone comment on ROM botloader etc AT&T would want to see on the phone if I got them to replace it? It is only like 3 months old.
Click to expand...
Click to collapse
I had the same kind of behavior with mine. Radio was 1.47
After a few days of similar misbehavior... the radio died
sdemon said:
It seems to be related to the newer radio versions. I am running the 1.47 that came with the official Dutch WM6 Rom and have had no problems what so ever with Schaps Rom. So my guess is that it is related to the 1.54 versions of the Radio.
Anyone had these problems with the older radio versions?
Click to expand...
Click to collapse
Nope, I had it with 1.47 back 6 months ago...
By the way
To me it is obviously hardware related: if I try to flash the radio 5 or 10 times I end up managing in flashing it (I have to try, retry, etc...) with another radio. However... I still have the No GSM issue, even after the new radio has been flashed
It's the best proof soemthing is broken inside, not just the radio
Alcibiade said:
I had the same kind of behavior with mine. Radio was 1.47
After a few days of similar misbehavior... the radio died
Click to expand...
Click to collapse
I've had this issue with every radio after 1.47, and multiple cooked ROMS, I've tried every radio newer than 1.47 with a bunch of different ROMS. My phone hasn't died....yet but I wouldn't count on it in an emergency or any urgent situation.
I haven't even had this phone 1 year, no way I'm going to spend 300+ AGAIN because of a ****ty HTC product.
What error messages are you guys getting?
I get (not verbatim) the following very often:
phone not ready, wait 15 seconds
answering modem has disconnected
(not a message) searching for signal
(not a message) no signal, just a ! in the signal meter
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
I have noticed lately that I have less problems in 3G areas.
eagercrow said:
I've had this issue with every radio after 1.47, and multiple cooked ROMS, I've tried every radio newer than 1.47 with a bunch of different ROMS. My phone hasn't died....yet but I wouldn't count on it in an emergency or any urgent situation.
I haven't even had this phone 1 year, no way I'm going to spend 300+ AGAIN because of a ****ty HTC product.
What error messages are you guys getting?
I get (not verbatim) the following very often:
phone not ready, wait 15 seconds
answering modem has disconnected
(not a message) searching for signal
(not a message) no signal, just a ! in the signal meter
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
I have noticed lately that I have less problems in 3G areas.
Click to expand...
Click to collapse
I have the EXACT same problem as eagercrow. The only difference is that I HAVE NOT *repeat* HAVE NOT mod, or use any cooked ROMs. When i'm using WM5 and radio 1.04, the problem did happen very often. Then when the official WM6 witn radio 1.47 release by HTC, i flash it straight away. It clears all the problem for a few month but some of the problem start to appear since last month:
answering modem has disconnected
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
It happen in any area with weak network (less than 4 bar/full), either 2G, 3G or 3.5G.
For answering modem disconneted, i have to shut down the phone and remove the battery to solve he problem. I must say that the problem may be due to heat. Since when i using it as a modem, the phone gets pretty hot.
I wonder why since i'm using the official ROM only (i've never use any cooked ROM). Even HTC servrice center can't really solve the problem. (my phone board controller was faulty and HTC changed it for me. After that all those problem just vanish for a few month). HTC says its normal!. I paid almost USD600 for the phone. I'm thinking of getting O2 but my friend says he had almost similar problem.
Wonder why......
I forgot to add one more problem to the list, phone sometimes will not disconnect from a call, I have to soft reset
eagercrow said:
What error messages are you guys getting?
I get (not verbatim) the following very often:
phone not ready, wait 15 seconds
answering modem has disconnected
(not a message) searching for signal
(not a message) no signal, just a ! in the signal meter
call not completed
(not a message) phone hangs when dialing a call
(not a message) received calls sent straight to voice mail when I have full signal, either a soft reset or attempt to make a call fix the problem. The attempt to make the call fails and the phone reconnects to the network.
Click to expand...
Click to collapse
I get most if not all of these 'errors'.
eagercrow said:
I forgot to add one more problem to the list, phone sometimes will not disconnect from a call, I have to soft reset
Click to expand...
Click to collapse
I get this one alot! But first it drops the actual call then just hangs the dialer.
two more to the list:
- long error message about the number not being right or something
- call not completed
sbrown138 said:
I get this one alot! But first it drops the actual call then just hangs the dialer.
Click to expand...
Click to collapse
Yeah that is what is happening with mine, the phone call is ended but you wouldn't know it by looking at the phone.
Well i didn't do my searching right, so i posted my issue in a new thread...
My issue is almost the same...It all started with BT getting disconnected from headset, and only soft reset will connect again...and then, radio started to act up. Phone went to sleep one night, and the next stay when i tried to wake it up, it wont wake up. Had to reset it to wake it up...it came back up, but when i plugged it to the puter, the puter wont recognize it. Here is what has happened so far...
1. GSM works after soft reset, and when on phone the phone freezes. Soft reset is the only option...(call is continued until soft reset)
2. BT will disconnect and will take forever to start up
3. Phone will not be recognized by PC (USB device not recognized error)
3. Can flash OS, Splash screens, ext ROM using SD flash method, but will not flash OS with GSM...hangs about as soon as it starts GSM (about 12%)
4. GSM, protocol numbers are still intact
My phone is less than 2 months old and i didn't get my phone through AT&T, so no warranty...kinda screwed eh I think this is a hardware problem...

Device screen sometimes does not turn on.

I have tried about 5 different WM6 roms from here mostly Gullums roms(VII, VIII, IXb, X). I am sure there are other roms that I cannot remember. By the way thank you to Gullum for his hard work cooking these roms. They seem to work fine for a few days then my device's power button will not turn on the screen and I cannot pick up a call or use the device unless I do a soft reset. The last rom I had which was VIII would require a hard reset and a lost of data. My question is wether this is the roms which have issues or just my device which is dying slowly. When I first got this device I had to ship it back to Spain because the motherboard died after a few days of use and flashing from WM5 in Spanish to WM5 in English. Has anyone had similar issues with their qtek s200 after flashing.
hope it might help!
yamilrx said:
I have tried about 5 different WM6 roms from here mostly Gullums roms(VII, VIII, IXb, X). I am sure there are other roms that I cannot remember. By the way thank you to Gullum for his hard work cooking these roms. They seem to work fine for a few days then my device's power button will not turn on the screen and I cannot pick up a call or use the device unless I do a soft reset. The last rom I had which was VIII would require a hard reset and a lost of data. My question is wether this is the roms which have issues or just my device which is dying slowly. When I first got this device I had to ship it back to Spain because the motherboard died after a few days of use and flashing from WM5 in Spanish to WM5 in English. Has anyone had similar issues with their qtek s200 after flashing.
Click to expand...
Click to collapse
i am pretty soure but i have been using Gullum for very long time and i didn't get any trouble like u but this day i found some other too so i am suing othere too. but i never found like u have the problem.
so why not try from other master so u could have solved by ur self.
i have read on this forum and some where else it said if u do restored then u might got this problem but as u said it nbot
so just change clean rom WM6 and try sor some days i guess u will find findout. hope.
hope it might help u out
I am now trying transformer 1.1 and so far no power button issues. Its only been 24hrs. The problem tends to happen anytime but usually after 1 week of installing. The other issues I was having with the other roms listed was that the program would get stuck on the second screen past the initial ipl/qtek screen. Hopefully this rom will work.
I have this problem as well, but believe it has to do with Pocket player. Are you using any applications that listen to button events?
DarkMannen said:
I have this problem as well, but believe it has to do with Pocket player. Are you using any applications that listen to button events?
Click to expand...
Click to collapse
I am not sure what you mean. Do you mean the windows music player. I am trying the transformer 1.1 rom but after 48hrs, today the same thing happened. I was just surfing the web on opera while in line to vote. It has happened while receiving a phone call as well and I cannot turn the screen on to answer. I did a soft reset and everything was ok. Unfortunatelly sometimes also what happens is that the software doesn't load and it requires a hard reset.
Actually i had the same problems when i use gullums rom for some reason.. I have had this problem with all of gullums rom except the coffie rom ! Try that and report back..
sorry, thread flush only~~
I also had the mentioned problem, especially with the battery <50%.
Sometimes, when I'm listening with the built in audio player and the screen is off, the playback stopps right after a track and the screen won't turn on again.
A softreset helped each time.
Also the phone is logged in in the gsm net, the caller hears the ringing, but the phone didn't ring.
Strange thing. I had the problem with ProphetTouch IX and VIII, yesterday I flashed number X.
ganjaninja said:
I also had the mentioned problem, especially with the battery <50%.
Sometimes, when I'm listening with the built in audio player and the screen is off, the playback stopps right after a track and the screen won't turn on again.
A softreset helped each time.
Also the phone is logged in in the gsm net, the caller hears the ringing, but the phone didn't ring.
Strange thing. I had the problem with ProphetTouch IX and VIII, yesterday I flashed number X.
Click to expand...
Click to collapse
I have had same issue with all of those. I'd hate to downgrade to wm5 to try it a couple of days and see. Maybe I'll do that.
After closing all running programs, especially Conduits Pocket Player, this problem seems to go away. I have noticed that when I start the pocket player and wait until the screen turns off, I can not turn it back on with the power button.
I my case it seems to be connected with Pocket Player, but it could just as well be ROM related. I'll keep looking for a source.
I hope there is a simple solution to this, as it is quite annoying.
i have the same problem b4 last time, when the batery status- lock device when wake up fuction is tick.

HTC TYTN HERM200 Weird Can't reflash?!!!

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.

Touch screen is unresponsive... Please help

My touch screen will not work at all, everything else on the phone works just fine. I tried a hard reset and now I am stuck at the alignment screen. Any suggestions.. Anyone run across this error?
Thanks
reflash bro
put the stock rom back on
and then put the modded rom on
and it should be fine
Typically means something is interfering with the recognizer.
If you are using a protective case (shell) or screen protector, try removing them temporarily to see if they may be causing your problem.
I didn't have anything over the screen.. Any idea why it would do something like that?? I'm going to reflash to stock and back to modded ROM tonight and I'll let you guys know in the morning.. Thanks for your help.
Could be a "bad" flash.
If it still happens with the stock ROM flash, you may have a defective unit on your hands.
Hardware problem?
I had the exact same problem about a week ago. I tried reflashing the device, hard reset, etc. In the end, I couldn't even get past the screen calibration wizard. My conclusion was that I had some kind of harware problem -- the touch screen would respond intermittently for brief periods of time and then go unresponsive again.
My fix: I took the phone to my ATT service center who, much to my gleeful surprise, gave me a new one (warranty exchange) without any hassle. I expected to have to fight with them, but the transaction was trivial and stress-free.
I'm now deciding which WM 6.5 ROM I like the best. Many thanks to all the hard-working contributors and chefs on XDA for providing such awesome content and support!
Good Luck with your phone
i also had this problem recently. phone was working fine in the night, went to bed and woke up and was unresponsive. Tried everything. I ended up flashing back to all the stock stuff and sent it in for repairs. I got the screen and dpad replaced under warranty. I have no idea what caused it, but it happened. Definately not a software issue if you have reflashed...
my advise, flash back to stock spl and your carrier rom and send it back.
I had a similar problem and opened a thread as well. My problem in chronological order
1. Bought a TMobile MDA IV over ebay.
2. Flashed several different ROMs of WM6.1 and was just enjoying myself.
3. Installed a 6.5 ROM the calibration screen required me to go through 3 full circles.
4. Worked fine for a day, then the device was locked and watever I tried I just couldnt get to open it up
5. Did softreset, it didnt help either. I Would end up at lock screen
6. Finally got back to HTC stock ROM 6.1, and I couldnt get past the calibration screen for a month.
7. My conclusion as well, that its a hardware problem, unfortunatel where I live I dont have Tmobile and the screen from touch pro is slightly different in size to the tmobile variant.
8. Hence it was a brick!!!!
9. After a month just last week, I thought of trying to flash back to 6.5 and see if it works.
10. Went calibrating in circles for about 10 times and guess wat!!!! It starts up!!!!
Now my conclusions are as good as anyones, it cant be an hardware issue. I am trying to find a solution so I can reflash my ROM and go to a stable version and live with my phone atleast for an year.
The Mystic ROM lite version has touch response software built in, Could this be the issue.
Anyones got any idea let me know

Screen goes black for 95%

Hi there,
I've seen many topic about black screens, but none simulair to the symptoms I am seeing.
I have this after the very first time I flashed by phone (approx a month ago). Today I installed version 3.25.1 (3251-23081-3G) and also on this version I immidiately had this problem (note: it does not always happen. It happens a few times a week).
Symptoms:
My device is fully functional and the screen is normally working also properly. After a certain timeout the screen goes completely black/off which is expected (saving energy).
Sometimes (randomly), when I shortly press the power button to turn the device on again, only the top bar (where the icons are located for battery %, signal strength and 3G) is being shown/displayed. Rest of the entire screen is black.
Device info:
niki200
spl-1.22.Hard
cpld-4
R 1.65.28.25
G 25.98.40.07h
D 2.16.831.03
dirkjanv said:
Hi there,
I've seen many topic about black screens, but none simulair to the symptoms I am seeing.
I have this after the very first time I flashed by phone (approx a month ago). Today I installed version 3.25.1 (3251-23081-3G) and also on this version I immidiately had this problem (note: it does not always happen. It happens a few times a week).
Symptoms:
My device is fully functional and the screen is normally working also properly. After a certain timeout the screen goes completely black/off which is expected (saving energy).
Sometimes (randomly), when I shortly press the power button to turn the device on again, only the top bar (where the icons are located for battery %, signal strength and 3G) is being shown/displayed. Rest of the entire screen is black.
Device info:
niki200
spl-1.22.Hard
cpld-4
R 1.65.28.25
G 25.98.40.07h
D 2.16.831.03
Click to expand...
Click to collapse
Maybe you should upgrade your radio...or maybe reflash the same version. Seems to be a problem with power management.
New Radio?
AFAIK this is the latest working Radio for NIKE200
Have tried to install 1.71.09.01 several times, but my phone cannot boot after completing (100%).
Have been flashing quite some times today, but am getting bigger problems now (e.g. phone freezes when syncing mail).
Will try to use an official ROM, test everything, and than try to flash again to a new version
dirkjanv said:
AFAIK this is the latest working Radio for NIKE200
Have tried to install 1.71.09.01 several times, but my phone cannot boot after completing (100%).
Have been flashing quite some times today, but am getting bigger problems now (e.g. phone freezes when syncing mail).
Will try to use an official ROM, test everything, and than try to flash again to a new version
Click to expand...
Click to collapse
to flash the 1.71.xx.xx radios you need to downgrade to a 1.58.xx.xx radio before
to flash the 1.71.xx.xx radios you need to downgrade to a 1.58.xx.xx radio before
Click to expand...
Click to collapse
Arggh, OK, will try that this weekend (no time most probably during this week).
About the 95% being black: problem is still there after the latest test.
People can still call me, the interface is simply not showing anything...
I notice that when the problem is not there when switching on the phone, it often takes 0,x seconds to have the 'main window' visible (it's black for a very short time).
I do not need to do anything to break it: simply let the phone on the table during the night, and the next morning I can only see the top bar indicating the UMTS status and other (mini) icons.
Very odd I'm the only one that seems to be having this.
Got this with multiple non-official roms. To me the problems seems to be related to the TouchFlow 3D stuff that shouls fill the main window.
dirkjanv said:
Arggh, OK, will try that this weekend (no time most probably during this week).
About the 95% being black: problem is still there after the latest test.
People can still call me, the interface is simply not showing anything...
I notice that when the problem is not there when switching on the phone, it often takes 0,x seconds to have the 'main window' visible (it's black for a very short time).
I do not need to do anything to break it: simply let the phone on the table during the night, and the next morning I can only see the top bar indicating the UMTS status and other (mini) icons.
Very odd I'm the only one that seems to be having this.
Got this with multiple non-official roms. To me the problems seems to be related to the TouchFlow 3D stuff that shouls fill the main window.
Click to expand...
Click to collapse
Niki can't run TouchFlo 3D, maybe you mean Manila2D... Anyway what model do you have? It's a branded model like T-Mobile MDA Touch or a stock HTC model?
HTC Touch Dual
lapy said:
Niki can't run TouchFlo 3D, maybe you mean Manila2D... Anyway what model do you have? It's a branded model like T-Mobile MDA Touch or a stock HTC model?
Click to expand...
Click to collapse
Using the 'FINAL Insomnia v3.25.1 - 23081' versio which has TouchFlo 3D.
Is working, but as explained, with problems...
It's a T-Mobile branded version, but that isn't relevant right now, as the device is fully flashed and unlocked.
I have now installed a new ROM (can't find the download link/forum post anymore... ) which does not come with TouchFlo 3D, and is running stable.
As all others do not seem to have problems with running TouchFlo 3D (read: the Insomnia image), you can try it as well if you want it.
If you get a black screen after a while (phone is still operating and people can e.g. call me (and I can pick-up the phone)), so you have to restart the phone on almost daily basis..

Categories

Resources