Managed to get a HTC Desire for an absolute steal of a price as the seller had managed to forget his lock pattern and hadn't set up a google mail account to bypass the lock pattern. Having used Android phones before I knew that if I could just figure out the correct combination of buttons on startup I'd be able to reset the phones to factory settings and have a working phone.
So, I quickly bought the phone, figured out the "Power+Vol Down" combination and ran a factory reset from within that menu.
The phone restarted and I went through the setup and everything seemed fine, until I tried to send a text/make a call.
When I send a text message, I get the message sending failed error and it retrys various times before the phone finally gives up and stops trying.
When I try and make a call the phone just hangs for a couple of seconds on the dialing screen, beeps and cuts off (as though I have no signal).
I assumed that the phone had been blocked, hence the seller was selling it so cheap and he had come up with this story of locking it out, but after having a play I realised the internet was working perfectly and I had full HSDPA signal. Now correct me if I'm wrong but I'd have no sort of connection if the phone had been blocked by the carrier?
I assumed this was a software issue and have updated from 2.2 to 2.3 but still the same issue. After updating, I've also realised that I am unable to change network carriers (I'm on TMobile and they now share networks with orange).
My sim works perfectly in other phones and if I put another sim in the Desire, it still has the same issues. The phone is locked to TMobile (not that I think that would matter), running the official HTC 2.3 Gingerbread release and as far as I'm aware my APN settins are all okay.
If anyone could shed any light onto what is going on here, and hopefully to a fix then it would be greatly appreciated
Thanks in adavnce
Please use the Q&A Forum for questions Thanks
Moving to Q&A
my apologies, thanks for moving me to the correct forum
Hello! I don't know why but my phone started having this problem. It was out of nowhere. Well, maybe not, I've flashed my phone with the official mango update like two weeks ago, and it was working fine.
And today I saw that that I messages doesn't send out. I tried to call/text myself from other phone, and I couldn't. Phone displays gsm network name in phone hub, and also it shows full gsm connection bars(five of them), so you couldn't tell that something is wrong until you try to text or call. When you call the phone says "dialing..." but this shows forever and there's no sound from the speaker. It's worth mentioning that I've received few messages I've send to myself, but just about 2hours from sending, and then I tried to send a few more and haven't received those. Also, I've suceeded to call for a few times but after a long long wait(like at least 30sec) with the "dialing..." message shown. However, I cannot reach the phone when calling from my other phone.
I've tried to turn my phone on/off, to take the battery/sim card off, reseting the device, but none of these things helped. Then I've decided to flash my device. I've flashed my phone with DeepShining Mango custom ROM, and it seems to be working fine, but the problem still exists.
I don't know what else to do. And that's a major problem, because noone can call or text me. As I've said in the beginning, it was out of the sudden, I haven't done anything to my phone. Just yesterday I was using my phone normally, texted and called with no problem.
So I'm asking yours, guys, help. Could you please suggest what I could do? Thank you very much!
P.S. I've bought this phone from second hand and it was unlocked, but it has an orange logo on the battery cover, so I suppose it was locked to orange.
Did you pay your bill?
I have a prepaid card.
Ok, do you have a another SIM to test
I saw a topic almost the same as mine but I don't really understand what they're all saying as I am an Android Noob.. I think my case is different because I upgraded my phone without using the leaked one..
I just upgraded my Samsung Galaxy Note 2 to 4.3 last Tuesday, 12/24/13 and today, I noticed that I can't send and receive SMS and Calls on my phone. I don't know if the problem is my phone or my sim card. I tried restarting the phone and reinserting the sim. I almost tried everything. I can't try a new sim because I have no extra micro sim in my house.
When I send a text, it says "currently unable to send your message. it will be sent when the service becomes available" then it goes on a message loop. When I try to call someone, it says "Not registered on network". The signal bar is full though.
Is there a way to solve this issue without having to root my phone? I still have it on warranty and I can't really follow complicated instructions since I'm new to Android.
if there is really no way of solving this issue, then i'll go to the SSC. however, i really want to fix this alone cause' i'm pretty sure that they'll wipe off everything from my phone. if wiping every off of my phone will solve the issue, than i guess i'll just have to give it to SSC.
Thank you.
Something really weird is going on with my At&t galaxy s3. I'm new to this forum so I'll just explain what I'm experiencing and do my best to work through it will all of you. This phone got rooted by someone else and when I got it, the rooted program was in chinese and was acting all weird and wasn't getting good reception, although it was before it was rooted. I flashed it back to normal and it's acting very curious. It will receive an At&t simcard but the service bars will go from 1 bar to 4g to Edge to 1 bar all in a matter of 20 seconds or so and doesn't seem to work. It will occasionally work to send messages, make calls, but it seems like it can't ever receive calls. I checked and the IMEI number is still the same. Also, I had originally tried to unlock it to another carrier and when I put in different simcards (From other carriers such as verizon) the service bars don't show up, instead, all it shows is a cancel sign and doesn't ask for an activation code or anything. I'm honestly not sure what to do here, I thought I had broken the simcard reader and replaced that, but that made no difference. I'd greatly appreciate any help. Thanks!
StookDog said:
Something really weird is going on with my At&t galaxy s3. I'm new to this forum so I'll just explain what I'm experiencing and do my best to work through it will all of you. This phone got rooted by someone else and when I got it, the rooted program was in chinese and was acting all weird and wasn't getting good reception, although it was before it was rooted. I flashed it back to normal and it's acting very curious. It will receive an At&t simcard but the service bars will go from 1 bar to 4g to Edge to 1 bar all in a matter of 20 seconds or so and doesn't seem to work. It will occasionally work to send messages, make calls, but it seems like it can't ever receive calls. I checked and the IMEI number is still the same. Also, I had originally tried to unlock it to another carrier and when I put in different simcards (From other carriers such as verizon) the service bars don't show up, instead, all it shows is a cancel sign and doesn't ask for an activation code or anything. I'm honestly not sure what to do here, I thought I had broken the simcard reader and replaced that, but that made no difference. I'd greatly appreciate any help. Thanks!
Click to expand...
Click to collapse
Unlock is supposed to be permanent so it's odd that you lost it.
Now as for your problem, a lot of people are getting this issue lately, where unlocking damages their nv file. The solution can be found here: http://forum.xda-developers.com/showpost.php?p=43842387
BWolf56 said:
Unlock is supposed to be permanent so it's odd that you lost it.
Now as for your problem, a lot of people are getting this issue lately, where unlocking damages their nv file. The solution can be found here: http://forum.xda-developers.com/showpost.php?p=43842387
Click to expand...
Click to collapse
Thanks for your quick response I have been looking for a long time and never saw this issue before. I'm not sure where I'll be able to find a replacement nv file...but i'll see if anyone I know has a galaxy s3 from at&t. Maybe once I do this the unlock issue won't be messed up anymore.
Hi guys,
I am experiencing a bug on my Swift where the phone reboots itself during almost all calls after a minute or so. When the phone comes back on, there is no record of the call in the call log! The phone does not reboot during any other activities. Phone details below:
Wileyfox Swift
Cyanogen OS 12.1.1-YOG7DAS2FI
Kernel version 3.10.49
Build Number LMY48Y
I have checked for another similar thread without any luck. Thanks!
I have a similar,though not identical issue. Phone keeps rebooting,seemingly at random,every other day or so. During a call, listening to spotify,idle on the desk...i have an untampered with original Os on the phone.
Cheers,
Me too.
Hi, I just registered to say I'm having the same problem. If you check the Amazon UK reviews too there are several people with this rebooting problem.
So far I have:
- uninstalled all additional apps I installed
- tried it with wifi and data off
- tried the other SIM slot
- done a factory reset
and it still reboots during calls. After the factory reset things appeared to work better in general (alarms now worked properly, and there were more options available, eg in the power button menu), but it rebooted 5 seconds into a phone call, which is a record. It's usually a few minutes into it.
The factory reset didn't actually delete my data (photos, files, etc), so I am going to do a reinstall via Fastboot now; firstly because I'll have to do that I guess if I want to send it back, and secondly to see if it finally fixes it.
I personally think the update process has screwed something up. It did an update as soon as it was powered on for the first time (it to 12.1), then a couple of weeks ago did another update to 12.1.1. It was rebooting before 12.1.1, so it is either 12.1 or earlier where the problem exists.
If it still reboots after a Fastboot reinstall then it's getting send back, and I probably won't ask for another. It's a nice phone, and a nice idea but I can't have a phone that reboots during >50% of calls. That's useless.
Pretty sure you can discount the update process too! I have also had this issue on cyanogenmod nightlies, I honestly thought I had inadvertently pushed the power button..but, NO
*edit* CM13 nightlies
That's strange as I have had no such problem with mine (bought in October) and mine is rooted with the unofficial builds of CM13... Maybe it is a manufacturing error and only on some devices...
Have you tried contacting Wileyfox?
I have not experienced this yet on the Swift when making or taking calls on it.
i'm on the latest cm13 nightly for crackling. each and every time the phone is called, whichever sim, the phone reboots. what a waste...
I have the same issue of spontaneous reboots, mostly during calls but also at other times. Spoke to Wileyfox who weren't very helpful. Has anyone found a solution for this?
Hi, I'm having the very same issue (appears a few are on other forums). Has anyone found a solution? I'm about to factory reset if it continues
Update
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
enzoparker said:
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
Click to expand...
Click to collapse
Hi thanks for the update, I've just factory reset, if problem persists I'll try to get a replacement too! Was it quite a quick replacement process?
R
I'm in South Africa and have the same problem. Whenever sound is involved, I get random reboots. Calls, and music/audio books.
Not with videos though.
It doesn't reset any other time except when I've been listening to music, or on a call.
Been doing this from the beginning.
I thought it was Google Play Music, so downloaded different player.. That made it much less frequent, but then it started affecting my calls as well.
Not happy.
Hi, UK user here. I got this phone less than a week ago and have already had this issue a few times. Two spontaneous reboots on resuming from sleep, being connected to a large WiFi network was the only change from normal use here; then twice regarding calls, once when answering then immediately after reboot it rebooted again while the missed call notification was present, although still on the aforementioned large WiFi network. Unmodified, unrooted, Cyanogen OS 6.0.1 with two sims in use.
Same issue on my a1g2.
It reboots on wf swift Roms. It stucks in call screen on a1g2 stock rom. Strange...
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
DevilMind007 said:
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
Click to expand...
Click to collapse
Maybe it's the Dialer in Cyanogen OS, i installed the Google Dialer and made it default Dialer on my Swift, i don't have any problems with reboots during calls and i make long phonecalls. You don't need root access for this.
Although Wileyfox accept that there is a grounds for returns, I believe it is a software bug in Cyanogen OS 13. This fits in with using another dialler. You could also downgrade, or switch to Cyanogenmod.
Also, I only have found the issue when receiving calls, rather than making them, although I don't use a lot of minutes.
Sent bug reports to Wileyfox.. They're saying that what they see is a battery-pull reboot..
I tell them it's happening while I'm using the phone (music or calls)..
They say they can't see what the issue is.
Cos I'm in South Africa, sending the phone overseas is pointless.
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.