OK, I've been thru this twice now, so I'm pretty sure it's not a busted phone...
Personally, I've got a Sprint Mogul - runnin' Radio 3.39.10, and DCD 3.1.2 - everything's peachy-keen.
At work, I've got some XV6800's, stock, right outta the box.
I did the following the phone #1, didn't work at all (as described below), and repeated on phone #2 after thinking #1 was just a bad phone.
HELP!?
Phone #1:
Took it out of the box, booted it, let customization run, activated it - everything's happy-scrappy.
Flashed spl-1.20-olipro.
Went into boot-loader, flashed Radio 3.39.10 with RUU (don't have a card to do the SD method with - seemed to work fine)
Went into boot-loader again, flashed DCD 3.1.2
Booted to the first WM 6.1 screen, flashed spl-2.40-olipro.
Booted into DCD 3.1.2, can make calls, rcv/end txts...
NO DATA - and NO LOCK WITH GPS (installed QuickGPS & VisualGPS) - NOTHING.
Called VZW - spoke to some schmuck, said phone was busted, would send new one...
Phone #2:
Same process as #1, except I didn't activate this one with VZW, wanted to see if I could get GPS to lock up first... It sees Zero birds... NOTHING...
Since I got the same result with both phones, I'm assuming I missed something.
Yes, I ran DCD's carrier .cab for VZW on Phone #1, but it didn't solve anything. Didn't bother on #2 - I shouldn't have to do this for GPS, should I?
Please... What am I missing??? Anybody?
NetworkPIMP said:
OK, I've been thru this twice now, so I'm pretty sure it's not a busted phone...
Personally, I've got a Sprint Mogul - runnin' Radio 3.39.10, and DCD 3.1.2 - everything's peachy-keen.
At work, I've got some XV6800's, stock, right outta the box.
I did the following the phone #1, didn't work at all (as described below), and repeated on phone #2 after thinking #1 was just a bad phone.
HELP!?
Phone #1:
Took it out of the box, booted it, let customization run, activated it - everything's happy-scrappy.
Flashed spl-1.20-olipro.
Went into boot-loader, flashed Radio 3.39.10 with RUU (don't have a card to do the SD method with - seemed to work fine)
Went into boot-loader again, flashed DCD 3.1.2
Booted to the first WM 6.1 screen, flashed spl-2.40-olipro.
Booted into DCD 3.1.2, can make calls, rcv/end txts...
NO DATA - and NO LOCK WITH GPS (installed QuickGPS & VisualGPS) - NOTHING.
Called VZW - spoke to some schmuck, said phone was busted, would send new one...
Phone #2:
Same process as #1, except I didn't activate this one with VZW, wanted to see if I could get GPS to lock up first... It sees Zero birds... NOTHING...
Since I got the same result with both phones, I'm assuming I missed something.
Yes, I ran DCD's carrier .cab for VZW on Phone #1, but it didn't solve anything. Didn't bother on #2 - I shouldn't have to do this for GPS, should I?
Please... What am I missing??? Anybody?
Click to expand...
Click to collapse
personally i am running the 3.35.04 radio with more luck and quick gps lock. i also am using 3.1.2 dcd rom
and as far as data.... you have to have a dmu reset for it to work i'd just call and tell them you want a DMU reset i've had to do it more than once
EDIT also i have changed GPSmode to 4 instead of 2
coffey_joshua said:
personally i am running the 3.35.04 radio with more luck and quick gps lock. i also am using 3.1.2 dcd rom
and as far as data.... you have to have a dmu reset for it to work i'd just call and tell them you want a DMU reset i've had to do it more than once
EDIT also i have changed GPSmode to 4 instead of 2
Click to expand...
Click to collapse
Thx for that, Josh... I changed my GPSmode to 4, but to no real joy...
I figure I need the DMU reset and/or new AKEY from VZW - which I'm fine with calling and getting - but, I've got no workable GPS on either of these phones, and I'm still thinking that it's independent of data/activation, right?
BTW - let me define "workable" -> I put my Mogul next to either of these 6800's and turn on VisualGPSce, and the Mogul finds 7-10 birds and locks on within 5-20 seconds... This = "workable" to me. The 6800, on the other hand might see 1 or 2 birds, on occasion, then back to zilch, and never a lock. (This applies to BOTH of the 6800's I have in front of me!)
Also, I'd like to add that yes, I did turn Location ON in Phone/Options...
I've seen some of the big-wigs here seem to be running 6800's with DCD and Radios 3.35.04 & 3.39.10 with good results - i.e. a LOT better than mine...
So I ask again - any other idears!?
Like I said, no troubles on my Mogul - so what am I doing wrong? I'm pretty sure it's me .
Very frustrating seeing all the success others having with VZW phones, but not me? I'm noob-like, but I'd like to think I can hold my own!
Thx in advance to ALL!!
having the same problem, using new dcd with newest radio. tomtom 6.01.
i can surf the internet, does that mean i have data? or will i still need to reset dmu/akey? what's akey?
I can get a gps signal at all. using astro luancher.
auto3251 said:
having the same problem, using new dcd with newest radio. tomtom 6.01.
i can surf the internet, does that mean i have data? or will i still need to reset dmu/akey? what's akey?
I can get a gps signal at all. using astro luancher.
Click to expand...
Click to collapse
If you can surf in IE, you have data...
If you can make/rcv calls & texts, you have voice...
My experience is you can have voice and no data, or both, or none...
Two things:
Seems that you're saying you flashed the ROM, then loaded olipro 2.4-- should be other way around (of course after flashing radio on olipro 1.2)
Also, for DCD, you need to run the carrier cab after flashing the ROM. So if you didn't do that, that would account for the data problem.
ebb said:
Two things:
Seems that you're saying you flashed the ROM, then loaded olipro 2.4-- should be other way around (of course after flashing radio on olipro 1.2)
Click to expand...
Click to collapse
no, he did it right. the new radio roms will flash from RUU under olipro-1.2, but not under olipro-2.4. his order allowed him to flash the radio with RUU.
Also, for DCD, you need to run the carrier cab after flashing the ROM. So if you didn't do that, that would account for the data problem.
Click to expand...
Click to collapse
correct, there is no data connection configured without the .cab, unless you manually configure it under connections.
as for gps, we have been testing lately. it is totally possible that your gps refuses to work. it is very unlikely that the gps hardware is defective or bad in any way. there are low level radio parameters that are set differently on different carriers - some xv6800's are set in some way that screws up GPS. thats about all i can tell you right now. there is not a reasonable solution currently for VZ. some people are lucky and some are not, which may suggest that some XV6800's came provisioned differently. we are not sure yet...
i think that there are 2 differences between my device and yours:
a) my radio has sprint aGPS server info set.
b) my radio has some other provisioning flag set differently
we cannot do anything about A until a vz agps server is identified. we are working on identifying B.
without A or B, your GPS can work, but i've heard of it taking hours to pick up initially. try quickgps and clear line of sight to clear sky..
there seem to be some VZ users who somehow picked up "B" and the setting stuck. we cant confirm or reproduce this yet but it seems likely.
i'm not going to give any more details right now because people will start doing stuff to their phones to create themselves problems...
I use BAFS GPS launcher with verizon to get GPS working. I just turn it on for a couple of minutes, and then get a good, quick satellite fix with googlemaps or Live Search. You can find it in the GPS sticky topic at the top of the forum.
I thought I did agree in my earlier post about using 1.20 for the radio flash (that's how I do it), I just thought he had kept it at 1.20 for the ROM flash, then loaded 2.40, then flashed again. Maybe I read his first post wrong.
ebb said:
I use BAFS GPS launcher with verizon to get GPS working. I just turn it on for a couple of minutes, and then get a good, quick satellite fix with googlemaps or Live Search. You can find it in the GPS sticky topic at the top of the forum.
I thought I did agree in my earlier post about using 1.20 for the radio flash (that's how I do it), I just thought he had kept it at 1.20 for the ROM flash, then loaded 2.40, then flashed again. Maybe I read his first post wrong.
Click to expand...
Click to collapse
sorry, i misread your post earlier. i think we are all agreeing.
ebb if you start visualgpsce without doing anything else after a bootup, how long does it take you to lock? you shouldnt need to activate the port, vgpsce will do it.
Phone #1 has to go back in the next 48 hours or so, but I have phone #2 available to me probably `til Thurs or so...
Let me know if you want me to test anything with it...
I can get it activated in it's current state (olipro-2.40, radio 3.39.10, DCD 3.1.2)
dcd1182 said:
.....
ebb if you start visualgpsce without doing anything else after a bootup, how long does it take you to lock? you shouldnt need to activate the port, vgpsce will do it.
Click to expand...
Click to collapse
I'll d/l it and try and post back.
NetworkPIMP said:
Phone #1 has to go back in the next 48 hours or so, but I have phone #2 available to me probably `til Thurs or so...
Let me know if you want me to test anything with it...
I can get it activated in it's current state (olipro-2.40, radio 3.39.10, DCD 3.1.2)
Click to expand...
Click to collapse
But did you or did you not load the verizon carrier cab after the ROM?
ebb said:
But did you or did you not load the verizon carrier cab after the ROM?
Click to expand...
Click to collapse
I did.
After installing carrier .cab:
On Phone #1, after a hard-reset with DCD3.1.2 still on there, *228 (option 1, then option 2 later) gets me voice/txt, but no data - will need DMUreset/Akey. I'm confident I can get that part working with some more time/effort.
On Phone #2 (which is the replacement sent for Phone #1), *228 (option 1) gets me a referral to customer service, not suprisingly.
I fully expect this to reverse once I activate #2 in place of #1.
What I'm gathering from DCD's reply is that both phones are probably fine, physically. Regardless, I need to get #1 back to VZW before they ding me another stack of cash I don't have
That said, I'll have #2 a bit longer before I'm committed locked in (i.e. the grace period on returning it us up).
1. I just think then that going to a 3.xx.xx radio wiped your Akey out, and you need to call and get it re-provisioned. Just tell the tech you had to hard reset from a software conflict, and they'll do it.
2. DCD, I had to restart visualgpsce a couple of times to work at all- on the third try, it asked me what comm port, and after setting it at comm port 4, I get immediate lock (like as soon as I click "accept" on the first screen).
ebb said:
2. DCD, I had to restart visualgpsce a couple of times to work at all- on the third try, it asked me what comm port, and after setting it at comm port 4, I get immediate lock (like as soon as I click "accept" on the first screen).
Click to expand...
Click to collapse
OK, so... to date, I haven't gotten to activating phone #2... BUT...
I took it outside (my Mogul works fine inside here, but OK, I'll play along ) and fired up VisualGPSce... It took a while (I sat around for about 15 minutes) and it eventually worked it's way up to seeing 10 birds and using 6 - but NEVER locked on... and it wasn't very reliable... went up and down between seeing 10 and 0, and never "used" more than 6. Again, it never got a "fix"
(Yes, I also installed QuickGPS and updated it using ActiveSync connection.)
As I've said, carrier .cab is installed, tho the device is not activated so there's no data/voice service.
Inside (again, where my Mogul works just fine), the thing is useless for GPS...
Not sure if that helps, but there it is.
dont knwo if this is related but you messed up when using spl-1.20-olipro. the dcd thread cleary states "Hard-SPL 2.40-olipro is REQUIRED.
A device with SPL 1.20-olipro will constantly reboot with this rom!"
newone757 said:
dont knwo if this is related but you messed up when using spl-1.20-olipro. the dcd thread cleary states "Hard-SPL 2.40-olipro is REQUIRED.
A device with SPL 1.20-olipro will constantly reboot with this rom!"
Click to expand...
Click to collapse
Thx - this was addressed above... I am, in fact, running olipro 2.40... I used olipro 1.20 to get the radio rom on, then subsequently upgraded.
NetworkPIMP said:
Thx - this was addressed above... I am, in fact, running olipro 2.40... I used olipro 1.20 to get the radio rom on, then subsequently upgraded.
Click to expand...
Click to collapse
check your pm's please, there are a few things i can walk you thru trying.
dcd1182 said:
check your pm's please, there are a few things i can walk you thru trying.
Click to expand...
Click to collapse
if there are some "suggestions" if you'd let me know some because i used the 3.49 radio and i felt like i took a step backwards as far as GPS. it would show 10 sats but would never lock no matter what i tried via info in the threads.
however i'm back to 3.35 and happy as can be!
it picks up and locks within 30 seconds
coffey_joshua said:
if there are some "suggestions" if you'd let me know some because i used the 3.49 radio and i felt like i took a step backwards as far as GPS. it would show 10 sats but would never lock no matter what i tried via info in the threads.
however i'm back to 3.35 and happy as can be!
it picks up and locks within 30 seconds
Click to expand...
Click to collapse
maybe you are onto something for users on vz (who have no agps info and possibly missing another parameter)
i have not paid close enough attention to the reports to tally up votes. can the difference in lock time be consistently reproduced?
Related
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...
THIS THREAD IS OUTDATED. aGPS SOLUTIONS NOW EXIST FOR ALMOST ALL CARRIERS.
VERIZON USERS SHOULD USE THIS LINK FOR NEW INSTRUCTIONS:
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
--------------------------------------------------------------------------
Below is a link to the "fix" we've been working on for the Titan GPS.
We've gotten mixed results with the testing thus far. Some who have NEVER been able to achieve a lock have gotten locks within 30 seconds. Some say they don't see any change.
I must reiterate though that this "fix" is not something that works wonders. It merely helps the current situation. People who have trouble getting an initial fix, people who don't see locks for 5-10 minutes, etc may see improvement with this. Since I've applied it, I've noticed consistent initial locks taking anywhere between 30-60 seconds on Verizon. I'm happy with that for now. If you apply the fix and don't see any improvement, it doesn't necessarily mean that it doesn't work, as others are seeing results. Unfortunately, we've been unable to determine why this happens.
You still have to use the same steps as you normally would for using the GPS. This does not negate the act of priming it or using a launcher. Do everything as you normally would after you apply the fix.
The Titan GPS, though functional, will NEVER be able to function like it does for Sprint customers. Until other carriers provide access to a PDE aGPS server, there will always be hardships for the customers. No amount of hacking, fixing, or upgrading can remedy this.
THIS FIX IS NOT INTENDED FOR SPRINT
THIS FIX WILL PERSIST THROUGH FLASHES OF ROM/RADIO.
USE AT YOUR OWN RISK - I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR DEVICE
http://wiki.xda-developers.com/index.php?pagename=TitanGpsFix
I successfully completed this procedure on Vista64 SP1 without issue.
Now I just need to go outside and see if I get a better fix!
Thanks GC for a great and simple tutorial.
MrTek said:
I successfully completed this procedure on Vista64 SP1 without issue.
Now I just need to go outside and see if I get a better fix!
Thanks GC for a great and simple tutorial.
Click to expand...
Click to collapse
if this is supposed to do what we Sprint users have, then you shouldn't even need to go outside . I wish you the best of luck.
im gonna try it on my xv6800 in a few.
backing up right now...
edit: just did it and WOW! on a cold boot, it connected to my exact position wiht 4 sats without even shifting. all in 38 seconds (timed it). by far the fastest ive ever gotten in my house. soft reset and went outside, and got an exact lock in 5 SECONDS! holy christ, gc you are the man.
Thanks!
GC, I will try this as soon as i get home from work and report results. God I can hardly work waiting to do this.
Problem
GC, trying the fix now. I've downloaded all of the required apps.
Just for reference, I'm using:
DCD 3.1.2 ROM w/ Radio 3.39, w/ provider: Verizon
I just tried:
Put the phone in DMR Mode by dialing ##3424 and pressing send, or dialing ##3424# (depends on carrier). ActiveSync will disconnect, and the PC should recognize the phone as an HTC USB Modem and will install the drivers.
Both options, whether ##3424 and hit the green phone button...or ##3424# failed to open DMR mode for me. All I receive are a response by Verizon indicating that The phone number either disconnected, is no longer in service. etc.
I'll look around for another option. (This is similar with trying to access the options by calling to change how often the radio toward is checked for calls...I had to go directly into Windows and click ePST )
Are you using a third party dialer? If so, **** can it.
Also, reinstall the verizon carrier cab.
Right
I used the fix for SPB Pocket Plus that would make the Dialer continually pop up by installing a similar dialer I downloaded. (fixes the problem).
Should I proceed to reinstall the Cab from Verizon, or entirely discontinue the process?
I'm glad I'm not the only one that is not content with the GPS mode...from a cold start, 10 minutes can be average.
Looks good.
Thanks for the easy tutorial, went smoothly and I think it is a bit better. Edit: I know it is better, I just connected inside work where I never could connect before.
I notice that using TomTom I always before had No GPS signal for about 10 seconds, then it would say waiting for a valid GPS signal for another 10 seconds to three minutes or so, sometimes not at all until reboot. When I did it after the update it said No GPS for about five seconds and went straight to "lost gps signal 4 seconds ago". The longest it took to connect was 10 seconds after five tries (longest was after pressing the power button while in the program then waking it up...go figure).
Will you be able to integrate these drivers into the new builds for DCD? Or will we need to do this as the drivers are released.
Just out of curiosity, I know these aren't Verizon drivers, what provider are they ripped from? Will this be something that will be possible to update as new drivers are released?
Sorry for all the questions, another solid release guys.
BTW - Is anyone using HTC GPS on their phones when they applied this fix? Does HTC GPS even have an impact?
I used the fix for SPB Pocket Plus that would make the Dialer continually pop up by installing a similar dialer I downloaded. (fixes the problem).
Should I proceed to reinstall the Cab from Verizon, or entirely discontinue the process?
I'm glad I'm not the only one that is not content with the GPS mode...from a cold start, 10 minutes can be average.
Click to expand...
Click to collapse
Whatever dialer or dialer fix you're using is preventing ## codes. You need to go back to the stock dialer you installed from the kitchen, then reinstall the carrier cab. After that, start over. (You don't have to reinstall the wmodem drivers or qpst)
Will we need to redo this process after a flash or hard reset, or do changes stick?
Ivan
Verizon 6900 Results
I performed the fix on my 6900 and it seemed to get locks quicker after a few soft resets. Not sure if it's placebo yet but will let it run for a few days.
I'm also seeing more sats locked. Not sure the why, but I was normally seeing 5-6 at my desk and I'm seeing 8 now.
thanks I may try this when a working PC comes back...
But what exactly does this change on the phone?
Also is it possible that settings from a Sprint phone (PDE and all) could be mirrored into QPST for a Verizon phone?
I did this fix before I flashed to 3.1.6. After flashing, I connected it to check, and all the boxes are still checked.
So I believe it survives a flash
Great Job guys! GPS is locking on in under 10s now it seems!
Doesn't seem to do much for me, the lock isn't any quicker. By, the way, to get into DMR mode without the keycodes look for DM-Router in the windows directory.
not much luck. still took almost 1.5 minutes. I'm not concerned but I'm going to check it again in a while just too see if i can get a faster lock later on tonight
Thanks for the work and continued support for this community
verizon 6800
thanks sooo much gc14 and dcd. you guys are great!
i was the one who started the original thread about this issue, and this fix has helped tremendously! it still took about ~1.5 minutes, but it was a bit cloudy and it was the first lock since upgrading to dcd 3.1.6.
awesome work though! i can't wait till verizon gets some gps servers up and running (i have a friend that works fro verizon and he swears that verizon is releasing their official rom soon, w/ gps enabled so i'd assume their launching some sort of gps server. who knows though, verizon makes lot of promises). we can only hope!
as of now, this fix works just fine for me, so thank you both very much!
GREAT!
Wow man this was an excellent fix for the gps.. when i used the HTC GPS tool, it took maybe minute or more to lock with GPSMODE=4, with this fix, it also took about a minute still.. So i changed GPSMODE back to 2 and did a softreset... wow, it locked like in 10 sec.. never before in my house it did that!! one up for this fix!
Rom: no2chem 5067 kitchen
radio: 3.39
Ever since the VZW Update released my GPS no longer works, (didn't Update my phone)
I used to get locks right away (8-10 satellites) when I was outside now I get ZERO.
I use GPS today and Google maps.
anyone have any explanation why it would suddendly stop working?
Running DCD 3.2.5 and 3.42.50
sorry man I have no idea. my device still gets locks but I always have to toggle location on settings. (go in and turn it to 911 only say ok till I am back to the main screen then go abck and turn it on and say ok till I am back at the main screen again) then soft reset. it takes me a while now to gets locks but I do get them (no2chem5066 with radio 3.42.50)
evanbriggs1 said:
Ever since the VZW Update released my GPS no longer works, (didn't Update my phone)
I used to get locks right away (8-10 satellites) when I was outside now I get ZERO.
I use GPS today and Google maps.
anyone have any explanation why it would suddendly stop working?
Running DCD 3.2.5 and 3.42.50
Click to expand...
Click to collapse
have you updated your phone via *228? llboredll spoke about how me might of found some issues when programing his phone after verizon released the software update.
I had some serous issues trying to get a fix yesterday but just now I walked out my basement and got 7 sats and lock within 15 secs or better. So I will have to chalk it up to some weird anomaly yesterday.
guys thanks for the quick response, ya il try resting my "location" setting and yes i did do a *228' 2 ealyer today trying to fix the issue, it didn't change my PRI.
ya the location reset didnt work im still dead
evanbriggs1 said:
ya the location reset didnt work im still dead
Click to expand...
Click to collapse
Try a GPS program that displays the NMEA messages like GeoScout. If you don't see any then your GPS is not turning on. So either flash the ROMs again or you have a back GPS possible.
I wish you guys would read the damn forums.
The OFFICIAL VZW update kills GPS for anything but VZW Navigator, got it?
scrawnyb said:
I wish you guys would read the damn forums.
The OFFICIAL VZW update kills GPS for anything but VZW Navigator, got it?
Click to expand...
Click to collapse
But he said in his original post that he didn't flash the VZW update.
scrawnyb said:
I wish you guys would read the damn forums.
The OFFICIAL VZW update kills GPS for anything but VZW Navigator, got it?
Click to expand...
Click to collapse
Read the first post, he didn't (repeat) didn't update his phone. His theory is that Verizon did something to the network to work only with the update such that us on Custom ROMs it will not work. Obviously that is not the case but that is what he was asking or theorizing about.
I think we all have read the forums on it and are tired of people updating their phones and then complaining on this forum that it screwed up their phone. I can only say "Do your homework before flashing anything" otherwise don't whine about what you have now.
so you think it may be more along the lines of software??
give me your top 3 pics and ill try them all out.
Thanks a lot, and yes I was theorizing it was a network issue not my phone its self. seeing if anyone else may have had a issue recently with it.
Fixed it, uninstalled GPS Today
Installed GPS Toggle, and got locks 30 secs after i turned it on, thanks for leading me in the right direction!
I even get locks in my Room witch did not happen before. so defiantly awesome!
Had this problem for a few months now, but wasn't a big deal - until one needs it.
I can view web pages with no problem. RSS is fine. SMS & emails are perfect.
But downloads get stuck.
Downloading a podcast in RSS fails. IE will sit on downloading forever. Opera (the version that comes with the x7501) will give me a "connection has been interrupted" message, which you can then resume. Resume it around 20 times, and you'll eventually get the file. Opera 9.5 gets stuck & sits there.
The new Youtubedownloader gets stuck downloading files also.
The cap seems to be around 180k. Small files under that work fine, but anything bigger gets stuck.
I did a hard reset last night (after a backup) - same problems.
AT&T support is not much help. If you tell them you're using the Advantage, they go with the "not supported line". So I told them I was using a Touch - but hit compatibility problems with their Media.net download attemps.
SO - just me? I can't imagine a hardware problem that could cause it, but AT&T swears that they don't block things.
it's not a hardware problem at all, i was also getting this problem. there can be a number of things affecting your device: it could be that they're working on the towers in your area. it can be a weather situation. the athena is registered as an edge device on ATT's network so you have to let them know that it's a 3G device and should update there settings accordingly.
i don't have that problem, i used to but not anymore. it was frustrating for me because downloading is a part of my daily device use, lol. i spent three days on the phone with them, when they finished i even had better signal strength. what you could also try is to flash another rom (different build than the one you want to use) then flash back. plus what radio are you using? for me i had less problems with 1.58
Sorry, I should have been more clear. I've had this device for at least a year now, probably more. For quite a while I had no problems downloading.
Around 6 months ago the problem started. I think I noticed it on my RSS reader first (and thought it was a bug in their software), but experiments showed it was the whole phone.
I figured AT&T did something to my settings or their network. But it didn't affect me much, so I ignored it.
Now, it's starting to bug the heck out of me.
(so it's not a weather or tower thing)
I didn't know that AT&T can register devices as Edge or 3G. When I connect, it does show HSPDA
When I'm connected to the Internet, I see "MEdia Net (3G)" or "HSPDA" - and if I'm indoors, sometimes "EDGE." Does that mean I'm set up correctly, or can the phone mis-report which network I'm on?
I've never flashed this thing since I've had it - never even looked at those threads - always thought they were more for people that had Windows Mobile 5 & were updating to 6 - or for those packages with lots of utilities built into the flash.
Lessee.. Device Info:
ROM: 2.19.453.4
Radio: 1.47.51.00
Guess I'll start with running a search for Radio 1.58 & see where I can download it and how to install it.
I assume since it's flashed, programs like SPB backup won't help if I have to roll back?
Just for others that may read this thread - I'm starting my reading about flashing with the following threads:
http://wiki.xda-developers.com/index.php?pagename=HTC_Athena
http://forum.xda-developers.com/showthread.php?t=429013
ok, make sure you unlock your phone first before you try to flash anything. I'm using bootloader 1.2, and radio 1.58.
yes, on your phone it's registered as 3G but on their network it's registered as an edge device. you'll still get good speed but sometimes it can cause problems.
at work i used to have 2 bars on edge and nothing better unless i go beside a door or window. but now i have 2bars 3G and I'm not close to the window.
i would say your radio is at fault, so when you unlock, try a newer radio and see if it helps.
rom flashing is not just for people with older OS, but people who want the most out of their phone. the cooks here gives you more free space and free memory, they remove the operator's junk, the put in their tweaks and other things which gives you a faster device. their roms will make you feel like the first time you got your phone and was just playing with it none stop. they breathe new life in these devices, trust me. lol no joke.
if you decide to try a cooked rom just make sure you read up and follow the instructions properly. happy flashing.
to tell you the truth, i do believe it's your radio, maybe they updated their towers in your area which is causing problems with your older radio. i don't know but that seems to be a good explanation.
Did a lot of reading this morning.
I ran the AthenaUnlocker (step 1 only) - no problems.
I then ran the Athena-Radio 1.58 - which ran fine, but device won't boot (black screen only with glowing green power).
Trying to re-do the 1.58 again to see if I get luckier - if not, I'll try the 1.57.. and if not that I'll have to download an original rom and hope I can get something going!
(right now my faith in the different ROM's isn't too high)
Which one are you running?
No luck on retry. 1.57 radio extracts to something very different then 1.58. Can't find the link to 1.50 yet either.
Trying ROM: "RUU_Athena_HTC_US_2.19.453.4_105_1.47.51.00_Ship.exe" now to see if I can get back to where I started.
(I assume the 1.47 at the end of the file means I will get back to the original radio)
I didn't use the AthenaWrapper anywhere in there - was I supposed to do that?
Many of the posts in the upgrade section kind of assume that a newer person has already read every single threat in the forum. I see lots of posts from confused people & lots of rude "search the forum" type of responses.
Wiki could use some help also - kind of a ..
If you own a US x7501, run the unlocker from this thread (link), then do this (link) etc, then do the radio (this link). If you get a black screen, follow these steps..etc.
had you unlocked your phone?
One last thing for now - reading the 1.58 radio, I don't see where the hard-spl is done by anyone yet. Reading over some of the spl posts to see if want to start over with one of those (like 1.2 for example) and then try the radio.
But I think I'll wait to hear which spl you're on first.
lennie said:
had you unlocked your phone?
Click to expand...
Click to collapse
He said he did steps 1 only lennie. If I recall correctly you need to do steps two and three for the radio to unlock. He might need to do all three steps as step one's for CID unlock. {I THINK}
Do ALL the unlock steps, then retry radio 1.58. As you've probably seen from my many posts on this subject, 1.58 is a must-flash for the best network speeds. Personally I think 1.57 had better bluetooth sound quality, but either is far better than the stock 1.47. And the speed gains in 1.58 make the slightly worse sound quality a non-issue.
It's already an unlocked phone (sim), so in theory 2 & 3 were not needed.
Now that I was able to do a restore from ROM back to working order (and testing doing a restore on SBP backup - so I'm good now) - I might risk trying it again when I have a little more info.
Based of what I read, steps 2 & 3 should not be necessary... but should not hurt either. So I will probably try that.
I also have a complete 1.57 radio now to try, and I think I found 1.50 also.
The 1.57 thread seems to think that you don't even need to unlock the phone at all.
Main questions - does radio 1.58 work with the Hard SPL? If not, which SPL (preferably with link) are people using? Do I need the Wrapper at all?
Edit - going to do the 3 steps & try 1.58 now.
--
Steps 1 & 2 done, doing step 3 now. Question - if this works, and if the 1.58 radio works ... can I still restore from my SPB backup, or do I need to re-install everything from scratch.
---
Finished the radio 1.58 patch... and it looks like it's booting (no black screen). I peeked at the Device Info after step 3 and before 1.58 - looks like the same ROM, but radio 1.50.
It's up and doing the Customization stuff now. I'm thinking about installing SPB Backup & doing a backup before the restore just in case. Not to mention, even if I can restore my good backup, now would be the idea time to clean up & re-install everything from scratch.
---
Well, well - ROM is still 2.19.453.4, and Radio is now 1.59.00.00 - excellent! Will update again shortly.
---
Welp, backup up the phone & ran the Opera Browser and tried to download a 30 meg podcast......and got the same old "Connection was Interrupted message" - or a lot of work for no end result on flashes
Go the same 1.18 megs (I think I put k in the earlier message) - so no difference. Going to try to restore my backup now.
BTW, my backup before I started was 60.8 megs (!). The clean one is only 8.24 megs. I gotta see what's taking up all that space!
lennie said:
the athena is registered as an edge device on ATT's network so you have to let them know that it's a 3G device and should update there settings accordingly.
Click to expand...
Click to collapse
Following up on this idea - AT&T has me registered as an 'unknown' but now have me as a 3G device. They looked up the model to decide what to put me on. Rep said wouldn't cause my problems, (it would just affect speed), but nice to have it correct.
(testing now...... seems to be on Edge. I just went outside, rebooted - still Edge. Guess I'm calling them back now!)
Back home - phone is now correctly showing HSPDA!
..and I'm happy to say, I was able to download a 25 meg file on the way!
Could be the combo, but I think it was lennie's simple suggestion of making sure that they had me registered me as a 3G device!
Thanks lennie!
----
Next morning - problem is back, even after a reboot. Will call AT&T shortly & see if the setting somehow changed back
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.