Related
Hi I am currently a T - Mobile customer and when I originally bought my Samsung Galaxy S2 with the company, I thought I could take advantage of using both the T - Mobile network and 2G services of the T - Mobile Orange Network.
However after successfully using it for the first 2 weeks, after my KE7 firmware update, I have an unbranded phone, it did not connect to the network anymore, stating, even if I manually select T - Mobile Orange in GSM mode only, Cannot registor with network, Unable to connect, then it states it is registered and yet I have emergency calls only stated and not either T - Mobile or even T - Mobile Orange. Then it will not connect to either network manually until I restart the phone.
I have since flashed my phone with various other firmwares, am currently on cognition s2 1.13, it's a great Rom, and still the same thing occurs.
I have contacted T - Mobile, they can't fix it, I have took the phone to a Samsung Repairer and they couldn't see anything wrong, stating it was a fault with Orange, as the guy in the shop's T - Mobile branded Galaxy s2 did the same.
Anyone solved the mystery, or is able to explain the issue to me?
It's doing my nut in, I have had phones like these for years, flashed them and enjoyed them, and usually work things out for myself, my last phone was an Samsung I8910, which was great with custom firmware support and I must say the Galaxy s2 is by far my favourite ever phone, but even my Samsung Omnia I8910 works properly on T - Mobile and Orange, and the latest and greatest phone won't!!
Have you tried flashing a different modem? Seeing as the cognition rom is based on I9100XXKG1, I know of a couple of forum members that have had trouble with the KG1 modem, and had to revert to the KF2 modem.
Worth a try? It won't wipe you phone of anything daft either.
List of official modems: http://forum.xda-developers.com/showthread.php?t=1131950
Before you do anything, can you dial*#1234# and just check what phone software is installed?
Thanks for the option Unfortunately I have tried the KE2, KE7, KF2 and KG1 Modems now, none of them have worked. It is really bizaar as the bloody thing works really well on T - Mobile, when there is coverage, plus the 3 and H is great speeds when they are in coverage, it just won't switch to Orange
mattisfaction said:
Thanks for the option Unfortunately I have tried the KE2, KE7, KF2 and KG1 Modems now, none of them have worked. It is really bizaar as the bloody thing works really well on T - Mobile, when there is coverage, plus the 3 and H is great speeds when they are in coverage, it just won't switch to Orange
Click to expand...
Click to collapse
one moment, I'm on t-mobile aswell.
text YES to 2121.
Homer moment: Doh, you cant text can you?
Just for reference, I'm with Orange and in my network list I have both "Orange" and "Orange and T-Mobile". I can connect to the Orange one fine, but not to the other one. It does switch to T-Mobile sometimes though. I've seen it do it.
Hi again, I have text yes to 2121, and it was working on my phone before. So yours has no issues then?
mattisfaction said:
Hi again, I have text yes to 2121, and it was working on my phone before. So yours has no issues then?
Click to expand...
Click to collapse
No, but I remember I used to have an everythingeverywhere app in data/private, which is no longer there.
I just texted yes to 2121 and now it lets me register on orange aswell as t-mobile.
stoney73 said:
No, but I remember I used to have an everythingeverywhere app in data/private, which is no longer there.
I just texted yes to 2121 and now it lets me register on orange aswell as t-mobile.
Click to expand...
Click to collapse
I just looked in data/private and do not have an everythingeverywhere app, plus I have just again text 2121 and still cannot use the orange network
Cheers for your advice though mate
johncmolyneux said:
Just for reference, I'm with Orange and in my network list I have both "Orange" and "Orange and T-Mobile". I can connect to the Orange one fine, but not to the other one. It does switch to T-Mobile sometimes though. I've seen it do it.
Click to expand...
Click to collapse
Cheers for the information
Unfortunately if I let mine automatically switch network, it switches to emergency calls only if I am out of a t mobile network range, not orange, and it used to switch to orange no problem
Then when it is in emergency calls only, I have to turn it on and off to get it to work at all, as it will not register back to T mobile
My last attempt......when you go into wireless/mobile network settings, is data roaming ticked?
stoney73 said:
My last attempt......when you go into wireless/mobile network settings, is data roaming ticked?
Click to expand...
Click to collapse
Yes it is, cheers for all your help. It's very frustrating and I can't fathom it out, so cheers for trying yourself
You don't need data roaming ticked in order to use Orange. T-mobile and Orange are both considered 'home' networks.
I'm on T-Mobile without data roaming ticked and it switches automatically to Orange without any issues. Might be worth phoning t-mobile up and seeing if there's some sort of issue with your account.
I installed Lite'ning Rom and found that I couldn't connect to Orange on my unlocked tmobile sim. Turned out that I had the "com.orange.authentication.simcard.permission" apk missing.
Downloaded it here:- http://www.contentsd.nl/apk/SimServicePermission.apk
and installed it with titanium and registered ok on orange.
Hope this helps.
dirobeshploppy said:
I installed Lite'ning Rom and found that I couldn't connect to Orange on my unlocked tmobile sim. Turned out that I had the "com.orange.authentication.simcard.permission" apk missing.
Downloaded it here:- http://www.contentsd.nl/apk/SimServicePermission.apk
and installed it with titanium and registered ok on orange.
Hope this helps.
Click to expand...
Click to collapse
I've just checked my simfree phone and it has the above apk installed. How on earth did you figure out you were missing this apk??
Joey2o11 said:
I've just checked my simfree phone and it has the above apk installed. How on earth did you figure out you were missing this apk??
Click to expand...
Click to collapse
Was browsing the list of stock apk's here:-
https://spreadsheets.google.com/spreadsheet/pub?hl=en_US&hl=en_US&key=0Ag43oj7rLQP4dENZcmhGN0ZUa3pHSENVeXlqUm5vV0E&single=true&gid=0&output=html
and noticed the "com.orange.authentication.simcard.permission" reference and when I checked via titanium it wasn't installed so I tried it and it sorted out my problem.
Hiya guys. Sorry to jump on this thread but I am having the same issue as OP. I'd just like to give you an update on what I know so far. It is a nightmare trying to speak to someone at T-Mobile who actually knows whats going on, but I was persistent and got through to an engineer who said that they are having transmitter problems in east anglia and surrounding areas...not sure if you are in that area or not. Unfortunately all the engineer said is that they are working hard to a. figure out what the problem is ang b. fix it! He also could not give me an ETA and said that the only way to get back onto the network is to reboot the phone a couple of times. Not ideal, but I though it was something to do with the VillainRom that I flashed...so here's stupid me flashing stock, bricking/unbricking the phone etc etc only to find out later that its not the phone...on the plus side I have amazing battery life now haha who would have thought ey!
Anyways, hope this information is useful to you all.
Steph
It is not a ROM issue - it is a T-Mobile/Orange fault
stephan.pieri said:
... I was persistent and got through to an engineer who said that they are having transmitter problems in east anglia and surrounding areas...not sure if you are in that area or not. Unfortunately all the engineer said is that they are working hard to a. figure out what the problem is ang b. fix it! He also could not give me an ETA and said that the only way to get back onto the network is to reboot the phone a couple of times. Not ideal, but I though it was something to do with the VillainRom that I flashed...so here's stupid me flashing stock, bricking/unbricking the phone etc etc only to find out later that its not the phone...on the plus side I have amazing battery life now haha who would have thought ey!
Anyways, hope this information is useful to you all.
Steph
Click to expand...
Click to collapse
Absolutely right Steph, it is not ROM related.
T-Mobile have acknowledged that there is a problem with registering T-Mobile customers on T'Orange cell towers.
I've been having this issue for a couple of weeks now (also in East Anglia), and after a lot of perseverance I got transferred to Level 2 support (Technical Support - not Customer Support) last Monday. They said there was a 'rectifier problem' on a mast in Henny Street, near Sudbury, Suffolk at the end of June and it has had a knock-on effect on other masts in the area. It was/is a level 2 priority for fix.
I wasn't happy with that explanation as it happens all over Suffolk!
Still with the issue on Thursday, I called them again and got straight through to Level 2 as they had marked my account as an on-going problem which Customer Support (in the Philippines) couldn't handle.
While explaining in detail the 'Your SIM does not allow you to connect to this network' problem the Guy I was talking to received an internal notification that they were aware of issues registering on T'Orange cells, that they'd known about it for 72 hours, have no idea what is causing it, and no eta to fix.
I've been using a forced connection to T'Orange for the last couple of days (poor T-Mo signal in house which always caused it to hunt for T'Orange anyway). Downside of course is that it won't get a 3G signal when forced into T'Orange mode.
Still happening today so need to give them another prod...
Oh, and I found this thread searching for answers - I don't have a Galaxy S, I have a Desire. Further proof that it isn't ROM related.
I'll update when I find out more from them.
Aaron
Just spoken to them again, problem is still on-going, they are still investigating and looking for more samples of the problem to try and isolate the issue. In light of that I would suggest anyone else having this to phone them and ask for Technical Support and register the fault - the more samples they have, the better chance of getting it resolved.
In other words, they still don't know what's causing it or when they'll fix it.
Hi People
I recently bought a second hand Samsung Galaxy S2 locked to T-Mobile (UK).
I unlocked it (Chainfire Galaxy S2 Sim unlock utility did not work) using Helroz unlock utility. Installed O2 Sim, phone booted fine. However I cannot make calls with any SIM inserted into the phone.
After much research and many forums later I put android 2.3.3 on the phone - mainly because I only had a single CSC Code (TMU - T-Mobile UK ?), installing Andriod 2.3.3 allowed me to choose a generic CSC Code XEU (*#272*<EMEI>#). This did not help still cannot make calls.
I decided to install Android 2.3.4 samfirmware - still cannot make calls.
I bought a T-Mobile Sim and inserted into the phone the name of the network (T-Mobile) is now shown (previously it said "Emergency Calls Only") but still cannot make calls. I have spoken to T-Mobile and they have assured me that this phone is not barred from their network.
Currently have Android 2.3.5 installed (samfirmware) - still cannot make calls and cannot send texts either.
Any help would be much appreciated - but please speak slow as I am a noob!
I apologise if this issue has been dealt with in another thread.
The plot thickens
I spent some time on the phone with T-Mobile yesterday and this morning my phone CAN make T-Mobile calls.
If I put *#simlock# into the dialler it tells me that the
Network Lock [OFF]
Network Subset Lock [OFF]
SP Lock [OFF]
CP Lock [OFF]
Therefore I assume I should be able to use this phone with other networks, but I cannot use it with Vodaphone or O2.
The CSC code is XEU (*#272*<EMEI>#)
Any help much appreciated.
Help needed
Any help with the above problem would be very much appreciated
having the same issue here tried *#simlock# and everything appeard just like you mentioned did you find a fix for this Im trying to get my gfs phone to connect to giffgaff
Dont like the sound of that. Am seriously looking at getting an S2 on a 24 month contract this week. I dont normally bother with contracts and usually buy factory unlocked, but on seeming to read these were pretty easy to unlock, I figured I had nothing to lose.
Now not so sure. Have you managed to solve this?
pewdle said:
Dont like the sound of that. Am seriously looking at getting an S2 on a 24 month contract this week. I dont normally bother with contracts and usually buy factory unlocked, but on seeming to read these were pretty easy to unlock, I figured I had nothing to lose.
Now not so sure. Have you managed to solve this?
Click to expand...
Click to collapse
My GF bought this through ebay and its looking like its been barred from what the replys on giffgaff are suggesting, plus from googling Id say me and the OP have been the only people that have had this issue so far...The SG2 has been exceptionally reliable so far for myself plus do some shopping around and get a 12 or 18 month contract as 24 months are just overkill
Sometimes after I reset the my phone I get the notification "restricted access change".
At first i thought it might be sim card since it is a new phone. So I switched it with my wifes and she put mine in hers. Her phone worked perfectly but when I turned mine on, It worked for a bit (sometimes does this also) then eventually stops working.
* no Texts can be sent or received and no calls can be received. If I try to call someone it stays on dialing and I can't cancel the call. (stays as if I am calling and have to reset phone)
Sometimes It doesn't show error, Just stops all of the above anyway.
Any suggestions or comments? anything would help.
Did you ever get to solve this issue? I am getting it on my T-mobile S3.
Tmobile could not solve the issue. Now sending the device to Samsung support to see any hardware issues...
cnraghu said:
Did you ever get to solve this issue? I am getting it on my T-mobile S3.
Tmobile could not solve the issue. Now sending the device to Samsung support to see any hardware issues...
Click to expand...
Click to collapse
I am getting this error too on my T-Mobile S3. Any info on this would be greatly appreciated.
EDIT:The reason I was getting this error was due to the guy I got my S3 from closed his t-mobile account without paying the ETF. Therefore my S3 now has been blocked on Tmobile network. The guy gave me a refund on the phone tho.
Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.
Hello all,
To put my issue simply, I am receiving the "Not registered on network" error on my phone. I have tried many things to resolve it and to help narrow down the possible problems, I will explain my situation and what steps I have taken to try to resolve it. I appreciate you taking the time to read my detailed explanation in advance, as I wish to be as clear and informative as possible.
My phone is an unlocked Australian Galaxy S3 (GT-I9300). I bought it about 6 months ago and about two months ago had some issues with the display come out of the blue. I was able to get this issue resolved through my warranty. When I received the phone back though, I thought it was all working fine but then I noticed I couldn't send SMSs or make calls as my phone wouldn't connect to my phone network (Vodafone). I tried reboots, hard reboots, restoring backups, using a different SIM card (from a different carrier) and I still couldn't get it to work.
During this process of trying to fix it myself, I rooted the phone. So when I realised I couldn't fix it and it could possibly be a hardware issue, I sent it back to be fixed under warranty. Unfortunately my warranty was voided when I rooted the phone, even though it was broken before I rooted it.
So a few days ago I received my phone back again and spent about 6 hours trying to fix it. Here's what I tried...
I tried to flash the latest Australian firmware (XSA) which is the same as the one I initially had when I purchased the phone. I tried factory resets, different firmware flashes, custom ROMs, different modems etc. None of this worked. I thought I had found my solution when I stumbled across ARIZA's patch, but event this did not solve my problem.
The really strange thing is I can occasionally connect to the network and if I try repeatedly, I can sometimes get an SMS to send. I've checked my SIM is clean (I've tried another SIM anyway) and everything seems fine.
My IMEI number is still intact and isn't blacklisted. I've tried restoring backups from when it was working (before I got it "fixed" the first time) and that's not worked. The current status of my phone is:
ROM: Omega v5.0
Version: 4.2.2
Baseband: I9300XELLA
Network: vodafone AU (sometimes shows as Unknown)
Mobile Network State showing as "Disconnected", except in rare moments
IMEI and Serial intact
I've tried all I can think of and all the suggestions I can find on the Internet. I'm hoping someone here will have some suggestions for things I can try. I'd really like to fix this issue as I've been without my phone for months. I'm thinking it could be a hardware issue, but want to make sure I've exhausted all options I can try myself first before trying to get a place to repair it. As my warranty is void, I'm not sure how easy this will be.
Thanks in advance for your time and suggestions,
Jay.
.:Jay:. said:
Hello all,
To put my issue simply, I am receiving the "Not registered on network" error on my phone. I have tried many things to resolve it and to help narrow down the possible problems, I will explain my situation and what steps I have taken to try to resolve it. I appreciate you taking the time to read my detailed explanation in advance, as I wish to be as clear and informative as possible.
My phone is an unlocked Australian Galaxy S3 (GT-I9300). I bought it about 6 months ago and about two months ago had some issues with the display come out of the blue. I was able to get this issue resolved through my warranty. When I received the phone back though, I thought it was all working fine but then I noticed I couldn't send SMSs or make calls as my phone wouldn't connect to my phone network (Vodafone). I tried reboots, hard reboots, restoring backups, using a different SIM card (from a different carrier) and I still couldn't get it to work.
During this process of trying to fix it myself, I rooted the phone. So when I realised I couldn't fix it and it could possibly be a hardware issue, I sent it back to be fixed under warranty. Unfortunately my warranty was voided when I rooted the phone, even though it was broken before I rooted it.
So a few days ago I received my phone back again and spent about 6 hours trying to fix it. Here's what I tried...
I tried to flash the latest Australian firmware (XSA) which is the same as the one I initially had when I purchased the phone. I tried factory resets, different firmware flashes, custom ROMs, different modems etc. None of this worked. I thought I had found my solution when I stumbled across ARIZA's patch, but event this did not solve my problem.
The really strange thing is I can occasionally connect to the network and if I try repeatedly, I can sometimes get an SMS to send. I've checked my SIM is clean (I've tried another SIM anyway) and everything seems fine.
My IMEI number is still intact and isn't blacklisted. I've tried restoring backups from when it was working (before I got it "fixed" the first time) and that's not worked. The current status of my phone is:
ROM: Omega v5.0
Version: 4.2.2
Baseband: I9300XELLA
Network: vodafone AU (sometimes shows as Unknown)
Mobile Network State showing as "Disconnected", except in rare moments
IMEI and Serial intact
I've tried all I can think of and all the suggestions I can find on the Internet. I'm hoping someone here will have some suggestions for things I can try. I'd really like to fix this issue as I've been without my phone for months. I'm thinking it could be a hardware issue, but want to make sure I've exhausted all options I can try myself first before trying to get a place to repair it. As my warranty is void, I'm not sure how easy this will be.
Thanks in advance for your time and suggestions,
Jay.
Click to expand...
Click to collapse
Return to a stock rom and use triangle away to reset the counter, retry with your provider, they may let it slide that you've previously tried.
It would appear that you've already tried everything.
Return to stock and update via OTA, remove root, remember to use triangle away, I personally haven't had to do it but i would imagine that it needs root privileges to complete so thinking about it i would say to use triangle away first.
Hope you get it sorted.
dladz said:
Return to a stock rom and use triangle away to reset the counter, retry with your provider, they may let it slide that you've previously tried.
It would appear that you've already tried everything.
Return to stock and update via OTA, remove root, remember to use triangle away, I personally haven't had to do it but i would imagine that it needs root privileges to complete so thinking about it i would say to use triangle away first.
Hope you get it sorted.
Click to expand...
Click to collapse
Hey,
Thanks for the quick response.
I doubt they would let it slide as I had a pretty long back and forth with them trying to get them to fix the phone or at least send it back to me without charging me for the shipping costs and that didn't end in my favour. I'm sure they'd remember that they already rejected it due to it being modified and would just blame the rooting for the issues.
I'm thinking I might just reset it all to stock, reset the counter and at least ask. If not, I'll try to find a repair shop who will take a look. Thanks for the suggestion. I'm still open to any other ideas people might have which I can try from my end.
Thanks,
Jay.
Starting point would be correct firmware modem and CSC for your location and network .
Flash your original rom .
Check
http://forum.xda-developers.com/showthread.php?t=1978840
jje
JJEgan said:
Starting point would be correct firmware modem and CSC for your location and network .
Flash your original rom .
Check
http://forum.xda-developers.com/showthread.php?t=1978840
jje
Click to expand...
Click to collapse
Hey,
Thanks for the suggestion. I believe I have tried this by downloading the latest firmware from SamMobile and flashing that through Odin, but I haven't tried it through Keis, so I guess I'll give that a go.
I'll let you know how it goes.
Thanks,
Jay.
Me too. I've an i9305 (S3 LTE) and i've tried every tutorials on internet and so far nothing: always the same issue "not registered on network". In case you solve the issue please let me know. I'll do the same. Txs
I've tried to connect my phone using Keis and it just seems to say "Connecting..." forever. I've tried running the connection troubleshooter and that just seemed to re-install the drivers but not actually fix the issue. I still can't get Keis to even connect to my phone.
Any ideas on why this would be? Or other suggestions I can try for my initial problem?
Thanks,
Jay.
As an update to this, it seems I've tried everything I can on my end to fix it to no avail. I believe it must be a hardware issue and have dropped it into a phone repair centre. I'm hoping they will be able to find the problem and fix it.
I'll let you know how it goes.
Another update to this, I received a response from the repair centre. They said:
"...we took it all apart and checked all connections and serviced it.
Once we put it back together we tested it with Vodafone and Optus sim cards. Both sims had service and were able to connect to the internet as well."
After I asked for more details on what they did to try and help me determine what the problem was, they said:
"The phone looked 100% fine inside, no signs of water or any other damage. Sometimes electronic devices can be a bit temperamental, maybe the fact that we undone and cleaned all connections it's booted it back to life."
So I'm going to pick it up tomorrow, but it sounds like it's all sorted now. So not it's not 100% clear what the issue was, but to anyone having this same problem who has tried everything like I did, it is likely a hardware issue. Your best bet is probably to try a repair shop (assuming your warranty won't cover the problem).
Thanks to those who offered suggestions and good luck to those with the same problem.
Do please tell us if it worked because i'm tempted to do the same as you did before selling it on ebay as faulty for parts. PLEASE ANSWER US BACK AFTER TESTING IT an entire day. THANK YOU A LOT!
Does it work properly now? Thanks - Please reply.
Not sure if it is exactly the same problem but I remember getting that msg when i was on Telstra and I'd installed a new ROM - I went to the Telstra site and got them to send an activation msg that reset my provider info. It didn't seem to matter for phone calls but I wasn't getting any connection to do with data until I 'ran' the msg they sent.
Hi I had this issue with my gs2..what I did was flash the right modem and restore efs thats how I solved my problem..hope this helps..
Sent from my GT-I9100 using xda premium
ichigo200 said:
Hi I had this issue with my gs2..what I did was flash the right modem and restore efs thats how I solved my problem..hope this helps..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Txs for help but I don't have the backups of my efs folder... so I think it is useless therefore i am going to sell it on ebay as faulty for parts. Unfortunately! I love my i9305!
You should probably do some more searching on site - there are a number of things to do, including getting a service centre to fix it. Be cheaper than a new phone. Is it an i9300 or ann i9305?
pmmfilipe said:
Txs for help but I don't have the backups of my efs folder... so I think it is useless therefore i am going to sell it on ebay as faulty for parts. Unfortunately! I love my i9305!
Click to expand...
Click to collapse
Ask a service centre for a fix price first .
jje
Homervy She
Journyman16 said:
You should probably do some more searching on site - there are a number of things to do, including getting a service centre to fix it. Be cheaper than a new phone. Is it an i9300 or ann i9305?
Click to expand...
Click to collapse
It's a i9305 and I've tried everything, every tutorials on internet without success so far. I am tired of the situation and also very disappointed therefore I think i will sell it as faulty. As it regards to a repair center, near my area it's very difficult to find someone who can fix it.
For me it seems my connection is still intermittent when using my Vodafone SIM on my S3 (and the same for another Vodafone SIM I tried on this phone) whereas both SIMs work fine on other phones.
I then tried a Telstra SIM on my S3 and it worked fine. So it seems I have a weird problem with my phone where the combination of the S3 and Vodafone doesn't work, but other phones or other SIMs do work.
I think I'm just going to try changing carrier (I've been meaning to anyway) since it seems their SIMs work in my phone.
Really not sure what is causing this issue, but I'm at the point where I just want it fixed and I don't really care how. Hope you find out how to solve your issue.
How is your phone right now? Im also having the same problem. It always say 'not registered to network' everytime i make a call. This happens whenever i turn on the flight mode, then turning it off.. i have a strong signal and i can use the internet provided by my network but i cant make a call or text.. people cant also reach my number. I sent this already to samsung service ctr and they changed the board but its still there whenever i access the flight mode..
caloyski072885 said:
How is your phone right now? Im also having the same problem. It always say 'not registered to network' everytime i make a call. This happens whenever i turn on the flight mode, then turning it off.. i have a strong signal and i can use the internet provided by my network but i cant make a call or text.. people cant also reach my number. I sent this already to samsung service ctr and they changed the board but its still there whenever i access the flight mode..
Click to expand...
Click to collapse
Hi...the same, no solution so far. I am actually selling it on ebay for parts. I simply gave up.