Bought the xdaIIS two months ago and was working fine until i used it for more than 10 minutes after which it completely freeze! only way to unfreeze it was to take the battery out! i eventually got it replaced and got a new one this week but still has the same problem!
Does anyone else have the same problem? or has a solution to this?
(the handset has the latest ROM and I have tried a hard-reset without success)
helppppp
Have you tried a Hard Reset with Corporate Mode selected when it first boots?
Mine have behaved so much better, without the O2 Active Tat!
problem solved
yeah that seems to have solved my problem
thanks a lot nixonm
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
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
tigerz0202 said:
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
Click to expand...
Click to collapse
It may be hardware related but it could also be an app that you are installing on each rom. Try a new rom and don't install anything for a few hours and see if it still happens.
Sent from my SGH-T989 using xda premium
tigerz0202 said:
so i guess ive been getting what you would call SOD's, only normally the only way to boot your phone is by pulling the battery ,well i can just hold the power button for an extended amount of time and it will reboot for a couple minutes and then shut down again ,after its through that cycle i can boot it normally with the power button, it happens when i plug the phone up and let it charge to 100% and if the phone isnt taken off the charge then it shuts down like this, its happened once on a call too and i wanna say the wi-fi was enabled every time ...i dont remember im running a test with the wi-fi off right now ,any how i would assume this would be hardware related since ive flashed every rom and it happens on all of them ....any thoughts? im planning on returning the device for another one ,just hesitant because i got one without any of the screen issues that some people are getting
Click to expand...
Click to collapse
SOD? whats that?
sleep of death
i think its related to the wi-fi being on while charging , just fully charged it and left the phone on the cord for an hour after charging and it never went off. ran it down to 90% and turned wi-fi back on and hooked it up to see if it does it again
that has happened to me with other phones, like Nexus S, I9000, Moto XT720
so it's definitely not hardware related AFAIK
the way i narrowed it down to has always been a ROM problem
after I flash clean up, or load a more stable ROM the Sleep Of Death goes away.
i had a lot of that with the recent "stable" CM 7.1 for Nexus S
flashed to a newer nightly unstable and it fixed the "stable" problem LOL
well i just got my new phone in yesterday and so far no random reboots or SOD's ,phone seems a little faster than my previous got 3700 quads stock unrooted and over 15megs download and almost 3 upload , i think i got a better device this time and im pretty sure it was a new one and not refurbished, im gonna run it stock for a couple days just to see if any problems re-occur, i was having them on my first phone before i rooted ,thats why i decided to root and install custom roms
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
Hello all,
since last 2 weeks, every time my phone switches off and when I turn it on, it gets stuck at the Sam. galaxy note 2 logo forever. I've tried restarting, removing battery but it doesnt helps. It all started when I was on a call and my phone just switched off.
Since then I've flashed my phone 6 times with different roms (Initially i thought boot sware got corrupt) like RR (lollipop and Marsh), nightly but issue still persists. I've also noticed that hardware key (menu and back key) have stopped working completely from last 3 days. If i continue to keep my phone on throughout it works alright untill it switches off again. Because of this, I have to flash my phone and go through installation of all apps which is tedious and irritating.
I'm not able to figure out what the problem is. Please help me understand the issue and suggest an appropriate solution.
Awaiting response. Thanks in advance
Best regards,
Sumeet Bais