Develop Bugs

indeterministical crashes

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

Artemis crashes - battery problem?

Hi,
My Artemis is running Meschle's Touch 4.02 WWE for a long time now.
A couple of months ago it started to crash, apparently randomly. It started after I installed auto-hibernate, but this could be a coincidence.
What happens most of the time is that the screen is turning black (fades away), starting from the bottom. Sometimes it just gets stuck on the home or other window or it soft resets automatically. I also got twice a white screen that said: 'reset due to sudden power loss'. Soft resets sometimes work, sometimes it gets stuck on the boot screen. I did several hard-resets with no luck.
I am trying for a long time to figure out a pattern. Maybe it has to do with the radio consuming too much power? Upgraded to 03.21.90: same problem.
Last two crashes happened while trying to start Opera mini.
After a crash the clock is wrong (the time of the crash the clock stopped).
It seems to happen more often while charging.
I've changed the battery: it seemed to be better for a while (two weeks) but then it started again.
I've disabled everything, leaving only the phone (no data, no HTC home, ....) but still the phone crashes from time to time (sometimes every hour, sometimes every 5 mins, .....).
Battery status indicates some weird things too: after charging up to i.e. 35% then soft reset batt status indicated 58%...or batt status is 30% then 2 mins later status is 2%. The OMAP function is turned off, because sometimes while booting the cpu is stuck on a very low frequency (screen flickering, very slow boot, ...).
I've tried to flash with another rom (original HTC) but I get: 'update utility not for this device' or something similar. I've tried several RUU's en always USPL.
Does any of this make sense to anyone? Any suggestions? Thanks in advance.

I have exactly the same problem. Think solved from 2 days. Changed the SD card i have 2 one 2 gigs and one 1 gigs the problem was with the 2 gigs card. Try to backup your data and format the card.

bobybravo said:
I have exactly the same problem. Think solved from 2 days. Changed the SD card i have 2 one 2 gigs and one 1 gigs the problem was with the 2 gigs card. Try to backup your data and format the card.
Click to expand...
Click to collapse
Thx, I'll try that. However, even when the sd card is removed the crashes occur.
Just had another crash....connected via usb to my pc: after 5 secs screen faded to black. I had to soft reset. After that some 'invisible window' was blocking the start menu. Closed it (via the close button top right) and got the start menu again. Re-connected to usb and is ok until now....
I also see 173mA of drain.

I had the same problem.............and i change back to the original swedish wm6 rom and it was better for a couple of days, then got worse started to freze fade out until one day it "died" now i can only get into bootloader but cant boot any roms not the original swedish rom (wm6) or any other rom, in boot loader it only says IPL 3.13.0001 SPL 3.13.0001 no gsm or other stuff but when conected to USB it says usb, I tried the SD flash to but no good so my sugestion it that u see to that ur device is "open spl" if it take the same route that mine did.
(i change to a brand new battery when the problem where starting but taht didnt help.....)
I guess now as i understand it my only hope is to find the original shiped rom wm 5 swedish rom?! and try if that will flash onto my device.
i hope u dont get the same problem as me.

Only problems, no solutions...
Mine (p3300; Black&Blue v5) got a new Battery, new SD-Card. Did´nt help. I removed the SD, removed SIM, loaded the battery, then turned it on again and from now on it´s sometimes booting, sometimes not. If it´s booted up (after long time lying with removed battery) it doesn´t live long enough to flash it with another (old) rom.
Now it´s lying next to me, with all this expensive accesoires, doesn´t talk to me and say what the problem is. My Provider called me and asked if I want a new one.
Again HTC? I love the functions of WM...

I have the same problem with my Dopod M700 (Love)
But mine doesn't freeze it just auto soft reset itself... i don't know whats going on... somebody please help.
Changing to different ROM doesn't solve the problems... put back the original factory ROM also doesn't help.

Here still the same problem.
I've upgraded the radio to 03.21.90: now WIFI isn't working anymore and the phone still 'crashes'. I'll change it to 03.18.90 and see what happens.
I've emptied the battery several times (until bootloader switches off) and recharged with the original AC adapter. Did a hard reset on battery 100%: problem remains.
There are several threads with the same problem. I didn't find an answer, exept maybe to replace the motherboard.
I really wonder if there's anyone who knows what is causing the problem.
It could be the graphics card (screen fading) or the battery/charge chip...no idea.
I've also noticed that when a crash occurs, it often takes some time until it boots again, as if the Artemis needs to 'cool down'.

System Crash
PeteNewt said:
Hi,
My Artemis is running Meschle's Touch 4.02 WWE for a long time now.
A couple of months ago it started to crash, apparently randomly. It started after I installed auto-hibernate, but this could be a coincidence.
What happens most of the time is that the screen is turning black (fades away), starting from the bottom. Sometimes it just gets stuck on the home or other window or it soft resets automatically. I also got twice a white screen that said: 'reset due to sudden power loss'. Soft resets sometimes work, sometimes it gets stuck on the boot screen. I did several hard-resets with no luck.
I am trying for a long time to figure out a pattern. Maybe it has to do with the radio consuming too much power? Upgraded to 03.21.90: same problem.
Last two crashes happened while trying to start Opera mini.
After a crash the clock is wrong (the time of the crash the clock stopped).
It seems to happen more often while charging.
I've changed the battery: it seemed to be better for a while (two weeks) but then it started again.
I've disabled everything, leaving only the phone (no data, no HTC home, ....) but still the phone crashes from time to time (sometimes every hour, sometimes every 5 mins, .....).
Battery status indicates some weird things too: after charging up to i.e. 35% then soft reset batt status indicated 58%...or batt status is 30% then 2 mins later status is 2%. The OMAP function is turned off, because sometimes while booting the cpu is stuck on a very low frequency (screen flickering, very slow boot, ...).
I've tried to flash with another rom (original HTC) but I get: 'update utility not for this device' or something similar. I've tried several RUU's en always USPL.
Does any of this make sense to anyone? Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
I'm having exactly the same problem which happened after I upgrade from Artemis love 32 to 33.
I have tried everything mentioned here, changed th Rom 5 times, went back to the Ship Rom, but the system keep on crashing.This is the second time this is happening to my Artemis. The solution at the first time was replacing the motherboard and nothing else, as it has worked fine after that.
I posted my problem in another thread here but no solution yet. Four days back and after I got enough with it, I took my Artemis to the HTC work shop and they told me that they couldn't find the reason for the crash, and the only way to solve the problem is to replace the motherboard which will cost me too much.

Strange it happens to several phones, and more or less in the same way.
I've changed my Rom to B&B 5.0 now. Still same problem.
Wifi isn't working at all anymore: tried several radio versions, none brings back the wifi. Is this the end of my Artemis?

Me 2
Jup it happened to mine too, I returned it to the shop and when they returned it they said that they had replaced something but they couldn't tell me what It worked for a couple of months but now the same problem so it's back at the shop again... (luckily i had 2 years of warranty) So i guess it's not really a software problem.

Maart84 said:
Jup it happened to mine too, I returned it to the shop and when they returned it they said that they had replaced something but they couldn't tell me what It worked for a couple of months but now the same problem so it's back at the shop again... (luckily i had 2 years of warranty) So i guess it's not really a software problem.
Click to expand...
Click to collapse
I hope u really try to get them to awnser what they change this time and then u can tell us? who knows it might help to know that.

So...installed B&B 5.0 (thx Tom ).
I did several complete 'battery charging cycles'.
I formatted my SDHC card.
It seems to me that it crashes less now (only once yesterday, not yet today).
Wifi seems to be definitly gone.
It probably isn't SW-related, but why would it crash less now than before?
I think that the most probable cause would be the chip that handles the battery status.
Let's hope that the chip somehow got resetted with the charging cycles.

No luck....it crashed all the time yesterday.
It seems that it happens more often when it is in my pocket (temperature related?).
When it lies on the cupboard it seems that it stays ok...again very strange.
Also while charging the battery status was 48%. I removed the charger and the status jumped to 100% :s.
Does anyone know how much it costs to have the MB replaced?

MDA Compact III
Hi!
I had the same promlem with my MDA Compact III!
I think it's a hardware problem. I tried so many roms, original, and cooked too... change the battery, clean the motherboard, but didn't help.
I was nervous, take out the battery for 5sec then reinstall it and took it in the refrigerator (NOT IN THE FREEZER!!!) for about 10minutes!
The result: don't crash about 1 hour!
So i took it back for 1day. And now, it works 2weeks continously, with no crash.
But unfortunately the battery (also the new one) holds the charge only 1day.

ElVikin said:
I hope u really try to get them to awnser what they change this time and then u can tell us? who knows it might help to know that.
Click to expand...
Click to collapse
Same problem here. I called HTC, they picked up my device, replaced the inside (motherboard) I guess because my device has a different IMEI number now. Very quick service, within one week my device was at my desk again.

I had similar problems.
had my HTC repaired (new MB)
problems remained the same.
after two repairs I received a new device and even that did not solve my problems.
Up till I bought a new battery
now he is working perfect again!

Hi i have the same problem as all of you. But is there really no solution to this problem except for sending it up to HTC and let the **** be replaced?
I also have the exprience that when its in my pocket is crashes also directly. but when it's just lying on the table nothing happens.
It is now lying there for 2 days without crashing.
i flashed it back to the original ROM. but still crashes after i put it in my pocket.
when i reset it (i cannot turn it normal on with the on button) it turns back on and starts normaly. i can use it now aslong as i don't put it in my pocket.
Please will some-one help find a solution for fixen it what causes these problems.
Many thanks in Advanced Fill

