I've got a At&T i747. Unlocked (through the *#197328640# menus) and rooted it. Loaded it with the GOODNESS ATT v2.4 ROM. It worked OK several days, but today the phone stopped issuing and receiving calls without any visible reason and I did not change anything in the settings. When I dial a number, I hear one beep in the headphone then, the phone writes the call is ended. Same is when I call to it from another phone: the calls ends in seconds without connection. Signal indicator shows one or more bars. I have tried to insert another working SIM, but now there is no signal indicator at all. (I tested both SIMS on another phone of mine: both are 100% OK in and out).
The phone does not say there is no SIM in both cases and does not request unlock code.
I have cleared the cache, the Dalvik: no change.
I have re-flashed the ROM: same.
I have changed the Kernel: same.
I have made factory reset: same.
My feeling it is something connected to unlock or modem, but I don't know what tools can check and confirm it.
Does anyone have idea what can it be? And what should I do?
mess18 said:
I've got a At&T i747. Unlocked (through the *#197328640# menus) and rooted it. Loaded it with the GOODNESS ATT v2.4 ROM. It worked OK several days, but today the phone stopped issuing and receiving calls without any visible reason and I did not change anything in the settings. When I dial a number, I hear one beep in the headphone then, the phone writes the call is ended. Same is when I call to it from another phone: the calls ends in seconds without connection. Signal indicator shows one or more bars. I have tried to insert another working SIM, but now there is no signal indicator at all. (I tested both SIMS on another phone of mine: both are 100% OK in and out).
The phone does not say there is no SIM in both cases and does not request unlock code.
I have cleared the cache, the Dalvik: no change.
I have re-flashed the ROM: same.
I have changed the Kernel: same.
I have made factory reset: same.
My feeling it is something connected to unlock or modem, but I don't know what tools can check and confirm it.
Does anyone have idea what can it be? And what should I do?
Click to expand...
Click to collapse
Looks I have found the heeling, but I still do not know what cased the "sickness": I just made again the *#197328640# unlock until I've got the "successful" result. Now both SIMs work OK. and calls can be done in and out.
Does anybody experienced such a problem with unlocking a phone using this method? Is it a temporary solution?
Should I just buy a code from AT&T and forget the whole thing?
Related
Ok this may have been asked before but i havent really gotten the understanding that im trying to. so ill ask specifically. i have root, have installed 3 or 4 different roms CM6, stock 2.1, modified 2.1(currently 2.2 froyo from t-mobile). does this mean my phone is also "UNLOCKED" or is there something else im missing? also i am having an issue where immediately after i turn my phone on, i can place phone calls. but after a few minutes, i cant make a call. it just sits there and then times out unless i shut the phone off and back on again.
Simple Mobile $60 plan
Mt3gs
rooted
2.2 froyo OTA
I was thinking 'Unlocked' meant it was able to be used on other carriers?
i was too but im not sure if thats the issue. because the phone was originally a t-mobile phone but i bought a Simple Mobile sim. so now the phone is actin funny about calls. the internet is programmed and works fine. mms is sketchy. but phone calls act like the phone drops the carrier after a while and i cant scan for carriers (says no carrier found) until i reboot it. also i cant enter airplane mode fully when that happens. sometimes i can get incoming calls but cant dial out. other times, incoming calls ring then go to vm without the phone ringin at all
mrmagiq said:
i was too but im not sure if thats the issue. because the phone was originally a t-mobile phone but i bought a Simple Mobile sim. so now the phone is actin funny about calls. the internet is programmed and works fine. mms is sketchy. but phone calls act like the phone drops the carrier after a while and i cant scan for carriers (says no carrier found) until i reboot it. also i cant enter airplane mode fully when that happens. sometimes i can get incoming calls but cant dial out. other times, incoming calls ring then go to vm without the phone ringin at all
Click to expand...
Click to collapse
Rooting your phone doesn't unlock it, so technically your phone is still sim/carrier locked to T-Mobile. Simple Mobile may have been able to work around SOME of those locks, but you probably won't eliminate those calling issues until you get it the unlock code from t-mobile. You also might try hack-unlocking it, the unlockr I've heard is good for that kind of stuff.
Rooting just means you gained superuser access to the phone, vs regular end user access. Rooting allows custom roms and overclocking and that sort of stuff.
Hi Guys.
So received the phone on Thursday, Friday I did a sim swap from my normal sized sim to a micro sim. I waited the whole day but the phone didn't have any network access.
Today when I woke up I I switched the phone on hoping that everything will be fine, thinking the simswap just hasn't gone through yet, still no network access. I took out the swim from the phone and switched with my ipad, the sim was working in the ipad, and the ipads sim also didnt give the phone network access.
In the top right corner it shows full bars in grey, cant make emergency calls or anyhting.
In the about section of the phone, I have ALL the details present, baseband version is there, kernel version is there.
In Status section, network is unkown, signal strenght is -83 dbm 15 asu, network type unkown, service state is out of service, and the rest is also present.
I thought the phone didn't properly register to a network, so went into settings - wireless networks - more settings - mobile networks, but it gives me a insert sim card message.
The phone is reading the simcard fine because it asked for the PIN when switching on.
When trying to make a call I get, it says "Not registered on network"..
So what am I to do? Vodacom can only pickup the phone and exchange it on Tuesday, so was hoping that this might just be a software issue that can be resolved by a flash.
I have tried resetting / hard resetting the phone numerous times.
Its the Note 2 N7105 LTE Version
Any help would be highly appreciated.
Try this
http://forum.xda-developers.com/showthread.php?t=2014982
If you bought it new dont flash anything and send it back. At this stage you dont need to make things complicated
Sent from my GT-N7100 using xda app-developers app
dr.ketan said:
Try this
http://forum.xda-developers.com/showthread.php?t=2014982
Click to expand...
Click to collapse
Great thanks.
I tried this but didn't solve the problem. I am using the same sim that I received from the carrier with the phone they shipped.
I have played around in the menu however, maunally setting the band and so forth, just restarted and started receiving sms, so basically if not for your post I would not have solved this.
Thanks
I have isolated the problem.
In the service menu - UMTS - DEBUG SCREEN - PHONE CONTROL - NETWORK CONTROL - SERVICE DOMAIN
There are 3 options
1 CS + PS
2 CS ONLY
3 PS ONLY
CS seems to be for making calls and sending smses
PS seems to be for data connections (When this is selected, the bars are replaced with a circle with a stripe through)
I Could be wrong with the above, so anyone with experience please shed some light
Those 2 work seperately, but when CS + PS is selected, none of them work? Very odd, anyone know what the issue could be?
anyone?
Hi, I recently started having trouble with my gf's phone (Nexus 4 running lollipop 5.0, lte enabled, tmo). It started shortly after I enabled a SIM lock pin on the sim, but not sure if that's the cause or not... The phone started to intermittently drop signal, and would not make calls (it would just appear to be dialing, but you'd hear no ringing and never connect). When I'd restart the phone, I could usually make a call. I tried to fix it by restoring everything the stock image, rechecking the apn, making sure stock radio was installed, etc, but the problem persisted and eventually got to the point that voice calls did not work at all. LTE and data worked to get onto the internet, but once a call was attempted to be made, it'd lose all signal. I discovered eventually that if I switched off lte/4g/3g, and only kept gsm 2g on, I could make a voice call. Next I tried her SIM card in my phone (Note 2 on Android 4.4, t-mobile) and as soon as I put her sim in, my phone started doing the same thing. After switching back to my SIM (that was working just fine, before), now MY phone is stuck with the same problem! (Can only make calls with just 2g enabled). I'm at a total loss. Has anyone experienced anything similar, or do you have possible solutions/ideas on how to fix this?
Solved
For anyone who may be having the same problem, here is how I solved it. I picked up a new sim card from t-mobile, flashed a stock rom via odin (with the sim card not installed), loaded rom, and installed sim, loaded correct apn. Everything works as it should now.
Reply
What Brand was her SIM?
Hi all,
My problem is that my Galaxy S3 (i747M) cannot make or receive phone calls*, but I can send or receive most SMS**, and my LTE data is fine***. I've tested to ensure it's not my account with Rogers, or my SIM card. I took my SIM card and put it in two other phones, and both worked just fine (one Rogers, one Telus). Putting their SIMs into my phone and the same problem as with my own SIM in my phone. I have unlocked my S3 using the 4.2 trick, but I didn't have this problem back then. I'm assuming this isn't causing me issues now.
I used asterisks because each of the above has some additional details:
* I cannot reliably make and receive phone calls. For example, I can try calling the same phone number (home) 10 times, and it may only go out once. From my home phone I can try calling my cell phone 25 times and only get through once. Every time my calls out fail, it either sits at "Dialing..." for 30 seconds before ending in "Call Ended 0:00" or just immediately drops the call without the 30 seconds of "Dialing...".
** Most of the time I can send and receive SMS from any other cell phone. Occasionally a message won't send out even though I have 4/5 signal bars. Resending the message works. Not sure if this is related to my issues with calling.
*** LTE data is fine (using LTE APN). Switching away from LTE to just 4G/H+ and data is a bit spotty. Sometimes it connects, sometimes it doesn't. LTE always connects just fine.
I've tried all sorts of flashing and reflashing:
- problem started when I was on S3Rx 4.0, but I never thought much of it because most calls went through fine
- problem got worse when I was on Lollipop (CyanideL), progressively so
- used Odin to flash stock NF2 (downloaded from Sammobile site), was no different than when I was on Lollipop (CyanideL)
- used Kies to flash stock N__ (forgot exactly which one), still no different
- flashed different bootloaders and modems
- while in stock NF2 firmware, went into *#2263# and made sure it was set to Automatic.
So any ideas what problem this is? I just find it extremely odd that calls almost always fail, yet SMS and data aren't a problem. Of course, when my SIM is in another phone (Nexus 5 on Telus, Galaxy S5 on Rogers) I was able to do everything without any problems: calls, SMS, and data.
Thoughts as to what this could be? Is this a hardware issue? If it's software, what could it be? My warranty's out and I'm willing to flash anything or pop the phone open (already have to make sure antenna isn't disco'd).
Thanks!
Have you tried the fob1 firmware? It's the latest kk release for the Canadian s3.
Yup, that's the firmware I'm currently on. Downloaded it from SamMobile, flashed via Odin. I'm literally running the stock firmware right now, no root, only TWRP as recovery so I can more easily flash any modems or bootloaders (vs using fastboot).
OK, so further to this issue, I contacted Rogers technical support. Spent about half an hour on the phone with the tech, went through a few things:
1. He reset my voice account, didn't help
2. Had me search in the "Network Operators" list, no networks ever show up
3. Had me use my old phone (Nexus S, network unlocked) to ensure that it's not my account. All tests with the Nexus S went fine.
4. Had me test different network bands. Bingo!
The phone can place and receive calls when I set the network mode to 2G only (or GSM only). 3 out of 3 calls came in, 3 out of 3 calls went out. Then again later we tested incoming and outgoing calls, still on the 2G network.
So technically problem solved, but realistically not really. I am able to get voice, text, and data (solved!), but I'm paying for a LTE data package and should at least be getting 3G mad.
Any idea why my phone would be working on the 2G network and not on the other ones (3G, H+, LTE)?
This is crazy but the baseband and modem are one fob1? I know you said you flashed a stock rom but it may be worth checking.
My niece is using an unlocked bell s3 on Rogers and she has no problem with voice, data, or text when setting the network to wcdma only or wcdma/LTE.
Yes! Both Baseband (modem) and bootloader are the same. I just downloaded Phone Info (Samsung) to check this, and they both report being FOB1.
Now here's something that's irking me quite a bit. I only just discovered this and do not know if it is of consequence to my problem: I have no PDA or CSC version and Latest Firmware is reporting "Not Found" in the Firmware tab of Phone Info. I've attached a screenshot so you can all see what I mean. Is that normal?
Is phone running a custom rom?
That's right, I just restored a NANdroid of CyanideL (5.1.1).
So this also happens on a stock fob1 rom too?
I am almost tempted to say it may be a hardware issue.
That's right. This happens with a custom ROM (e.g. CyanideL, 5.1.1) as well as a stock ROM that's been freshly flashed via Odin (FOB1, 4.4.2). When flashing with Odin, I'm doing a full wipe via TWRP. Wiping /data partition as well.
I'm inclined to believe this is also a hardware issue, but it just seems bass ackwards in that I can get everything (minus LTE) working while on 2G, but I lose voice access if I move up beyond 2G. I could understand if I couldn't get any voice, SMS, or data, but that going down to 2G solves all my problems... it just seems weird!
Can you try the phone on another carrier? This would probably be the final test you could do. Sounds like you have tried everything.
Yup, tried that earlier on, when I tested my SIM card in some friends' phones (one on Rogers, one on Telus), and while doing that also tested their SIM cards in my phone. With their SIM cards in my phone, the same problem happens as when I'm using my own SIM card.
Gah! It's frustrating, but something I can live with for now until I can get a new phone. I just still can't get over the "everything's fine" on 2G, but moving up to 3G or beyond and I completely lose voice. A colleague of mine has the same phone and the same plan, bought only a month or two before I bought mine. He's got no problems at all with LTE and voice. Although he was on the unofficial CM 12.1 nightlies (5.1.1), I don't think that would have any perceivable difference than when I was on CyanideL 15.x (also 5.1.1).
I've tried everything, so hopefully someone can shine some light into this issue.
I bought a new (unused but from a 3rd party) Samsung Galaxy A50 (A505U) Verizon branded and unlocked. Got a sim card from Visible and went to get it connected. Nothing. WiFi works, everything works, but no cell service.
Here's what I've done (some multiple times)
- reset everything to include network settings, hard reset, etc
- removing the sim, resetting, putting the sim back in. I always get a notification saying the sim card is removed and it goes away when I put the sim back in, so it is recognizing a sim card is in there
- switched sims with another Visible phone/sim and nothing. Both sims worked on other phone but neither worked on this phone
- tried getting into the hidden menus but none of them worked
- talked to Visible tech support which upgraded the issue to the highest level and concluded it's the phone
- Visible believes it's the APN settings but I cannot edit current APNs nor add new ones (grayed out)
- manually add networks, I can see Visible, TMobile, ATT, and some weird numbers, but when I try to connect to Visible it says cannot register on the network, other networks say the sim is not setup for them
- sometimes I get the icon that shows all bars but they're grayed out, sometimes it shows 3-4 bars lit up, sometimes even shows a 4G icon, but mostly the grayed out bars
- sent the phone to Samsung, they tested it and found no faults, guess the hardware is good, ruled that out.
- got into dev options but I'm aware the OEM unlock is not on option on the A505U, not sure if I can change anything else.
I'm out of options. Any other ideas? I think if I can either get into the hidden menus I'll be able to diagnose it better, or if I can somehow change the APN settings I'll be able to set it up. Visible tech support thinks it's the APN, which makes sense to me, but I can't change them.
Any help is greatly appreciated.
I was able to get into the CSC change function, there's not many there, but would changing the CSC help? If so, which should I go to?
I've had a similar issue. Was working fine until the Android 10 update arrived. Since then, it won't work with my total wireless sim card. Tried 3 different sim cards on it, but nothing. Can't add it do anything with the APN, and getting into the phone info hidden menu doesn't help any. I suspect it's a bug in the new firmware or something like that. Works fine with a Verizon SIM though.
Update: Verizon SIM no longer connects to phone. Still works with LTE data. It seems that the CDMA radio quit working with the update to Android 10. Must have been collecting to the Verizon network with VoLTE until it updated the provisioning or something.
So, I finally figured out a workaround for mine that was able to get both data and voice networks to connect while using total wireless, which is an MVNO on the Verizon network. I pretty much narrowed it down to being an issue with the modem not working with CDMA. What I did was download the last Android 9 firmware and flashed just the modem (file starts with CP_) using Odin. After that, I rebooted it and voila! It connected.
Just thought i would give my experience as i just delt with this. i got my 10 update this morning nd let it update and apon a reboot i lost all mobile connection, a signal bar would show for a few seconds looking like it was trying to lock in a signal and it would go back to the ⌀ symbol. i tried flashing the android 9 modem from 2 different updates and neither fixed it. i just decided to order a new phone as i feel its time anyways. my next attempt will be to flash android 9 back using odin then just throw this phone up on craigslist
edit: odin successfully flashed back to android 9 and signal now works again. so if anyone has this issue you can try the method above of just flashing the modem and if that doesnt work you can go back to 9 and restore functionality of verizon mvno's
darkmage1991 said:
Just thought i would give my experience as i just delt with this. i got my 10 update this morning nd let it update and apon a reboot i lost all mobile connection, a signal bar would show for a few seconds looking like it was trying to lock in a signal and it would go back to the ⌀ symbol.
Click to expand...
Click to collapse
Out of curiosity, which carrier are you using?
TJay99 said:
Out of curiosity, which carrier are you using?
Click to expand...
Click to collapse
Visible
samsung a50 not connecting to VZW towers (red pocket)
My phone is doing the exact same thing and while I can appreciate how you resolved the issue it doesn't make much sense to me.
I use Red Pocket for my network. (Which uses Verizon towers - I use the CDMA Sim)
Before this major update to 10 my phone worked flawlessly. Now it won't connect to the network much like you guys have stated in this thread. Mine will connect intermittently for like 3 or 4 min tops and then get kicked off the tower and will actually not show any bars (Circle with a line through it) to show no service for about 10 or so minutes then restart the whole process.
I also have a work phone (2nd phone) that is directly tied to the verizon towers on the verizon network. If I take the sim out of that phone and put it in my samsung a50 the samsung a50 is happy and can make phone calls, send texts, and stays on the vzw towers with no disconnects.
If I take my red pocket sim card and place it in my work phone that phone also works just fine - send messages, make phone calls, and stays on the vzw towers with no disconnects. (work phone = iphoneXR - it's free, sue me)
Even though reverting the modem obviously fixes your issue I do not think that is the actual problem. It also doesn't seem that a third party carrier is being randomly booted off the towers, it seems to be a glitch with third party carriers using third party sims utilizing this new android 10 software that VZW towers do not like.
Which obviously points to an issue with Samsung's latest software not being compatible with third party carriers.
I can't seem to contact Samsung in a direct manner to resolve this issue as they want me to take it to a third party store to have it looked at. I spent 2 and half hours with tech support from red pocket and they came to the conclusion that VZW was doing "upgrades/maintenance" to their towers in my area. (whatever that means.
Any ideas on how I can contact Samsung directly to detail this issue to them? I really do not want to have to root my phone in order to use odin to set my modem back to version 9 as I'm hearing that doing so voids all kinds of implied warranties with the phone and it's only 6 months old.
Appreciate any help that you guys might be able to steer me towards.
Thanks.
Before this major update to 10 my phone worked flawlessly- They Told you the answer, Odin # 9 or if its under warranty take it back Good luck.
My phone (SM-A505U) wasn't even working on visible before android 10.
See my post at the end of this thread: https://forum.xda-developers.com/ga...official-firmware-t3955727/page2#post83845605
I have that problem too. Where I can download v9. I got the Odin.