EDIT: No feasible solution found, so I had the device sold. Question closed.
UPDATE ON THE ISSUE: It seems that it would not recognize WCDMA networks (GSM works properly), hence no signal on my WCDMA-only SIM card. Any ideas?
Hello all, new joining the Relay 4G forums
Long story short, so I got my Relay 4G today, but it just wouldn't fully recognize my China Unicom SIM card. Symptoms and information:
1) No signal
2) Correctly displays my carrier's name, but says "emergency calls only"
3) Can search for available carrier networks, including China Unicom, but fails to register on the network - it says "unable to connect, try later"
4) The device has a correct IMEI instead of a generic one
5) Doesn't prompt me to enter SIM UNLOCK CODE when I first plugged in the SIM card
6) SIM unlocking procedures posted in the forum doesn't help - the phone should be unlocked when I bought it
7) It recognizes another SIM card from China Mobile (WTF!!) and works properly
8 ) China Unicom uses the 2100MHz band, which is supported by Relay 4G
So now I'm out of ideas... Any help would be appreciated. Thanks
Sent from Google Nexus 4 @ CM11
See this thread for sim unlock. http://forum.xda-developers.com/showthread.php?p=40835465
croogrog said:
See this thread for sim unlock. http://forum.xda-developers.com/showthread.php?p=40835465
Click to expand...
Click to collapse
...So this phenomenon means this really is SIM-locked? Good, I'll revert to ICS and try unlocking with that method...
One question: why doesn't it prompt me to enter unlock code when I inserted the SIM?
@croogrog It didn't turn out to be that simple... SIM unlock procedures didn't work at all even though I got all the timings right. I think the problem isn't caused by SIM lock... But what can it be?
Sent from Samsung Galaxy Nexus @ CM11
Bump
Sent from Google Nexus 4 @ CM11
More strange symptom: another SIM from China Unicom got recognized quickly after I inserted it. I don't understand this...
Sent from Google Nexus 4 @ CM11
If other SIMs are working and you are able to call someone your phone was unlocked when you got it.
If your SIM isn't working it could be that you need a new one from your provider.
I had that problem years ago. My phone was too new ...or my card too old.
SGH-T699 (Relay 4G) Talk with a little Tapa
C3POID said:
If your SIM isn't working it could be that you need a new one from your provider.
Click to expand...
Click to collapse
Hmm, my not-working SIM is bought just days ago... I'll go to my carrier's deck and see if they could swap me a new card.
Sent from Google Nexus 4 @ CM11
AndyYan said:
I'll go to my carrier's deck and see if they could swap me a new card.
Click to expand...
Click to collapse
Good luck.
AndyYan said:
Hmm, my not-working SIM is bought just days ago... I'll go to my carrier's deck and see if they could swap me a new card.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Where did you buy the phone from?
gtmaster303 said:
Where did you buy the phone from?
Click to expand...
Click to collapse
From a local importer at TaoBao (China's equivalent of eBay).
UPDATE ON THE ISSUE: I changed my SIM card for a new one at my carrier's but still won't recognize. Adding in the symptom that it can recognize another China Unicom SIM, I guess I can conclude that the problem lies within this particular SIM.
Sent from Samsung Galaxy S Relay 4G @ CM11
AndyYan said:
From a local importer at TaoBao (China's equivalent of eBay).
UPDATE ON THE ISSUE: I changed my SIM card for a new one at my carrier's but still won't recognize. Adding in the symptom that it can recognize another China Unicom SIM, I guess I can conclude that the problem lies within this particular SIM.
Sent from Samsung Galaxy S Relay 4G @ CM11
Click to expand...
Click to collapse
Best test would be to try another carrier sim all together. Not china unicom. See if the phone takes it. That way you will know for sure that it's unlocked and works. Unfortunately, there's no way to check if it's unlocked, other than to test sim cards
My next suggestion would be to consult samsung for a warranty repair, because your phone might be faulty. Or consider asking the seller that you got it from to send you another one. Let us know if you still need help
Sent from my Galaxy S Relay
gtmaster303 said:
Best test would be to try another carrier sim all together. Not china unicom. See if the phone takes it. That way you will know for sure that it's unlocked and works. Unfortunately, there's no way to check if it's unlocked, other than to test sim cards
My next suggestion would be to consult samsung for a warranty repair, because your phone might be faulty. Or consider asking the seller that you got it from to send you another one. Let us know if you still need help
Sent from my Galaxy S Relay
Click to expand...
Click to collapse
1. I checked with a China Mobile SIM and it works. Also, as said before, another China Unicom SIM also works. Only this specific SIM doesn't. It IS unlocked when I purchased it.
2. No way for a warranty - I'm in China and this is a T-Mobile USA device that many local "smartphone gurus" haven't even heard of, let alone "repairing" it.
3. The importer only has one such device in perfect condition (others have plenty of worn and torn), so exchanging is not possible...
I'm thinking of setting up an alternative solution for now...
More update on the issue: even on the China Unicom SIM that got recognized, it wouldn't connect to WCDMA/HSPA+ networks. Did an experiment: I used *#*#4636#*#* to adjust network modes, and when the device is on GSM only / GSM/WCDMA auto / WCDMA preferred, it would receive signal like normal; however, choosing WCDMA only, no signal is received. It seems like the real issue lies within the device after all...
Sent from Samsung Galaxy S Relay 4G @ CM11
...The Relay isn't a WCDMA device.
Even though the relay is a US tmobile device i would still try to contact samsung. They may be able to help you and it can't hurt. This is certainly not the first Relay to leave the US and incur problems...
Sent from my Galaxy S Relay
Jax184 said:
...The Relay isn't a WCDMA device.
Click to expand...
Click to collapse
What? I mean, my carrier has the HSPA+ 21Mbps/42Mbps it supports... What do you mean by it not supporting WCDMA?
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
What? I mean, my carrier has the HSPA+ 21Mbps/42Mbps it supports... What do you mean by it not supporting WCDMA?
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
If I understand correctly, the network mode menu option for WCDMA in the CM10 ROM is left over from the D2, which is a phone of similar spec which our developers based our ROM on. It doesn't do anything on the Relay.
Jax184 said:
If I understand correctly, the network mode menu option for WCDMA in the CM10 ROM is left over from the D2, which is a phone of similar spec which our developers based our ROM on. It doesn't do anything on the Relay.
Click to expand...
Click to collapse
But it DOES switch network modes... Or so I think, judging from the symptoms.
The first SIM only supports WCDMA(HSPA+), and when inserted, it can find my carrier's network but can't connect. On the second SIM which is compatible with both GSM/WCDMA, I lose signal only when "WCDMA only" is chosen, and under this situation the symptom is same as above. I assume that it can find my carrier's GSM network but not the WCDMA one.
Sent from Samsung Galaxy Nexus @ CM11
Bump in vain. I guess I'll be selling this phone if the issue is really within the phone itself...
Sent from Samsung Galaxy Nexus @ CM11
Related
i am currently traveling around and i have bought the sim unlock code for the Infuse and it works great. i can use the sim cards from Taiwan and South Africa without a problem.
But the 3G capability on the sim cards are not working on the Infuse. i tried with my other phone i bought unlocked GS2 (international version) and the 3G was working great
do i need to root in order for the Infuse to be able to connect to 3G with other country's sim card? or i just need to do some setting on the phone?
please help, it's annoying carrying this big phone and unable to use it properly
thanks
You will probably need to put in the correct APN settings for your carrier. Many of the other ROMs will update the APN automatically, but the stock
ROM does not.
Sent from my SGH-I997 using XDA App
wuufer001 said:
i am currently traveling around and i have bought the sim unlock code for the Infuse and it works great. i can use the sim cards from Taiwan and South Africa without a problem.
But the 3G capability on the sim cards are not working on the Infuse. i tried with my other phone i bought unlocked GS2 (international version) and the 3G was working great
do i need to root in order for the Infuse to be able to connect to 3G with other country's sim card? or i just need to do some setting on the phone?
please help, it's annoying carrying this big phone and unable to use it properly
thanks
Click to expand...
Click to collapse
As PVD04 said thats an APN problem, go into google and search for the company you like for example i use 3g here in mexico and i typed " Telcel APN configuration" (Telcel is my carrier)
Do the same for your carrier on the country you currently are, then go into--->Settings--->Wireless and network--->Mobile Networks--->APN (access Point Names) and configure a new one typing the data you found about your overboard carrier.
That will fix it.
Also... i know its already done but... you dont need to buy the unlock code" many samsung phones can be unlocked for free Infuse can, searchf or the "how to unlock" thread next time =)
http://forum.xda-developers.com/showthread.php?t=1176886&highlight=unlock
http://forum.xda-developers.com/showthread.php?t=1093476
Hello,
I bought my HTC Sensation about a year ago on Ebay. The seller claimed the phone was purchased outright and paid off. I checked the imei and it showed clean. When I got it, I popped my Airfire sim card into it and it worked fine. A month ago, I switched to Cricket as Airfire was going out of business. Cricket made me enter my imei. It said it was bad. I called T-Mobile and they said the seller defaulted on payments. They refused to help in any way. They told me to buy the phone direct from them next time. I told them I had proof I was buying it in good faith. They didn't care and apparently have no problem punishing the victim.
Anyways, when I got my Cricket sim and popped it in, my phone said I was roaming. It has said I was roaming for a full month now. I can send and receive calls, but my data is stuck at EDGE and some of the programs don't work since the phone thinks its roaming. I need to have "data roaming" enabled for data to work. Cricket ran some tests and eventually said I needed to do a factory reset.
So, I switched from the Android Revolution rom to the ViperS 5.2.1 rom. I did a full dalvik and cache wipe and reformatted everything but the sd card. I installed the new rom and kernal. Same thing. Phone still says I am roaming. Odd thing is, when I go to manually select carrier, my options are Cricket (current carrier), Airfire (previous carrier) and TMobile (stock carrier). Also, when I am using data, it has an "E" above the data. E is what Airfire used. Is there somehow somewhere a place that the phone is storing info through wipes?
I am s-off, rooted and debranded. I sim unlocked the phone myself. I am so stuck and think that only one of the geniuses on XDA are my only hope. I have went mental spending hours and hours on this. Some XDA peeps are smarted than HTC and Cricket combined, so please help me out here.
Thanks,
Grant
SuperGrant said:
Hello,
Thanks,
Grant
Click to expand...
Click to collapse
Hi grant, this is a very odd situation your in. With my sensation when I leave the UK and connect to another EU "partner network" is the only time my phone would jump into roaming mode. Is it possible that cricket is not directly supported in your area? Maybe they rent their local connection from another carrier and thats why your getting connected as roaming? Have you tried any other sim cards to see if they come up as roaming?
Sent from my HTC Desire S using Tapatalk
Hi heavy_metal_man
I am quite sure that At&t is Cricket's parent company so all of the towers should be At&t's networks. Also, I have checked it when in other cities and I get the same message, though I haven't traveled more than 30 miles away.
The previous sim with AirFire worked fine. I also popped out the sim for Cricket and put it in my mom's phone to see if it was the sim. Her's worked fine. She got the automatic Cricket update settings right away and was not roaming. Mine never got the Cricket pop-up so I had to manually enter all of the data info. Yes, odd indeed and I am lost.
SuperGrant said:
I am quite sure that At&t is Cricket's parent company so all of the towers should be At&t's networks. Also, I have checked it when in other cities and I get the same message, though I haven't traveled more than 30 miles away.
The previous sim with AirFire worked fine. I also popped out the sim for Cricket and put it in my mom's phone to see if it was the sim. Her's worked fine. She got the automatic Cricket update settings right away and was not roaming. Mine never got the Cricket pop-up so I had to manually enter all of the data info. Yes, odd indeed and I am lost.
Click to expand...
Click to collapse
OK, the info your adding manually, is that the same info as is registered when the card is in your mums phone? Same APN etc?
Sent from my HTC Sensation using Tapatalk
heavy_metal_man said:
OK, the info your adding manually, is that the same info as is registered when the card is in your mums phone? Same APN etc?
Hi heavy_metal_man. Yup. Same info. Only difference is that the info all loads automatically on hers. I do get automated texts from Cricket when I put the sim in my phone as did she, but I had to get the APN info from Cricket the first time because it didn't auto load. I am still wondering if it is a sim issue, but I expected my mom's phone to be roaming when I put the sim in hers. I was shocked when it wasn't. She just has a free stock phone from Airfire btw. Nothing fancy and nothing done to it.
Click to expand...
Click to collapse
SuperGrant said:
heavy_metal_man said:
OK, the info your adding manually, is that the same info as is registered when the card is in your mums phone? Same APN etc?
Click to expand...
Click to collapse
Hi heavy_metal_man. Yup. Same info. Only difference is that the info all loads automatically on hers. I do get automated texts from Cricket when I put the sim in my phone as did she, but I had to get the APN info from Cricket the first time because it didn't auto load. I am still wondering if it is a sim issue, but I expected my mom's phone to be roaming when I put the sim in hers. I was shocked when it wasn't. She just has a free stock phone from Airfire btw. Nothing fancy and nothing done to it.
Click to expand...
Click to collapse
Hmm. Are those 3 carriers the only ones available to you? I think the imei may be key here, if cricket know its a T-Mobile phone they may register that you are roaming. I think your previous carrier (airfire) was a Virtual mobile network, much like giffgaff in the UK ( which runs on the o2 network.) As such they may not have inforced the same imei policy's that cricket does. But this is just a hunch as I am on UK networks and we do things much differently. If you could ask about any friends and colleges that have different carrier simcards from our previous 3 you could gauge what carriers your phone is compatible with.
Worst case scenario you could maybe buy another broken htc sensation and perform a motherboard swap. This would solve your imei issue, assuming that it was the primary issue. But check the simcards first and report back
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
Hmm. Are those 3 carriers the only ones available to you? I think the imei may be key here, if cricket know its a T-Mobile phone they may register that you are roaming. I think your previous carrier (airfire) was a Virtual mobile network, much like giffgaff in the UK ( which runs on the o2 network.) As such they may not have inforced the same imei policy's that cricket does. But this is just a hunch as I am on UK networks and we do things much differently. If you could ask about any friends and colleges that have different carrier simcards from our previous 3 you could gauge what carriers your phone is compatible with.
Worst case scenario you could maybe buy another broken htc sensation and perform a motherboard swap. This would solve your imei issue, assuming that it was the primary issue. But check the simcards first and report back
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Hmm... There are only 3 carriers available. Should there be more? It's not tied to the sim? Everyone I know either still has Airfire and plans on switching to Cricket or has cdma so I have been out of luck with trying another sim. The only other thing I thought about was 4ext recovery. No matter what I flash; roms, kernals, firmware or radios, the recovery always survives of course. So, if the previous carriers are surviving the flashes, perhaps there is a place on the phone like the recovery where they are surviving.
SuperGrant said:
Hmm... There are only 3 carriers available. Should there be more? It's not tied to the sim? Everyone I know either still has Airfire and plans on switching to Cricket or has cdma so I have been out of luck with trying another sim. The only other thing I thought about was 4ext recovery. No matter what I flash; roms, kernals, firmware or radios, the recovery always survives of course. So, if the previous carriers are surviving the flashes, perhaps there is a place on the phone like the recovery where they are surviving.
Click to expand...
Click to collapse
Its unlikely to be to do with the recovery, no reason for it to keep anything like that. It's most likely the phones imei at this point, though im unsure as to why this was not an issue for airfire.
Do you know what firmware version you have? Have you flashed 3.33 by yourself?
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
Its unlikely to be to do with the recovery, no reason for it to keep anything like that. It's most likely the phones imei at this point, though im unsure as to why this was not an issue for airfire.
Do you know what firmware version you have? Have you flashed 3.33 by yourself?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yup, I flashed 3.33 universal after doing a super Cid. Well, maybe its time to just get a new phone, although I would really like to figure out this problem first. I am not the kind of person who can just drop things, lol.
SuperGrant said:
Yup, I flashed 3.33 universal after doing a super Cid. Well, maybe its time to just get a new phone, although I would really like to figure out this problem first. I am not the kind of person who can just drop things, lol.
Click to expand...
Click to collapse
I know how you feel. Maybe its because they cricket know the sensation 4g is a T-Mobile device and force you into roaming mode by default. I think its possible to overwrite the devices mid and cid, flash a sensation XE rom and effectively have a sensation XE. But such things can be quite dangerous and i couldn't say for definite if it would work to fix your issue :/ (not recommending anyone tries this without proper research and understanding :/)
Can you get access to another cricket sim without a contract? Just for testing?
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
I know how you feel. Maybe its because they cricket know the sensation 4g is a T-Mobile device and force you into roaming mode by default. I think its possible to overwrite the devices mid and cid, flash a sensation XE rom and effectively have a sensation XE. But such things can be quite dangerous and i couldn't say for definite if it would work to fix your issue :/ (not recommending anyone tries this without proper research and understanding :/)
Can you get access to another cricket sim without a contract? Just for testing?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I believe I have already done that. When I go into info about my phone, it says Sensation XE. It also registers as Sensation XE in the Google play store. I was thinking about telling Cricket to send me a new sim. Otherwise, I have no access to one at this time.
SuperGrant said:
I believe I have already done that. When I go into info about my phone, it says Sensation XE. It also registers as Sensation XE in the Google play store. I was thinking about telling Cricket to send me a new sim. Otherwise, I have no access to one at this time.
Click to expand...
Click to collapse
I think that it would be your best bet, although your device is probably showing up on the play store as an XE because of its build.prop from your custom rom, not any advanced MID changes. although you can check by using the command
Code:
fastboot getvar all
this will show your your mid, cid and your imei among other things.
SuperGrant said:
I believe I have already done that. When I go into info about my phone, it says Sensation XE. It also registers as Sensation XE in the Google play store. I was thinking about telling Cricket to send me a new sim. Otherwise, I have no access to one at this time.
Click to expand...
Click to collapse
I've worked it out! Its a frequency issue. Cricket apparently only support cdma frequency's, while the sensation only uses gsm frequency's. So in order to connect your phone is bunnying onto a local gsm service, which is then redirecting you to cricket. Hence the roaming! If you want off the data roaming you will need to either swap to a different phone carrier or buy a cdma phone
Sent from my Nexus 7 using Tapatalk
Hi heavy_metal_man,
Cricket did use CDMA for most of the time, but they have switched to GSM. They send a sim now and are trying to switch all of their old customers to GSM. What I am having trouble figuring out is what frequencies they use. Perhaps my phone is not quite compatible. I am having trouble with that as well. GSM arena, Phonescoop and the other major sites kind of have different data as far as my phone goes. My phone is called "HTC Sensation 4G" as far as I know. Yet, they list no 4g capability or frequencies. Of course, I believe that would only affect data and I still should not show as roaming.
I have been unable to figure out fastboot since switching to the viper rom. It doesn't use usb mass storage anymore. It uses the new system in which the whole phone is recognized as a storage device by the computer. Forgot what they called it. I wish they hadn't changed it, and apparently Windows 7 should recognize it by default, but it does not. I am sure if I get enough time to put into it I will figure out how to use the fastboot commands again.
I am ready to give up and just get a new phone pretty soon. Would be nice if Cricket's customer service wasn't so worthless. It could still be the IMEI or something on their end that I can do nothing about but they have failed to provide any solution.
SuperGrant said:
Hi heavy_metal_man,
Cricket did use CDMA for most of the time, but they have switched to GSM. They send a sim now and are trying to switch all of their old customers to GSM. What I am having trouble figuring out is what frequencies they use. Perhaps my phone is not quite compatible. I am having trouble with that as well. GSM arena, Phonescoop and the other major sites kind of have different data as far as my phone goes. My phone is called "HTC Sensation 4G" as far as I know. Yet, they list no 4g capability or frequencies. Of course, I believe that would only affect data and I still should not show as roaming.
I have been unable to figure out fastboot since switching to the viper rom. It doesn't use usb mass storage anymore. It uses the new system in which the whole phone is recognized as a storage device by the computer. Forgot what they called it. I wish they hadn't changed it, and apparently Windows 7 should recognize it by default, but it does not. I am sure if I get enough time to put into it I will figure out how to use the fastboot commands again.
I am ready to give up and just get a new phone pretty soon. Would be nice if Cricket's customer service wasn't so worthless. It could still be the IMEI or something on their end that I can do nothing about but they have failed to provide any solution.
Click to expand...
Click to collapse
Sorry for my delayed reply, I noticed that cricket swapped out to gsm and I discovered that their gsm tech is actually supplied at&t as they bought them out.
So I looked at their coverage map for the area airfire operated and I noticed that they had 2 or 3 area that were only providing 3g support via a partner, so I assume that would put you into roaming. It might be worth a look at their map and confirm if you reside on one of these black areas ?
Sent from my HTC Desire S using Tapatalk
Hi, I've got a Z3 dual D6633 which I want to use with an EE SIM in the UK. I've tried a cut down microsim and been into the EE shop and tried one of their nano SIMs but both don't work correctly in the phone.
The cut down SIM makes a service phone.android.com or something like that continually crash and doesn't connect to the network.
The one I tried in the shop just doesn't connect to the network.
This is on 23.0.F.1.74 and .82 I noticed in the release notes for .82a fix for Yoga SIMs in Russia but don't know what the problem there was, but wonder if it is linked. All other UK Sims work including 3, Lyca, giffgaff, Vodafone, virgin just not EE. has anyone got an EE one working or had similar problems?
I did notice that an app/widget I use called phono to show network info and signal strength usually shows the IMEI when no SIM inserted or the MSISDN, however with the non-working EE SIM it just shows 00000 - not sure which field it is getting wrong. Oh and yes the SIMs work fine in all other phones I've tried.
I do need to try more tests on factory reset and removing phono etc but so far it looks to be a firmware incompatibility with EE Sims.
OK, so I did a few more tests and got hold of another nano SIM on EE.
So it looks like the 23.0.F.1.74 firmware does not like EE SIMs and the phone application constantly crashes. On the later .82 firmware it works fine. I was mislead a bit by going into an EE store and trying a SIM - they must have given me an un-provisioned SIM to try. I stupidly assumed they would have actually given me a SIM that worked, doh!
I'm experiencing something similar here. I have the D6633, bought in UK, now I am in Brazil and the phone works great except that it won't connect to the 4G/3G/2G/LTE network. I can make calls, send sms normal. But internet only over wi-fi.
I called my operator, they say the phone is configured correctly, I tried my brother's sim card from another operator and the same happens.
So, the phone is clearly unlocked, if not it wouldn't recognize the sim cards at all. But no connection to the internet...
Any suggestions? I already did four factory resets, I recovered the Rom using sony software...
Same issue
adrenalize_ said:
OK, so I did a few more tests and got hold of another nano SIM on EE.
So it looks like the 23.0.F.1.74 firmware does not like EE SIMs and the phone application constantly crashes. On the later .82 firmware it works fine. I was mislead a bit by going into an EE store and trying a SIM - they must have given me an un-provisioned SIM to try. I stupidly assumed they would have actually given me a SIM that worked, doh!
Click to expand...
Click to collapse
Hello, I have the exact same problem. How did you get the firmware .82/for what country? Is everything working well with it? Really appreciate your guidance.
I had the same problem with the EE sim card, ended up sending the phone back.
fabiooli said:
I'm experiencing something similar here. I have the D6633, bought in UK, now I am in Brazil and the phone works great except that it won't connect to the 4G/3G/2G/LTE network. I can make calls, send sms normal. But internet only over wi-fi.
I called my operator, they say the phone is configured correctly, I tried my brother's sim card from another operator and the same happens.
So, the phone is clearly unlocked, if not it wouldn't recognize the sim cards at all. But no connection to the internet...
Any suggestions? I already did four factory resets, I recovered the Rom using sony software...
Click to expand...
Click to collapse
Just a thought, but is it definitely a 6633 and not some other variant which perhaps doesn't work in your country/network?
pconcha said:
Hello, I have the exact same problem. How did you get the firmware .82/for what country? Is everything working well with it? Really appreciate your guidance.
Click to expand...
Click to collapse
I purchased my D6633 from Saudi Arabia and the 23.0.F.1.82 update came as an OTA notification about a week ago.
If you look in this thread http://forum.xda-developers.com/z3/general/d6633-z3-dual-updated-to-23-0-f-1-82-t2929352/ it mentions that someone thinks the update has only been released for Saudi and Brazil - I assume it is for Europe as well as one of the release notes says a problem with Russian Yota SIMs has been fixed. I think there are also links to the firmware in there although I've not looked that hard as I got the OTA. I guess it might still in my memory - anyone know where Sony stick their OTAs?
Seems to work fine so far - no noticeable difference - well other than EE SIMs now work!
jadaress1 said:
I had the same problem with the EE sim card, ended up sending the phone back.
Click to expand...
Click to collapse
Ah, shame as it looks like the update might have fixed it. I was thinking I might have to go to another handset too (The Samsung G900FD is OK if you can put up with touchwiz and other Samsung "features"!!)
fabiooli said:
I'm experiencing something similar here. I have the D6633, bought in UK, now I am in Brazil and the phone works great except that it won't connect to the 4G/3G/2G/LTE network. I can make calls, send sms normal. But internet only over wi-fi.
I called my operator, they say the phone is configured correctly, I tried my brother's sim card from another operator and the same happens.
So, the phone is clearly unlocked, if not it wouldn't recognize the sim cards at all. But no connection to the internet...
Any suggestions? I already did four factory resets, I recovered the Rom using sony software...
Click to expand...
Click to collapse
Hmmm, sounds like another issue as with mine the EE SIM caused the phone.apk to constantly crash/restart.
Did the data work OK in the UK?
As you can make calls/SMS I assume you are at least on a 2G network which should still give you (very slooow) data - It does sound more like an APN issue - or something else. I know you said you checked with your operator what their APN settings should be (just my experience with operator customer support lines) - but I would try and have a look yourself - and maybe list your APN settings and operator and someone may spot something.
I have seen a couple of phones / operators where the "APN type" in the APN settings needs specific settings - its down the bottom and often isn't mentioned when people get the settings. For example in my current settings I have "default,hipri,dun,supl" for Virgin mobile in the UK.
You may want to search XDA/Google or start your own thread which might get more reads/replies
adrenalize_ said:
You may want to search XDA/Google or start your own thread which might get more reads/replies
Click to expand...
Click to collapse
...or try some of the things which have already been suggested and post your findings !
adrenalize_ said:
Hmmm, sounds like another issue as with mine the EE SIM caused the phone.apk to constantly crash/restart.
Did the data work OK in the UK?
As you can make calls/SMS I assume you are at least on a 2G network which should still give you (very slooow) data - It does sound more like an APN issue - or something else. I know you said you checked with your operator what their APN settings should be (just my experience with operator customer support lines) - but I would try and have a look yourself - and maybe list your APN settings and operator and someone may spot something.
I have seen a couple of phones / operators where the "APN type" in the APN settings needs specific settings - its down the bottom and often isn't mentioned when people get the settings. For example in my current settings I have "default,hipri,dun,supl" for Virgin mobile in the UK.
You may want to search XDA/Google or start your own thread which might get more reads/replies
Click to expand...
Click to collapse
It was working fine there. Here It apparently could not download APN settings, so I installed an APN APP and now it works fine!!!
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
poldie said:
Just a thought, but is it definitely a 6633 and not some other variant which perhaps doesn't work in your country/network?
Click to expand...
Click to collapse
Working great now!!!! I used an APN APP form PlayStore
adrenalize_ said:
I purchased my D6633 from Saudi Arabia and the 23.0.F.1.82 update came as an OTA notification about a week ago.
If you look in this thread http://forum.xda-developers.com/z3/general/d6633-z3-dual-updated-to-23-0-f-1-82-t2929352/ it mentions that someone thinks the update has only been released for Saudi and Brazil - I assume it is for Europe as well as one of the release notes says a problem with Russian Yota SIMs has been fixed. I think there are also links to the firmware in there although I've not looked that hard as I got the OTA. I guess it might still in my memory - anyone know where Sony stick their OTAs?
Seems to work fine so far - no noticeable difference - well other than EE SIMs now work!
Click to expand...
Click to collapse
I see. Mine is the d6633 but it is customized for HK. I have not received the OTA upgrade yet. I have checked xperifirm as they may have it but will wait for the OTA upgrade. Sony must be releasing soon.
Thank you for replying! I am using Vodafone in the meantime, but want to go back to my EE plan!
about dual sim connectivity
can anyone tell me which sim card slot support 2G, 3G and 4G or LTE
I heard that 1 slot support only 3G and 4G
and other one is support 2G & 3G so kindly confirm me what is actual.
thanks
arfan.chatha said:
can anyone tell me which sim card slot support 2G, 3G and 4G or LTE
I heard that 1 slot support only 3G and 4G
and other one is support 2G & 3G so kindly confirm me what is actual.
thanks
Click to expand...
Click to collapse
For mine, on my networks here in Australia, I can assign 4G LTE to any sim, however, that makes the other sim 2G only (GSM).
The other option is to have both at 3G (WCDMA/HSPA).
If you assign 4g to sim one that work only for 4g or like other phones "LTE(preference)/WCDMA/GSM"
4g not available automatically search 3G if 3G not available automatically search 2G?
Assume second sim is on 2g
arfan.chatha said:
If you assign 4g to sim one that work only for 4g or like other phones "LTE(preference)/WCDMA/GSM"
4g not available automatically search 3G if 3G not available automatically search 2G?
Assume second sim is on 2g
Click to expand...
Click to collapse
Yes, your 4G sim slot will fall back onto 3G and 2G as per expected for most handsets.
help needed
sephstyler said:
For mine, on my networks here in Australia, I can assign 4G LTE to any sim, however, that makes the other sim 2G only (GSM).
The other option is to have both at 3G (WCDMA/HSPA).
Click to expand...
Click to collapse
I just got a 6633 through kogan and i am having real trouble getting it to connect to optus network with iinet and truphone simcards. Does anyone know if i need to update any settings or firmware from factory to make it compatible. I can see iinet and truphone lte networks (which i assume is the optus 4g network) when searching manually but the phone wont connect. Sims work in a mates iphone6 without a problem.
Don't suppose anyone knows how to get rid of the #sim card icon on the statusbar?
adrenalize_ said:
I purchased my D6633 from Saudi Arabia and the 23.0.F.1.82 update came as an OTA notification about a week ago.
If you look in this thread http://forum.xda-developers.com/z3/general/d6633-z3-dual-updated-to-23-0-f-1-82-t2929352/ it mentions that someone thinks the update has only been released for Saudi and Brazil - I assume it is for Europe as well as one of the release notes says a problem with Russian Yota SIMs has been fixed. I think there are also links to the firmware in there although I've not looked that hard as I got the OTA. I guess it might still in my memory - anyone know where Sony stick their OTAs?
Seems to work fine so far - no noticeable difference - well other than EE SIMs now work!
Click to expand...
Click to collapse
Have you managed to root it? I rooted the 23.0.1.f.0.96 firmware for my Z3 D6633, but after a while (half a day) it starts to reboot frequently, and Google Play stops working (can browse apps, but not download them, as the download bar never progresses).
Also, my EE sim seems to work, but the phone still shows it as 'Sim 1 0000000' whereas other sims simply appear as sim 1 and sim 2.
I am wondering if I should just downgrade back to 23.0.F.1.74 and move from EE to Vodafone or 3...
Ah, work forced a BlackBerry (yuck!) on me and I've since sold the D6633.
So something weird has been happening since purchasing my mint conditioned note 3 on Sprint. Every time I was inside my home, my note 3 would lose LTE and stay on 3g. I was looking for answers and not finding a single thing. I came up with a solution myself and here is where the explaining begins. Be careful when purchasing a phone online as some are international phones (which we know). I happened to purchase an n900p note 3 model and it was actually made in China but my signal radios were set to Japan. If you are in the USA and using Sprint then do the following:
-Download from the play store an app called Samsung phone info
-After the install is complete open the app and open the menu on the left side
-Select Secret Codes
-Scroll down to settings and select Launch 0
-Choose Phone Information
-In the upper right hand corner there are 3 dots, choose radio baseband and select USA from Japan
-Enjoy LTE
Sent from my Note 3 using XDA Free mobile app
i am trying to use a n900p (sprint) unlocked phone with a gsm carrier in india.
in the *#0011# dialer menu it shows imei certi fail.
i have been searching for the 'imei certi fail -9' fix.
i searched on google but couldnt find a satisfying perfect solution.
will appreciate any help possible.
thanks.
aaki_rocker said:
i am trying to use a n900p (sprint) unlocked phone with a gsm carrier in india.
in the *#0011# dialer menu it shows imei certi fail.
i have been searching for the 'imei certi fail -9' fix.
i searched on google but couldnt find a satisfying perfect solution.
will appreciate any help possible.
thanks.
Click to expand...
Click to collapse
Are you rooted? Or on the default ROM for your device? The problem could be sprint uses CDMA not GSM, GSM is for devices without sim cards but I think is used on sprint for the sole purpose of emergency calls
Sent from my Note 3 using XDA Free mobile app
aaki_rocker said:
i am trying to use a n900p (sprint) unlocked phone with a gsm carrier in india.
in the *#0011# dialer menu it shows imei certi fail.
i have been searching for the 'imei certi fail -9' fix.
i searched on google but couldnt find a satisfying perfect solution.
will appreciate any help possible.
thanks.
Click to expand...
Click to collapse
But do you still have IMEI and Baseband version?
(look for the Baseband version and IMEI in the Phone INFO app).
ebs512 said:
Are you rooted? Or on the default ROM for your device? The problem could be sprint uses CDMA not GSM, GSM is for devices without sim cards but I think is used on sprint for the sole purpose of emergency calls
Sent from my Note 3 using XDA Free mobile app
Click to expand...
Click to collapse
the phone is rooted and running close to stock tw 4.4.4 rom.
true that sprint is a cdma carrier. but the n900p has all the gsm basebands which my carrier provides.
also phone has been internationally unlocked using sprint unlocker. (ssu.apk.)
vndnguyen said:
But do you still have IMEI and Baseband version?
(look for the Baseband version and IMEI in the Phone INFO app).
Click to expand...
Click to collapse
baseband is nk4 and my imei number is shown which starts from 99.
so i think everything is pretty normal here.
i am just concerned about the phone not activating and it refuses to register to any network. i've tried 3 different indian carrier sim cards.
aaki_rocker said:
the phone is rooted and running close to stock tw 4.4.4 rom.
true that sprint is a cdma carrier. but the n900p has all the gsm basebands which my carrier provides.
also phone has been internationally unlocked using sprint unlocker. (ssu.apk.)
baseband is nk4 and my imei number is shown which starts from 99.
so i think everything is pretty normal here.
i am just concerned about the phone not activating and it refuses to register to any network. i've tried 3 different indian carrier sim cards.
Click to expand...
Click to collapse
The phone might not be compatible with that specific carrier or you might have to take your sim card to the carrier and have them activate it but who knows.I took mine to Sprint and the guy asked me where I got the phone, I told him online. The problem with me having a Japan radio baseband set as default my LTE signal gets lost when I go in a building but when I'm outside, it picks back up again. If I switch the radio to USA I get 4g but then can't send/receive MMS. After a period of time on the USA baseband, it will completely lose signal and show up a black empty service in my status bar
Sent from my Note 3 using XDA Free mobile app
ebs512 said:
The phone might not be compatible with that specific carrier or you might have to take your sim card to the carrier and have them activate it but who knows.I took mine to Sprint and the guy asked me where I got the phone, I told him online. The problem with me having a Japan radio baseband set as default my LTE signal gets lost when I go in a building but when I'm outside, it picks back up again. If I switch the radio to USA I get 4g but then can't send/receive MMS. After a period of time on the USA baseband, it will completely lose signal and show up a black empty service in my status bar
Sent from my Note 3 using XDA Free mobile app
Click to expand...
Click to collapse
is there any permanent solution to get a signal ?
aaki_rocker said:
is there any permanent solution to get a signal ?
Click to expand...
Click to collapse
Not if the sim card isn't working I would contact the carrier and see if they can get your sim card entered properly for service to your device
Sent from my Note 3 using XDA Free mobile app
I got this phone yesterday. It is currently running Android 6.0.1 and the status bar keeps saying "No service". I have tried using 5.1.1, as well - same message.
When I first got the phone, I tried rooting 6.0.1 with the latest SuperSU but resulted in a bootloop so I reset the phone + unrooted it with the Nexus Root Toolkit.
I have tried using my SIM on another person's phone - works perfectly.
I have tried using another person's SIM on my phone - "No service".
In the "About phone" section -> Status -> SIM status, the phone recognizes my phone number and IMEI number. So my phone knows there is a SIM there and everything, it just can't connect to the phone network for some reason.
What could possibly be the problem?
Has the imei been blacklisted? Have you tried searching for networks?
i been getting the same thing on and off since i had mine and seem stuck as well
What network are you using?? If its CDMA you have to get the imie# activated into the system by your wireless provider... So any Verizon/sprint for example you need to get that activated in their system.. Only GSM is plug & play at&t/t mobile
Sent from my Nexus 6 using Tapatalk
audit13 said:
Has the imei been blacklisted? Have you tried searching for networks?
Click to expand...
Click to collapse
My IMEI is not blacklisted according to protectyourdata.ca's IMEI checker.
gothicasshole said:
What network are you using?? If its CDMA you have to get the imie# activated into the system by your wireless provider... So any Verizon/sprint for example you need to get that activated in their system.. Only GSM is plug & play at&t/t mobile
Click to expand...
Click to collapse
I am using Bell. It is HSPA I think. The SIM card works with my Oneplus One, which hasn't had its IMEI # activated on their system.
I've decided to just return it and get a new one.
anon5 said:
My IMEI is not blacklisted according to protectyourdata.ca's IMEI checker.
I am using Bell. It is HSPA I think. The SIM card works with my Oneplus One, which hasn't had its IMEI # activated on their system.
I've decided to just return it and get a new one.
Click to expand...
Click to collapse
Hspa is a GSM technology.. Make 100% sure the nexus supports your radio bands.. I would honestly either try a nother sim card or call customer service.. Perhaps it could be a defective unit. Also make sure it fits 100% in the sim tray. I had that issue once with a sim that didn't quite snap into the sim tray
Sent from my Nexus 6 using Tapatalk
gothicasshole said:
Hspa is a GSM technology.. Make 100% sure the nexus supports your radio bands.. I would honestly either try a nother sim card or call customer service.. Perhaps it could be a defective unit. Also make sure it fits 100% in the sim tray. I had that issue once with a sim that didn't quite snap into the sim tray
Click to expand...
Click to collapse
I just checked and Bell requires phones to be 850 or 1900 MHz compatible. The Nexus 5 supports these frequencies. I tried my sister's and friend's sim cards and it still doesn't work.
anon5 said:
I just checked and Bell requires phones to be 850 or 1900 MHz compatible. The Nexus 5 supports these frequencies. I tried my sister's and friend's sim cards and it still doesn't work.
Click to expand...
Click to collapse
You might have a defective sim reader
Also get a can of electronics spray air.. Blow out the sim port. Don't use your mouth as saliva can corrode the connector and they can claim water damage
Sent from my Nexus 6 using Tapatalk
I use a nexus 5 on the bell network and everything works perfectly.