Fill said:
Hi i have the same problem as all of you. But is there really no solution to this problem except for sending it up to HTC and let the **** be replaced?
I also have the exprience that when its in my pocket is crashes also directly. but when it's just lying on the table nothing happens.
It is now lying there for 2 days without crashing.
i flashed it back to the original ROM. but still crashes after i put it in my pocket.
when i reset it (i cannot turn it normal on with the on button) it turns back on and starts normaly. i can use it now aslong as i don't put it in my pocket.
Please will some-one help find a solution for fixen it what causes these problems.
Many thanks in Advanced Fill
Click to expand...
Click to collapse
just get a new battery and it hopefully will do...it solved my problems...first time i hat the issue....right now i'm having it again...and it seems like the battery
you say it stays like that or 2 days...try running some heavy apps like igo or something other which is memory and battery consuming..it will probably crash..if it does...i'm 95% sure it's the battery

Fill said:
Hi i have the same problem as all of you. But is there really no solution to this problem except for sending it up to HTC and let the **** be replaced?
I also have the exprience that when its in my pocket is crashes also directly. but when it's just lying on the table nothing happens.
It is now lying there for 2 days without crashing.
i flashed it back to the original ROM. but still crashes after i put it in my pocket.
when i reset it (i cannot turn it normal on with the on button) it turns back on and starts normaly. i can use it now aslong as i don't put it in my pocket.
Please will some-one help find a solution for fixen it what causes these problems.
Many thanks in Advanced Fill
Click to expand...
Click to collapse
Exactly my case!!!
I am fed up of being consistently taking my battery out or soft reseting. If it stays over the table quiet, it's ok. The moment it goes into my pocket...
Just ordered Hero...

velhote said:
Exactly my case!!!
I am fed up of being consistently taking my battery out or soft reseting. If it stays over the table quiet, it's ok. The moment it goes into my pocket...
Just ordered Hero...
Click to expand...
Click to collapse
Thanks for replying, it seems that the problem has fixed itself. i put it in the original charger for about 3 or 4 days. it still crashed a couple times just reset with the charger connected put it back. i now just disconnect it from changer (2 days) (after 3 or 4 days in the charger) without any crash. runned tomtom for couple or houres?
i also turned the phone function off and removed the simcard.
hopefully it will keep running and then i gonna try to put my simcard back in.
Thanks
Fill
-----
Ok it crashed already again

T-Mobile Dash doesn't want to boot

Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.

hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
Take out the memory card and try to boot her up. If that does not work.. call T-Mo and get a new one

To get past the error 270, download the SDA Unlock app. That should get you past the error there. As for not getting past the Windows screen, I had that problem too. You should be able to get it working by hooking it up to the charger. I found that my Dash was not reading the battery as having a charge. I am not sure if I have solved the overall problem yet but, just in case, you might avoid using the USB as a charger and go with the wall charger. Just keep it on the USB long enough to sync and unplug.
Hope that helps

hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
do a hard reset hold da 2 soft keys and press the on button keep holdin da soft keys until u see a screen asking u do u want to do a hard reset hope dat works

Thanks for the responses guys but i've already tried all that. The only thing i haven't been able to try is do a hard reset with the wall charger plugged in, for some reason it doesn't matter how many times i do the steps it never shows me the black screen. I might be on the same boat as you because the battery i got with the phone is some cheap counterfeit chinese crap. I'll keep trying to get to the black screen with the phone plugged in but any other help would be greatly appreciated.
Btw, i can't do anything with T-Mobile because this is an unlocked phone i got somewhere else and can't return it so i'm stuck trying to make it work.

Check sticky to make sure doing correctly
Hard-Reset & Bootloader there is 2 x options there.

I was doing it right.
So after a million retries i got the phone to boot and do the cold boot thing. Then, i did the usual steps for putting a newer rom with WM6.1 on it (RUU_Excalibur_WM61_Kavana_080408_WWE). It worked, rebooted and went into the home menu, i thought i had brought it back from the dead until i inserted the sim. I got the sim failure message and when i pressed done it crashed. Now it won't go into the home menu no matter if the sim is inserted or not. Already tried to see if the sim was making good contact by putting pressure on it, no change.
This is too frustrating.

Ok so i've semi gotten it to work by booting it up without a sim, turning flight mode on, inserting the sim and then turning flight mode off. I get asked for my pin, the phone registers and i can make/receive calls. The problem is that a) it eventually loses the connection and b) i don't want to be doing this every time i turn the phone on.
Any ideas?

XDA Orbit not running right

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?

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.

You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.

Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin

Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.

Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.

Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.

I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.

"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.

[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.

Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.

[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.

15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.