Related
Hi everyone,
This is my first post, I'm an IT consultant, but by no means a phone expert! I have been upgrading my HTC Universal fine over the last year, and would consider myself a beginner (especially in contrast to you guys!)
I upgraded ro Radio 1.18 and the Ultimate WM5 posted a few days ago. Really good results, and great work - however the actual phone component keeps breaking, and I have to HARD reset.
The phone screen opens fine, and when you try to make a call, it freezes that screen, although you can still return to the Today screen. I'm unable to bring back the phone screen until a soft reset - and then it all starts again.... until I finally hard reset and then I can make calls again.
I'm not going to load any software today, to see if it happens again whilst "clean", but all I had put on was voice command, and a few SPB tools and tomtom yesterday.
So I'll let you know if it goes bad again later, but I thought I'd let you know in case this issue is already raised elsewhere and the search didnt bring it up. To be honest, its not an easy problem to hunt an answer for, as the symptoms are quite generic and broad.
Thanks very much for whatever you can suggest in the meantime,
Kind regards,
Mike
Orange M5000 on O2
Hi again, phone still working ok after 9 hours - and have only done the following do far:
Activesync setup to exchange, and push activated
O2 modem gprs connection created
Dare I do anything else, before I bust it!
Cheers,
Mike
1) My opinion, it seams radio ROM 1.18 has some issues
2) Even any other Radio ROM I would suggest you to keep the phone Band in Manual (GSM or 3G). Keeping the Radio Band in "auto" and by low level signal leads that the Device keep surching for better signal and that cause the device to freeze.
The symptoms you describe sound familiair.
Only I have had the same problems with WM6 and any radio rom.
The radio always seems to get stuck, and after a couple of disabling/enabling the phone the radio really gets stuck and I can't connect to the internet anymore.
I then have to soft-reset the device once, but it usually hangs or crashes, a couple of soft-resets are needed to 'reboot' the radio rom or something.
This was with the first build WM6 roms and radio 1.15 Darkforce/Pdaviet
I don't have this problem now using the cooked WM6 roms using the second build WM6 core (new build) and radio 1.15 or 1.18
Having the same issue radio 1.18 and KDS's WM5 ultimate so just gone back to WM6 from PDA viet that I was running with no problems.
Psi
Thanks Mike for bringing up the issue.
My V1640 (Voda Uni) exhibits similar problems: phone dialer freezes & unable to exit the screen. Going back to today screen by pressing hangup button or using today start menu works fine but unable to bring back the dialer screen unless by soft reset.
Unfortunately, I can't isolate the problem yet to either the Radio Version or the OS ROM version or the Device. The freeze/hang problem appeared in WM6: L26 V7 & PDAViet 2.10.11 as well as in WM5: Js 1.90.96 & KDS Ultimate Edition using V 1.15 & 1.18 in all the above. Tried Darkforce WM6 2.10.02 last night with 1.15 radio rom & the freeze issue came up once already.
I think this is a program/app compatibility issue & now trying to find out the culprit but nevertheless would try to downgrade radio down to 1.11 & will report back any progress.
Cheers.
radio downgrade
Hello everybody! I would downgrade my Radio version, where can i find the necessary files? Which one do you suggest me? I have a qtek 9000 running wm6 2Things version.
thank you!
Hi All,
I am also running a Voda Uni upgraded last month to WM6 with Radio 1.18.00. Since then I have a problem -- I do not know if is related to the thread or not but I thought I would describe it since it relates to GSM 1.18 and GSM crashing.
When power gets low (30-50%) and I attempt a to make a call (or, more often, when I use GPRS) I get a pop-up dialog box that says "GSM Radio Crashed. Reboot in 30 seconds." The phone then kills itself and attempts to reboot. It dies completely midway through the boot. All is well again when I switch to a new battery --at least until the power gets low.
shrines said:
Hi All,
I am also running a Voda Uni upgraded last month to WM6 with Radio 1.18.00. Since then I have a problem -- I do not know if is related to the thread or not but I thought I would describe it since it relates to GSM 1.18 and GSM crashing.
When power gets low (30-50%) and I attempt a to make a call (or, more often, when I use GPRS) I get a pop-up dialog box that says "GSM Radio Crashed. Reboot in 30 seconds." The phone then kills itself and attempts to reboot. It dies completely midway through the boot. All is well again when I switch to a new battery --at least until the power gets low.
Click to expand...
Click to collapse
Have the same problem. I have been using thingonasprings WM6 for a month with radio version 1.15. And the last week when I try to make a call I get that dialog box "GSM Radio Crashed etc" I havent noticed if its only when battery is low (think its always low these days thoug I just bought a new one a few month ago)
Hello,
I have a strange problem with my HTC Artemis (O2 XDA branded, bought in Germany, no lock)
It behaves unstable and indeterministic.
Unstable means that it crashes/stucks or turns off.
Indeterministic means that it happens when i plugg it to charger, when i'm syncing, when a phone rings, when using applications/tomtom or just i arrive to work and i find the device off.
When it crashes or i find it off, the biggest problem is to boot the device. It takes me typically 10mins, when i'm always trying to press the power button, push the reset button or unplugg the battery for a while in random order until i bring it to work.
After first crach, the device also often crashes or stucks again during the boot process.
Once, the device was so dead, that it took me two days to bring it into bootloader mode and then i could at least flash the ROM.
All these was happening with ARTEMIS TOUCH 4.01 WWE - LITE NO CUBE.
Yesterday, i switched to ARTEMIS TOUCH 4.02 WWE - LITE NO CUBE (burned FW twice) without installing any other applications and the problems are still here
My personal feeling is that it is getting every week worser.
When i bought the device (eBay), there was original FW with Win Mobile 5 on it, i immediately flashed to ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device. So i flashed to 4.01 and this issue was away, but approx 2months ago, the above described behaviour has started and nowdays i'm fighting with it 2-3x a day.
so, can anybody help?
GiZMo
Similar here
I have a similar problem, what's really strange to me is, that as far as i can recall it started happening 2 months ago or so also!! weird huh...
my device simply reboots from time to time! even while i'm making a call.
the weird thing about these reboots is that when it comes back to live i do not have to enter my pin to enable the phone! everytime i perform a manual reboot (by software, using the pin or remove battery) i have to insert my pin to able to make a call...
i have upgraded from 3.01 full touch to 4.02 full touch about the time it started, i have now 4.02 vanilla touch but problem still occurs from time to time.
any ideas?
Im another one to join this boat!
Bought an MDA C 3, two days ago, bought of someone from gumtree.com.
Worked fine for the first hour, and then locked up - nothing on the screen, no LED. Only way to get it going was to remove battery and then press power button.
I upgraded the ROM from the original t-mob UK WM5 to mechles fine release: http://forum.xda-developers.com/showthread.php?t=371182
The lock-ups / crashes have now become rarer, on average every 4 hours (before was every 1 hour).
There is no pattern to them either, although I have saw the screen trun all corrupted just before it happens. The last one was caused when I pressed the 'start' button.
I'm on a T-Mob contract, and lost my Kaiser, got ripped of when I tryed to replace it by a tosser on here for $375 Thief on the loose thread, and was hoping my luck had changed when I bought this one!!
It is T-mob branded and I wonder if there isn't a fix on here, would T-Mob repair it under warranty??
same "issue" with no entering of PIN after reboot. But not always
GiZMoSK said:
ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device.
Click to expand...
Click to collapse
here i found a good description of that issue:
"
Originally Posted by lasertony
I've got the same problem as !Novy, but nobody seems to have noticed his question. Are there any other guys out there with this strange problem ? I have been using this rom for a while and sometimes, without any visual warning the phone freezes up. This is particularly ennoying because there is no way to check wether it is working or not. Every other function or software keeps working ! The phone is just not receiving any calls or sms. So you can miss an entire day of calls and sms without knowing... Only when trying to call somebody the dialer says 'Dialing...' and nothing happens. No connection.
A soft reset is needed to get the phone working again.
"
btw, now i'm again trying to turn the device on, it's again stuck. grrr
Hello,
i had a few weeks ago a similar strange behaviour.
After changing the sd-card I had problems to turn the device on. After a hard reset it began to boot but hang.
The I flashed back to original O2 ROM. Then I had a unpredictable behaviour. Somtimes no sound. Sometimes I cound not be called. Sometimes Error message "no sim card". After every reset i had an other error.
Hard reset and flashing was no solution. Removing battery for less than 4 hours has no effect.
Then I wanted to send it back for repair. I took of the battery. The next day I wanted to try a last time and surprise: The device works fine without an error. Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
regards
Andre
It is Happening to my device too!!
It stucks every 2-3 hours!Tried many of the cooked ROMs but nothing.Also tried all the radio roms for 1-2 days.still the same!
It stucks with no particular reason.SOmetimes in s2u2 sometimes when am receiving a call.... etc.
Had the pin problem too for 3-4 times!
I will try your sugestion ANDRE and we will see!
Also i will try flashing the original rom,cid unlock and then flash the cood rom twice!
Fingers crosed....
Andre1210 said:
Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
Click to expand...
Click to collapse
didn't help
happy u
now, i will try to flash back original german o2 rom
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
bricked or not?
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Vinnie1 said:
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
Click to expand...
Click to collapse
I thought it was a battery problem too, but I've 2 batteries and both are died in the same time? I think it's too strange...
My P3300 have this problem from when it is returned from assistence and with original firmware (without other applications).
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
GiZMoSK said:
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Click to expand...
Click to collapse
jahrami said:
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Click to expand...
Click to collapse
but i cannot get into bootloader mode so no flashing from SD card or PC
bricked device
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
GiZMoSK said:
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
Click to expand...
Click to collapse
the good sign are the leds that means you have a very good chance...the guy made the piont...check the wiki
random crashes are often caused by hardware malfunction...sometimes the connection on the motherboard stuck,get broken or make a short-circuit...so check the hardware
Hi,
I Have a problem with my O2 orbit. The power but will stop responding when the device is locked in standby (power button pressed after locked), the lights on the top of the orbit will continue flashing but it wont turn back on.
I thought it was a curropt OS so i reflashed the original wm5 back onto the orbit and it seemed ok, so I then flashed the o2 release of wm6 onto it, and then started installing all my programs. Soon after this i locked it and put it into standby, about 20mins later i couldn't switch it back on. Thinking it may be one of my progrmas that has caused this I hard resetes but same thing happened again!
This is not the first time this has happened to me, 4 months after i first got the orbit (about this time last year) the same thing happened and O2 replaced it. Then in easter it happened again, O2 sent it off for repair and it came back apparently fixed. But here we are 8 months later with the same problem.
Has anybody else experienced this? Does anyone know a solution? Is it a problem with the software? Or maybe the firmware? Or is it a hardware problem and I am screwed?
Thanks in advanced if anyone can help!
Futher Developments
I have been experimenting on different roms with the problem, i loaded up Carty's Fastest WM6.1 rom, and the orbit worked. I slowly reinstalled the programs i had installed. The program seemed to work, then when S2U2 was installed it seemed to die again.
I previously flashed back to WM5 and then reupgraded back to WM6 and only installed the SDHC driver an hour later. Before this the device seemed ok, but then sometime after (not sure as it was in my pocket) it died again.
So I am unsure if it is a problem with hardware or if it is the S2U2 causing it, or the SDHC? or both?
Has anyone had any of these problems? I'd really like some help, I would hate to have to keep using my stone age nokia!
I GIVE UP!!!
Ok, the final verdict is that it must be a hardware issue. I have tried just running normal roms, and i get the same problems when no software is installed.
When i return home after new years i shall take into o2 and hope they can either fix or replace it for the 3rd time. Im still shocked that this has happened 3 times to me and it seems to of never happened to anyone else on this site, strange!
Oh well, it could be worse! Thanks, though no-one really helped, thanks just for the existence of such a brilliant site!!!!
My XDA Orbit went crazy today, first I couldn't start him at all, he wasn't react on "power button". After few attemts he finally started. I connected him to PC but he turned off after couple minutes. From this moment I can't start windows, it stops at starting screen (with IPL, SPL, GSM, OS). After a while screen starting to quakes (like a low frequency on CRT). I tried hard reset, it won't help and run it in bootloader mode but Orbit just reset.
Additonal info:
IPL 3.04.0001
SPL 3.04.0000
GSM 02.67.90
OS 3.4.0.0
ROM: Original WM6 from O2
Can anyone help me?
Have you tried a different barttery?
No, I didn't. I don't know anybody with artemis to borow another battery.
EDIT: I checked battery voltage, it's about 3,85V and now i noticed something, on battery sticker is printed it is for ARTE160 3.7VDC-1200mAh but on the phone it's printed ARTE200 5VDV-1A. Is that can cause the problem?
Finally I forced it to run in bootloader mode and flashed with the same O2 WM6 ROM. He started and I was abble to flash USPL and other ROM. It's better but still sometimes phone just poweroff with no reason
flisak said:
Finally I forced it to run in bootloader mode and flashed with the same O2 WM6 ROM. He started and I was abble to flash USPL and other ROM. It's better but still sometimes phone just poweroff with no reason
Click to expand...
Click to collapse
Hi
Had a similar problem!!! Try reflashing the rom....It worked for me..I used the o2 stock rom found on the the artemis wiki in the ftp section.... Can also highly recommend the Touch rom found in the windows mobile 6 section of the artemis section here..
regards
Lohtse
I bought a new battery but phone still turning off and freezes. Now I can't even turn it on, sometimes it starts but screen slowly fades away and after few seconds its only black screen with black light. It's propably a hardware problem but what?
EDIT: I started it, working fine when it's connected with pc but when I disconnect it freezes after couple of minutes.
flisak
open the device and check the screen is connected propperly, piss easy, just be very carefull.
if this does not work buy a new LCD.
Hi, I have the same problem with my Artemis, did anyone find a solution? Can be a problem with the LCD?
And plus one here. The device always turn off, and is difficult to turn on again. Rplaced battery and is the same.....
I've got an XDA Orbit that periodically hangs (full black screen and occasionally this seems to drain the battery very quickly). I've taken it apart and reseated the connectors and these all look ok.
Seems to happen when you're taking it out of a pocket to answer a call etc. Sometime it just requires a soft-reset but occasionally it just doesn't respond. In these instances I have found that twisting it slightly across the diagonal (top left to bottom right bending back slightly) and then resetting the device seems to bring it back to life and it's ok for a few hour/days again. If I leave it alone, i.e. not in my jeans pocket - it's fine, so think it's hardware related but not sure which bit is faulty - screen, touch-screen, mainboard etc.
If I bend it the same as above when it's working the screen goes screwy and causes it to crash so think it's definitely this is what's causing the device to crash. However, the clock seems to keep going (I'm assuming so as in most incidents it doesn't seem to lose the correct time - although I might just be seeing the problem the instant after it has crashed) so don't know whether the mainboard is still ok.
Just thought it might help some if you try the slight twisting described above to see if that helps with these to get them working and if anyone has any ideas how I can work out which bit of mine is faulty I'd be grateful.
when I try to flash the ROM 6.5 for my HP3300 after 4% flashing it restrats again. Pls help me out. I think this problem might be with my Ext_ROM. How to unlok EXT_ ROM
what is the best touch rom to use for my xda orbit. and where can i get it
lohtse said:
Hi
Had a similar problem!!! Try reflashing the rom....It worked for me..I used the o2 stock rom found on the the artemis wiki in the ftp section.... Can also highly recommend the Touch rom found in the windows mobile 6 section of the artemis section here..
regards
Lohtse
Click to expand...
Click to collapse
what is the best touch rom to use for my xda orbit. and where can i get it
Well it seems that I'm having similar issues with my Orbit.
I've been having problems with it for a few weeks and they seem to be getting much worse now.
Occasionally it would just lock up and freeze, but after frantic tapping it will unfreeze itself and continue working fine. But over the past few days it's been locking up regulary. Removing the battery was the only way to get it going again.
But now it just won't do anytihing. As soon as I start it up I either get a white screen (it phases in during the splash screen), or it'll start up, freezes after a few seconds, then eventually switches itself off. Hard resetting it makes no difference at all. Changing the battery didn't work either. I always keep it on charge overnight, could that be the problem? Maybe I'm just overcharging the battery (if that's even possible).
Note: As I've typed this, I've switched it on again only to find the battery's flat, even though it's been off for most of the day (I gave up trying to start it up). The battery usually lasts for the whole day - maybe even 2 days if I don't use it much. I had it on charge overnight as I said.
I'll try another battery to see if that works. If not then what can I do?
I have this new T-Mobile Touch Pro 2. I currently have the Stock European ROM (6.5) on it. Before that, I was using the TMO 6.5 version. My problem is that the phone randomly freezes/dies/turns itself off while sitting idle. And every time it happens, I either have to soft reset it or take the battery out and put it back in to turn it back on. Simply pressing the power button doesn't do anything. Funny thing is that this phone is a replacement that was sent to me by T-Mobile because my first device was doing the same thing (which I had for about a month). T-Mobile tech support was just as lost as me. Can anyone here help me?
I have the exact same problem! Have you found a solution or at least learned the cause of the problem ?
Phone turns off ramdomly
Hi
I have the same problem the phone is shutting down ramdomly without any warning and i have to use the power button to turn it on again
any solution guys ??
Did you task29 the rhodium before flashing the new rom?
Sometimes flashing the new rom doesn't clear the memory properly leaving traces of old files to foul up the operation. Flashing task29 before flashing a new rom will stop this.
After you flash task29 there will be NO os on the rhodium. You will need to pull the battery, Put it into bootloader and then flash new rom from PC or use sd card method.
Cheers...
I have exactly the same problem, 2-3 times a day, I need to soft reset it. The phone was working well until I moved from 6.1 (original) to 6.5; I believe the new radio has issues. Any recommendation, flashing the radio does not solve the problem.
I used to have 1-3 SODs a day. Now I have only one SOD a month. My solution was to remove compact framework 3.5 and that weathersolution where you can add new cities. By the way; I upgraded to WM 6.5. Before the upgrade I had no SODs.
Sorry to bring up an old topic, but I recently acquired a Touch Pro 2 (RHOD100, original HTC model) and having exact the same issue. There's no saying when it's happening, but always during an action. Had it when pressing the End key after a call, when pulling the Usb cable from the device, and during other things too.
Hardware seems fine, battery is firmly in place and contacts are fine, and clean.
Having factory WM 6.5 Rom on it. And like mentioned before, I also do have Compact Framework 3.5 installed since it's required by some of my software.
Anyone ever found a solution that's confirmed to solve the issue?
I'm sorry for bumping up an old thread but after doing a search this was the first one that was listed which isn't 'That old'. I have just bought one of these phones, brand new, from factory. It comes with windows 6.5 and runs the OS version for the phone is - 5.2.21887 (21887.5.0.86) The phone seems to randomly just shut off without notice and to be able to turn it back on again to use it, I've got to take the battery out and put it back in again, then it will be able to turn back on. When the phone does enter the state of completely turning itself off. I have noticed that my notification LED light does flash green, I don't know why it does this. But if anyone has some help for me to sort this problem out and enable me to use my phone perfectly then that would be great!
Yet again, sorry for bumping up an oldish thread