Related
Not quite sure what the issue is with this one. Back in the beginning of the year my XDA II fell from waist height when the carry case snap popped open (notebook bag brush across the front catching on the flap). The only noticeable problem after that was that the power button no longer works, so I have to power it on by pressing the phone or address book buttons etc.
About a month and a half after that incident the phone suddenly just stopped getting signal. I was using the standard shipping firmware with a few apps. Soft reset, hard reset both failed to fix the issue, the phone simply will not pick up the network. Interestingly enough if I play with the phone settings and go through the process of manually selecting a network the phone WILL pick up available networks in the area (this kills my idea that the GSM radio failed altogether). For now I've had to switch back to a junk phone as I've been unable to figure this one out. Anyone have any ideas on this one? I'm using T-Mobile for a service provider and I'm based out of California.
Also, does anyone know of a place that can do diagnostic/repairs here in the U.S.? So far my searches have come up empty.
Thanks in advance.
Give this a try:
Reflash the phone with any version of ROM and it should start working fine again. I think the problem is that you're radio firmware somehow got corrupt.
Ok, guess I'll have to give it a try. I've been avoiding trying the slightly riskier stuff as I got this thing via an independant third party, so warranty/support are iffy.
Is there a general release ROM that I should be looking for (using T-Mo in U.S.)? Or should I look to cooking my own (which I'd rather not)?
You can try upgrading the ROM with the same branded one. That shouldn't void the warranty.
I.e. If you've got an O2 device, get the new O2 ROM
Reflashing
I have had a simular problem with hard locking. Finally my phone quit working all together. I went into boot loader mode and flashed it. It's like having a new phone again. So yeah.. I think the ROM's can get corrupt.
Brandon
NeoCole: Looks like you are using T-Mo in the U.S. Mind if I asked what you flashed yours with? Did you use a specific ROM, Radio Stack version etc.?
I'm running an unlocked i-mate (contradictory to my subj title, I know).
Flash it with the T-mobile 1.72 ROM
ROM Version
Well.. I flashed it with the IMATE 1.72 ROM and used most of it's extended ROM. I used the battery Meeter from the Qtek extended rom. I built most of my extended ROM Myself.
I look at T-Mobile's Beta 1.72 ROM like I look at Windows ME. Both should have never happend. I can't count how many times I had a hard reset with the T-Mobile ROM. I'm not sure if it was a combination of the programs I was useing or not. I saw a post that said SBP was possibly causing the problem. So I quit using SBP products. Later I still had to HARD RESET from time to time. Now that I'm running differently, My device has never been so smooth.
Let me know if this helps,
Brandon
Looks like I'm pretty much screwed. Without a working power button I can't do a hard reset into bootloader mode. When I try using a utility app that allows me to do a hard reset I can't hold down the jog dial at the same time. Good times.
*edit: yeah, that would be 'can't' hold down the jog dial.
You don't need to boot into the bootload to perform an upgrade... the upgrade software takes care of everything for you (except the hard reset at the end)
All you need to do is sync through Activesync and then run the upgrade program.
I would (and have!) flash the imate 1.72 ROM. It is very stable for me and HAS improved the battery life of my imate.
As stated above, just start the flash process and it will put the device into bootloader mode and perform the flash. It will need a HR at the end, but since your power button is not working, maybe you could remove the battery, slide the red slide/switch back into place for a few seconds as if the battery were there, then slide it back, put in the battery, slide it back into place and press one of the puttons to turn it on.
Hey . . . it might just work!
imate 1.72 ROM did the trick. After I actually READ all the posts regarding the ROM I realized it came with an installer and got that done. So far so good. Now if I could only find my missing tomtom 3 cd key that went MIA during my last move
Hey, that's fabulous! Welcome back to the world of convergence.
Hey All
I'm on my 5th phone from Orange. The latest one arrived today. I've had one with screen alignment problems and 3 that after a month or so making a piecing noise when the display is on. Off the 4 I've had previously only one of them seemed to be stable. All sorts of hangs with frequent software resets. Also it always seems to try and use a 3G connection when it has wireless. If you soft reset and try again it doesn't use the 3G and will use wireless. This is without installing any custom software but using a memory card. Had one that wouldn't always sync with XP and when I went to Vista refused to work. Just seems like hardware/software is poor quality
Driving me mad/nuts. Any suggestions. Orange has offered to swap to a different phone but I can't live without the functionality. I don’t hold much hope for my latest one either.
Anyone have any ideas when Orange is releasing new firmware?
HTC were due to distribute a new european ROM at the end of January, but not sign yet. This would then be customised by the network providers orange Tmobile etc.
You can always upgrade your ROM with the latest from HTC (1.35), which i have done on my M3100 with no ill effects. Since the upgrade it seems to run a bit quicker, plus you do not get all the orange branding on it. Have a look at the WIKI page for full instructions.
I've thought long and hard about doing that. However Orange has said if I did this and have another fault with a phone they won't replace it. I would have to claim under insurance. Bearing in mind I'm on my 5th phone I think this would be a problem. Most of the reasons why I've had my phone replaced are hardware issues (piercing noises with display on, no sync, screen alignment) Because I can't go back to an orange Rom I’d be a bit stuck. (How close is the Orange Romanian Rom to the UK Orange original Rom?)
Don’t get me wrong the software is buggy but I can live with it (just). I wondered if a Rom would also help with some of the hardware glitches to....
bobgfish said:
I've thought long and hard about doing that. However Orange has said if I did this and have another fault with a phone they won't replace it. I would have to claim under insurance. Bearing in mind I'm on my 5th phone I think this would be a problem. Most of the reasons why I've had my phone replaced are hardware issues (piercing noises with display on, no sync, screen alignment) Because I can't go back to an orange Rom I’d be a bit stuck. (How close is the Orange Romanian Rom to the UK Orange original Rom?)
Don’t get me wrong the software is buggy but I can live with it (just). I wondered if a Rom would also help with some of the hardware glitches to....
Click to expand...
Click to collapse
I'm like you. I daren't change the rom until there is an orange rom available to revert to.
Actually my device is stable and works well, but then I do a lot of housekeeping to avoid unecessarily stressing the device (including regular resets).
I too have an Orange UK M3100, in the first month I had 3 replacements: screen alignment x2, faulty camera. Since I got my 4th unit I have had no problems, I have a fair amount of software running on it, as the above post I regularly tidy it up but only reset it about 2-3 times per week. I understand how frustrating it is, I cursed my impatience for not waiting for the p990's release as I had a p900 and p910 but now I absolutely love the M3100 and am so glad I stuck with it, especially seeing all the problems my mates are having with their p990s.
For what it's worth, if Orange are prepared to replace it again without using your Orange Care insurance, I'd try again, cross your fingers and hope that you get a bug-free unit. Tell Orange you want a brand new replacement and not a refurb.
However, I doubt Orange will release a ROM update for some time, if at all.
i never ever have any problem on my m3100 from orange uk
using outlook msn skype and balaa balaa with my wilress internet
not even 1 fone
we got update from orange 2 fones
just now upgrading rom 1,23 to 1,24
br
@Usman GSMWORKSHOP 01618343351
I also belong a M3100. At first I lost plenty of my hair figuring how to get it working at least correctly. Now it is allmost perfect!
I tested plenty of roms; and at last my favorite is the Orange Romania; it is at least as fast as the SA 1.35 and seems more stable. Standby recovery with wifi is faster, bluetooth detection *seems* more stable, dialer skin match the vista theme, wifi *handshake* improved (I had to disable/enable the wifi more often with the SA rom to get it connected to my home network).
So, if I were you I would stick on the orange ROM. The only reason I changed my rom is that I really wanted an english one; localised versions get me sick.
What I did to get my phone working:
-Changed the default case (and its awfull magnet) to another one magnet free (it solved my "auto answer" issue)
-I managed to install only the software I need:
-SPB Pocketplus
-SPB GPS Mon
-MSN for WM2002-2003 (far faster/stable than the WM5 one!)
-TCPM
-HTC X-Button
@uhk: I would be very interested in your rom update; where can I find it? I found nothing on orange's site
do u have a link or smthng for the msn messenger?
I'm having a wierd problem with my Hermes. I have the Scnaps 4.01 WM6 rom on my phone right now, but the same thing happened with Blacks rom when i was running that.
Sometimes when i turn it on, it says it has signal so i try to make a call i get operation failed, and then you see the signal drop back to searching, it finds the network and then logs back on. Same thing happens even if i dont make a call, turn on the hermes, and look at it, has signal, then 10 seconds or so later it drops to searching (it never really had signal) then logs back on, and then sms's get delivered. I've also had people try to call me during this time and it's like the phone is off.
I've tried a few different radio versions recently but same behavior with all of them. 1.54.30, 1.54.07 and currently on 1.43.
Something else weird is the fact that it seems like (I could be wrong) this only happens after having the rom on for a week or so, ie after flashing a rom, the first week or so i don't get the issue, then it slowly starts to happen - this could just be my imagination.
Has anyone else had this issue? Any ideas/suggestions welcome, thanks
Hi Ferni...
This is something that is becoming quite an issue recently
Firstly, have you made sure the SIM contacts are nice and clean and everything is fitted OK - and have you tried a different rom image? If not - try these first.
Secondly, where abouts in the world are you and what network are you on?
Thirdly - when did you install 1.54.30 and 1.54.07 - did your problems start before or after you flashed a 1.54x radio - and what radio were you running before trying these.
Finally - What other information do you have about your device - is it a herm100,200 or 300, what IPL/SPL is it.
Sorry for the 100 questions, but I'm investigating these issues at the moment as a lot of users have had similar problems especially after using radio 1.54.x as this thread discusses.
Thanks for the reply. Just read the other thread you linked to (and the threads it linked to). Interesting to know i'm not the only one.
I just pulled the sim out and gave it a rub and the contacts and put it back in. I also had a bigger battery in it, so i removed that and put the standard one back in. See if that makes a difference.
I used to run the black rom, now I run the schaps one, trying to avoid flashing it again just a pain to resetup everything you know....
I'm in Australia, on the Optus network. The JasJam is actually only sold by Telstra here, but i got one 2nd hand and use it on the optus network fine (Optus sell the Dopod). The latest radio rom 1.54.30.10 i belive is actually from Telstra - in the offical WM6 rom from them for the JasJam.
As for when i flashed which rom and when the problems started happening - i can't really say sorry, i didn't keep track. I've had the phone around 6 months, flashed it with a cooked WM6 rom (black i think) when i first got it, i probably updated the radio as well.
How do i tell if it's a 100, 200 or 300? Also not sure what SPL it is, HardSPL or something?
Tempted to flash it to the official telstra rom released recently with the latest radio, so if it does die completely i can send it back for warrenty. What do you think?
Thanks for the info - every little helps at the moment!
Firstly, yes - the radio you're running is native to the area and network and so if you're running 1.54.30.10 and it goes duff you should be covered by your warranty so don't worry. Also, it's not certain yet that there is definitely a problem with this radio so don't loose too much sleep. (Most of the problems linked with this radio that I've researched so far seem to be coming from Europe and after rolling back).
As for flashing with the official ROM, that's a decision for you - however in the cases of sudden GSM death, the phone will still boot to Windows and it is still possible to flash the OS and bootloader roms (just not the radio) so if it did go bad with an unofficial ROM on it you should still be able to roll it back - again sleep easy ;-).
As for the problem - the steps you've taken are a good start, see how it goes and keep us informed here.
It may be worth also trying to manually set your band (if applicable on your network). Sometimes problems like this can be caused by issues on the network itself and trying an alternative (maybe a friends) SIM card for a different network or even manually switching the phone to GSM (if available) can "cure" a problem (although it's a pain if you specifically need to use 3G and it's data speeds!).
Finally - to see your full device information you need to enter the "bootloader" (tricolour) screen. Hang on to this information on the bootloader screen as it can be useful if you ever encounter a bad flash.
To do this, hold the OK button on the left of your phone and the power button on the right then press the little reset button with your stylus. You will then see the model at the top with the IPL version below it and then the SPL version below that. To get out of the tricolour screen, press the reset button again. Needless to say this won't erase anything or damage your device but make sure you close your apps and save your data first
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
ferni said:
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Click to expand...
Click to collapse
What radio are you currently running? Thought it was 1.54.30.10 or did you change that the other day when trying a new ROM?
ferni said:
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
Click to expand...
Click to collapse
*IF* this is the sudden GSM death syndrome then it will progressively get worse unfortunately - but it might not be that (think positive!)
[edit : removed - brainfart you answered my question] Incidentally, just updated this thread here - Look at post #60, it's a long post but there is a couple of possible things for you to try there (multiple flashing on a "chilled" phone) for users who STILL have some GSM connectivity... Might be worth a go and certainly could do no more harm... The post itself is very technical but just follow the instructions about 3/4 way through the post and ask any questions back here in this thread so things don't get too confused!
In terms of flashing your ROM - when you _really_ feel the phone may die _very very soon_ then it's worth considering flashing it with the latest OFFICIAL rom from your provider while you are able to do a full flash but don't leave it until DHL are at your door to collect it just in case you need some help!
Oh yeah... and finally for tonights post - Rolling back from Olipros Hard SPL... back to the normal, official SPL - Mr Vanx has written a fantastic guide to this here complete with illustrations - That should save you some searching
The SPL rollback, of course, should be the very last thing to do before shipping it back under warranty of course tho - just incase you need it in the mean time!
Good luck - and keep us updated - particularly if all works again (or not)forum.xda-developers.com/showthread.php?t=299070&page=32
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
ferni said:
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
Click to expand...
Click to collapse
Yes. Crazy as it sounds, if the previous radio caused "logical" bad blocks - a combination of a couple of flashes in quick succession with the PLA at a cooler temperature might recover them! (temperature issue came from the data sheet for the chip itself - Apparently more efficient writing at temperatures a minimum of 10C below ambient).
Good luck - let us know how it goes... I've got my fingers crossed you'll have a Hermes with it's wings back shortly
Last night the phone got worse, i had a missed call, tried to turn the unit on to see who it was and it wouldn't turn on, so i soft reset it, it booted up ok, but wouldn't pick up a signal.. eventually after about 5mins it did, but then it locked up. So i pulled my sim card out put it into an old phone which i'm using for now.
This morning came into work and put it in the fridge for 15mins, and flashed the latest radio firmware on it. Then flashed the latest official telstra rom onto it (getting ready for warrenty). That's just finished, only step left is to put the original boot loader back on. May test it again for a couple of days to see if i can get it to do the same thing on the offical rom/radio before i send it back. Will let you know.
Thanks for your help so far.
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
ferni said:
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
Click to expand...
Click to collapse
We did indeed - Ah well, at least you're covered by warranty
Mr Vanx has written a fantastic guide to rolling your bootloader back - complete with illustrations. (repeated for others who've just started reading this thread)
Yeah hopefully it gets covered under warrenty. That bootloader guide worked perfect
For anyone who cares, they replaced my radio board under warranty - I now have a new IMEI number. Haven't got the phone back yet to test to see if it's fixed.
Did you ever upgraded the Radio ROM ?
Or was it always 1.43.
My first ROM only upgrade.
http://forum.xda-developers.com/showpost.php?p=1462158&postcount=292
Yeah i had tried a few different radio roms before this. I suspect it didn't like being flashed so many times.
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
gondalguru said:
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
Click to expand...
Click to collapse
I flashed one of the wm6.1 roms and ended up with 1.54.07 radio and was getting the "modem disconnected" error message everytime I tried to log on to the internet.
I reflashed the original WM6.0 ROM from AT&T and then reflashed my radio to 1.48 (can't go back to 1.16 because of the radio bootloader I think) and then tried to log on to the internet.
That didn't work
But then I made a phone call to my home phone
tried logging on and it worked.
Been working fine since
crossing my fingers and hoping I dodged the bullet, not gonna flash again til ATT comes out with 6.1 then if it acts up even a little I am gonna send it in for warranty repair.
I hope this procedure works for you mate.
pedro2k said:
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
Click to expand...
Click to collapse
Not exactly sure where this setting is, the closest thing I could find was to install HTweakC. And now I have auto attach off. I also live in WI rural area, and 3G has been growing. Coming closer my home, and when I go to work it switches to 3G from Edge and I believe this is the biggest cause of this problem. I will let everyone know if this has helped me or not.
Thanks pedro for your suggestion. I will try that and will report back.
Hi guys, I am new to the HTC world .
I bought a Vodafone branded HTC Magic two weeks ago, but I had problems almost immediately. In practice, my screen goes mad and acts as if I touch randomly on the lower part of the screen itself. In order to get it back to work properly I have to turn it off and then on again, sometimes more than one time. Do you think it is a screen defect or it has something to do with the ROM?
I have hard resetted it but nothing changes (the ROM is not cooked, it is just the Vodafone one).
Thanks
Hi,
evene if I didn't get answers, I bump this topic because, after I sent my Vodafone Magic to HTC and they gave me a new one, I have the same problem.
Someone says that this problem is caused by a software incompatiblility with the SIMs from the Wind Italian operator, but I also tried with another SIM and I got the same problem (even if minor than with Wind).
Is it possible that no one had this problem?
I tried ROMs, patches, kernels, but I had no luck.
Thanks in advance
Hey my bros having some major signal and crashing issues with his new HTC HD Mini.
He bought HTC HD Mini on o2 several months back and ever since getting it it was crashing every now and then (i knew htc n winmo were prone to this prior to him getting it).
It has now got worse and he is having to soft reset it by removing battery at least 20 times a day, sometimes it will crash, remove bat and start again and it crashes as soon as it restarts!
this has now got even worse and he is now no longer receiving network signal! ive tried everything, new sim card, factory reset, hard reset, tried upgrading the ROM via HTC website as they have a ROM upgrade there but no, wont let me install that because it is o2 branded phone i get an error message saying Error 294 Invalid Vendor! have to get the ROM from o2 direct as you probably already know but this hasnt been released yet or as far as i am aware!
Can i use CustomRUU to reinstall / upgrade radio ROM
Will CustomRUU or SSPL allow me to upgrade ROM and will this change anything?
Ive been using winmo for few years and i have advised him to come here to get advice. i had an old htc (cant remember which model he said now) that had same prob that did not get any signal and was told to get a radio upgrade or somethin, after that i got normal signal.
Also he read somewhere about downloading some program to edit a certain registry value from 2-1 or something on the official rom upgrade to allow the install of it on o2 branded phones.
What are his best options and are these common problems with the htc hd mini do u know??
Cheers
I had the crashing problem too. Although not as severe as yours. Around 4 to 5 times a day. Had to remove battery each time, to reset it. I immediately register a complain to the vendor on the 2nd day. Replacement unit was approved shortly. New unit doesn't crash anymore.
I suggest your best option is to request a replacement unit from vendor. As soon as you can.
Agreed- as you've tried all the usual remedies this is almost certainly a faulty phone or battery.
Get it swapped under warranty, and make sure you note the serial number of the phone and the battery as they have been known to simply send back the faulty ones!
Regarding your comment about HTC and WinMo being prone to this- that simply isn't true especially with devices ovr the last couple of years. Most faults and crashes are down to user interaction- installing unstable programs etc, or failing to make sure unused ones are terminated. One of the perils of a multi-tasking OS, and one which iOS4 users are now starting to see