Hello,
i got my second BA not long ago (2 months) suddenly i mean overnight beofre going to sleep i made a call the second in the morning it was showing a ! exclamation mark on instead of the signal received i reset it.
While restarting in showed No GSM.
I left for few days then check it it was working again but i could not use the speaker phone so i reset it again as usual when the speaker phone don't work but this time it was for good the GSM part is refusing to work????
Can any one help ????
Thanks in advance ...
nabilaj said:
Hello,
i got my second BA not long ago (2 months) suddenly i mean overnight beofre going to sleep i made a call the second in the morning it was showing a ! exclamation mark on instead of the signal received i reset it.
While restarting in showed No GSM.
I left for few days then check it it was working again but i could not use the speaker phone so i reset it again as usual when the speaker phone don't work but this time it was for good the GSM part is refusing to work????
Can any one help ????
Thanks in advance ...
Click to expand...
Click to collapse
Have you tried updating to the latest Radio Stack.. It's 1.13 as opposed to the 1.12 you're stating in your Signature.
It's in Wiki - On signature
Cheers!
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
I finally got my desire back from repair. Since then all my calls are on speaker at the backside of the phone and i need to push the button to get it to the "normal phone speaker"
this happens if I call someone and if someone calls me
How do i get it back to "normal"?
Try pulling the battery for a few seconds.
If this doesn't work do a hard reset.
You can also phone htc and tell them that you have this problem since the repair and ask them what should you do.
There are two other threads like yours, but they're without some definite fix.
http://forum.xda-developers.com/showthread.php?t=713981
http://forum.xda-developers.com/showthread.php?t=706618
I had to factory-reset it again now it works
But weird anywasys. I reinstalled all apps and i did not get that isse again
After almost a year long battle against the repair center and my HD2, I recently received a brand new HTC Desire. The phone is working fine, except for the really annoying reboot which happened already 3 times while receiving calls. On the 3 occasions the phone got stuck once I slided the bar to accept the call. The screen freezes and then it reboots (just once and not on a loop which apparently is more likely to happen with the desire). The repair center advised to perform a hard reset and if the problem persists, they want me to send it back to install a new rom.
Anybody got a similar issue or a solution that will allow me to keep my phone?
Cheers
will send it back for repairs. Probably a mainboard issue like the more common reboot issue
Thanks anyway
Happened to me on a custom ROM. Changed the kernel and the problem was gone.
Thanks for the tip man, but the phone has this problem out of the box, with factory settings. So I am guessing that this rules out a kernel problem. Or I just hope cos if every machine they sell has this issue, boy they are gonna be busy on the helpdesk
The phone came back from HTC repair with a new board and guess what... I still have the same problem. frak me right?
Anybody have any theory before I completely go bonkers?
Hi! This is my first time posting something here but I had no choice since a troubleshoot the handset in every single way that I could
Heres my situation, I bought a Samsung Glaxy S4 Mini GT-I9190 last month, then I was riding the bus to go work and suddently my cellphone starts getting stucked, then I restart the handset in order to refresh it ( Regular restart not forced or anything like that ) When the cellphone succesfully restarted the screen wont come up, I heard the booting sound, the lockscreen sound, even I heard some messages coming up but the screen is totally in blank
Already troubleshoot the handset removing the battery, removing the SD Card, SIM card and wait for 5 minutes but the screen didnt show up again... My handset is not rooted and I never dropped or damage it or anything like that. This situation is very frustrated because I HAVE to make so many calls to my girlfriend and my daughter and I'm not allowed to do it.
Can you Pleeeeeeeeeeeease help me out with this!? If you can its well appreciated !!! :crying:
Drogakit said:
:
Click to expand...
Click to collapse
I think u need to go to Samsung service, nothing u can do "at home"
Drogakit said:
Hi! This is my first time posting something here but I had no choice since a troubleshoot the handset in every single way that I could
Heres my situation, I bought a Samsung Glaxy S4 Mini GT-I9190 last month, then I was riding the bus to go work and suddently my cellphone starts getting stucked, then I restart the handset in order to refresh it ( Regular restart not forced or anything like that ) When the cellphone succesfully restarted the screen wont come up, I heard the booting sound, the lockscreen sound, even I heard some messages coming up but the screen is totally in blank
Already troubleshoot the handset removing the battery, removing the SD Card, SIM card and wait for 5 minutes but the screen didnt show up again... My handset is not rooted and I never dropped or damage it or anything like that. This situation is very frustrated because I HAVE to make so many calls to my girlfriend and my daughter and I'm not allowed to do it.
Can you Pleeeeeeeeeeeease help me out with this!? If you can its well appreciated !!! :crying:
Click to expand...
Click to collapse
not sure if this will help, you can try a master reset, also you haven't rooted the phone, but did you flash it.
Drogakit said:
Hi! This is my first time posting something here but I had no choice since a troubleshoot the handset in every single way that I could
Heres my situation, I bought a Samsung Glaxy S4 Mini GT-I9190 last month, then I was riding the bus to go work and suddently my cellphone starts getting stucked, then I restart the handset in order to refresh it ( Regular restart not forced or anything like that ) When the cellphone succesfully restarted the screen wont come up, I heard the booting sound, the lockscreen sound, even I heard some messages coming up but the screen is totally in blank
Already troubleshoot the handset removing the battery, removing the SD Card, SIM card and wait for 5 minutes but the screen didnt show up again... My handset is not rooted and I never dropped or damage it or anything like that. This situation is very frustrated because I HAVE to make so many calls to my girlfriend and my daughter and I'm not allowed to do it.
Can you Pleeeeeeeeeeeease help me out with this!? If you can its well appreciated !!! :crying:
Click to expand...
Click to collapse
try using a usb jig to get to download mode and reflash a stock rom ... if u dont have one you can make it by yourself
:laugh:
Well I take my handset to the assistance because it was under warranty so... I need to wait 15 days in order to have it fixed or they give me a new one... Thank you anyways for helping me out !!! :laugh::good: