Unable to send SMS - Nexus S General

Hi,
I have a unrooted absolutely Stock Nexus S T-MOBILE version which I manually updated to Ice Cream Sandwich 4.0.3 using the official update file.
The problem I'm facing is that ever since I upgraded to ICS I'm unable to send SMSs but I can receive SMSs just fine. I did some searches and realized that the SMSC should be a valid number where as mine is showing 00. I tried to edit this by going to *#*#4636#*#* > Phone Information > SMSC update. But every time I try to update it, it says update error.
I'm using the phone in India Mumbai and the SMSC should be +919820005444 (verified on my friend's Android Device.
I also read that this could be an error due to a faulty SIM card but when I used the same SIM card in another device it works perfectly. I also tried other SIM cards in my phone, all of them are unable to send SMSs.
Please help!

Use this guide: http://forum.xda-developers.com/showthread.php?t=979564

I was unable to send/recive mms on ICS if i were on 2g/3g, but wifi worked.
Finally found out how to fix it today (at least my issue).
I wrote down whatever info i had in the APN-settings for wap and mms on my phone and merged them, putting all the mms info in the wap-apn, where none existed and added an extra ",mms" to the apn type-field.

Mine dont work too i am in uk called cs told me tobcheck apn still nothing
Sent from my Nexus S using Tapatalk

Related

got 7740 mango update by debranding

hi,
Today morning, i tried changing the following registry key .
Once i restarted the mobile, i got the updates notification for 7740 instantly.
MobileOperator: VOD-DE
MOName: Vodafone
OEMDeviceName: Atlantic_VDF_DE
anyhow, there is no Wifi tethering in this update.
What's new in this update?
Notice battery life improvements or anything?
It was said to fix the exchange server problem and some improvements in voicemail.
Not even 24 hrs since i installed the update.
Will keep posted if i see any battery improvements.
7740 supposed to have some improvement for battery according to this:
http://www.winrumors.com/nokia-promises-second-windows-phone-update-for-battery-issues/
Just did the changes as the OP suggested and I triggered the 7740 update. Interestingly, it says there is also "LG Update for Windows Phone", OP did you see this too?
Hoping it is for tethering .... updating now, will report when done.
Just in case anyone needed debranding instructions:
1. Enable the MFG application by going to the dialer and dialing ##634# then pressing call.
2. Launch the MFG application and enter 277634#*# when prompted for a password.
3. Select the Engineer Menu item.
4. Select the Other Setting menu item.
5. Select the Edit registry menu item.
6. Set the input boxes on this menu as follows:
Select ROOT_PATH: HKEY_LOCAL_MACHINE
Input SUB_PATH: \System\Platform\DeviceTargetingInfo\
Input KEY: MobileOperator
Data Type: STRING
7. Select Query and write down the result in case you need to re-brand for some reason.
EDIT:
Installation failed after rebooting phone, error code 8018001e, did not update to 7740.....did not do LG update...
EDIT 2:
Tried to update it a couple more times, but always getting the error... OP what kind of Quantum do you have and what carrier ROM? C-900? c-900B? c-900k?
can you tell me the registry changes you did ?
What mobile operator did you put in ?
I finally managed to update.
I think battery might be slightly better but that could be placebo lol
Anyway keeping current is always good anyway
I tried vod de and also vod it. Both showed there was 2 updates, but always failed. Op and scoobysnacks, what model of quantums are you using?
dont do ir his way, use the update cab sender here
http://forum.xda-developers.com/showthread.php?t=1306415
Much easier
Thanks, the cab sending method worked. I'm still interested in what carrier your phone was originally with
bobzero said:
Thanks, the cab sending method worked. I'm still interested in what carrier your phone was originally with
Click to expand...
Click to collapse
mine is a bell phone I'm using with telus
yakaaithiri said:
hi,
Today morning, i tried changing the following registry key .
Once i restarted the mobile, i got the updates notification for 7740 instantly.
MobileOperator: VOD-DE
MOName: Vodafone
OEMDeviceName: Atlantic_VDF_DE
anyhow, there is no Wifi tethering in this update.
Click to expand...
Click to collapse
Just a note -- if you truly 'debrand' by changing the MobileOperator to " " (blank), then you don't get the upgrade right away. It seems to be region specific.
Official 7740.16 update notices have been getting sent out over the last week to Bell phones.
No firmware update accompanied this OS update.
Just for reference in case anyone wanted to brand their phone to Bell or ATT:
AT&T
[HKLM\System\Platform\DeviceTargetingInfo\]
MobileOperator = ATT-US
MOName = AT&T Wireless
OEMDeviceName = PACIFIC_ATT_US
BELL
[HKLM\System\Platform\DeviceTargetingInfo\]
MobileOperator = BEL-CA
MOName = BELL
OEMDeviceName = PACIFIC_BEL_CA
Other keys that can be adjusted and have an impact:
FirmwareRevision
RadioSoftwareRevision
MODeviceName

[Q] No network available on unrooted s4

Hi,
I bought a second hand samsung s4(a few days old) from my friend...after inserting my sim in it, it isn't showing any network signals...when i looke in settings for network operators and selected automatically choose preferred networks, it shows "Can't connect to this network right now please try again later"...have removed and reinserted my sim in it but still no benifit...Have searched about my problem and found a related problem with another devices (s3) and it told them to place an EFS folder in root if you have backup but it was for a rooted phone and mine is not...So, Please help me

CDMA data not working after update to 4.4.2

Hi.
Have just update my droid razr M to 4.4.2. After successfully update, Data is not working. I am using Reliance CDMA sim card.
Please help me if there is any settings or crack to start EVDO data working..
Anyone from India having any solution for this problem? Plz Help..
kulsforu said:
Hi.
Have just update my droid razr M to 4.4.2. After successfully update, Data is not working. I am using Reliance CDMA sim card.
Please help me if there is any settings or crack to start EVDO data working..
Click to expand...
Click to collapse
Hi, Same issue with my phone droid razr m udpate to kitkat 4.4.2. Can any one help how resolve this issue. Having Reliance CDMA netowrk. Thanks in advance.
kulsforu said:
Hi.
Have just update my droid razr M to 4.4.2. After successfully update, Data is not working. I am using Reliance CDMA sim card.
Please help me if there is any settings or crack to start EVDO data working..
Click to expand...
Click to collapse
same problem here did you find any sollution?
ansarirashidy2k said:
same problem here did you find any sollution?
Click to expand...
Click to collapse
I have got one solution from somewhere is that we need to downgrade back to 4.1.2. But for that you need to download file from:
http://sbf.droid-developers.org/phone.php?device=8
Then You need to extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
there is a workaround for this, but it requires unlocked bootloader and possibly a ruim flashing tool.
i'm not sure it it will work for any of you, but at least i managed to make my ruim work in ukraine.
jgarin said:
there is a workaround for this, but it requires unlocked bootloader and possibly a ruim flashing tool.
i'm not sure it it will work for any of you, but at least i managed to make my ruim work in ukraine.
Click to expand...
Click to collapse
I am totally struck after 4.4.2 update. My Droid Razr M was so fine, now almost useless. No data on CDMA. I am from India and using Reliance. Battery drain is so fast, cannot even surviving one day, earlier it was almost with juice for 2 days. Waiting seriously for some work around.
Adiseshanaik said:
I am totally struck after 4.4.2 update. My Droid Razr M was so fine, now almost useless. No data on CDMA. I am from India and using Reliance. Battery drain is so fast, cannot even surviving one day, earlier it was almost with juice for 2 days. Waiting seriously for some work around.
Click to expand...
Click to collapse
Unlock the Bootloader & down grade to 4.1.2,this method work for me. Now I am able to use CDMA network using Reliance..
scorpions7 said:
Unlock the Bootloader & down grade to 4.1.2,this method work for me. Now I am able to use CDMA network using Reliance..
Click to expand...
Click to collapse
There is a new type of micro sim cards available at Reliance Web World. By changing to new UIM card at reliance, CDMA data will work in Kitkat.
I am using CDMA/ GSM Sim unlocked mobile.. If I change the Sim will data work after updating kitkat.. Coz it was not working with the same Sim.. Have you checked it by using new Sim after kitkat update?
Sent from my XT907 using XDA Free mobile app
scorpions7 said:
I am using CDMA/ GSM Sim unlocked mobile.. If I change the Sim will data work after updating kitkat.. Coz it was not working with the same Sim.. Have you checked it by using new Sim after kitkat update?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Was CDMA data working before update to kitkat??
kulsforu said:
Was CDMA data working before update to kitkat??
Click to expand...
Click to collapse
Yes CDMA data was working before update to Kitkat..but after update No data on Reliance CDMA network. Test messages & voice calls are working.
Micro SIM are not available in Reliance Web World they will ask you to cut the SIM for using it.
scorpions7 said:
Yes CDMA data was working before update to Kitkat..but after update No data on Reliance CDMA network. Test messages & voice calls are working.
Micro SIM are not available in Reliance Web World they will ask you to cut the SIM for using it.
Click to expand...
Click to collapse
Then it will definitely work if you purchase the new micro SIM and activate to your number. Here its available in reliance web world. There is another option to start CDMA data is that u have to restore back to JellyBean.
I have purchased New Micro SIM but still Data is not working. Downgraded to Jelly Bean and used normal SIM, now Data is working fine.
scorpions7 said:
I have purchased New Micro SIM but still Data is not working. Downgraded to Jelly Bean and used normal SIM, now Data is working fine.
Click to expand...
Click to collapse
You have to activate new SIM using any ZTE mobile. Then Data will work fine. I have done it and its working fine in kitkat.
kulsforu said:
You have to activate new SIM using any ZTE mobile. Then Data will work fine. I have done it and its working fine in kitkat.
Click to expand...
Click to collapse
I activated my micro Sim using Samsung young CDMA mobile...but it was not working after updating kitkat. You have to activate it using *228 enabled imported CDMA mobile.. Your ZTE mobile is purchased from reliance or it is imported mobile phone?
Sent from my XT907 using XDA Free mobile app
scorpions7 said:
I activated my micro Sim using Samsung young CDMA mobile...but it was not working after updating kitkat. You have to activate it using *228 enabled imported CDMA mobile.. Your ZTE mobile is purchased from reliance or it is imported mobile phone?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
The ZTE mobile is purchased from India. Not any imported phone.
Reliance evdo on droid razm m kitkat
After many research finally i got the way to use reliance evdo on STOCK KITKAT (TESTED ON DROID RAZR M).
1- First of all you need a blank reliance reliance standard omh ruim having series starting from RGER UC XXXX.
Picture attached for reference.
2 - visit reliance store and transfer your cdma no to the new RGER UC XXXX series RUIM.
3 - insert new into handset, then go to SETTINGS>MORE>MOBILE NETWORKS>ACCESS POINT NAMES.
now you can see a + sign in top.
picture attached for reference.
4 - click on + sign and fill the setting as below -
name - RCOM
apn - #777
proxy - leave blank
port - leave blank
user name - net
password - net
server - leave blank
MMSC - leave blank
mms proxy - leave blank
mms port - leave blank
mcc - 404
mnc - 00
authentication type - PAP or CHAP
apn type - leave blank
apn protocol - leave blank
bearer - leave blank
then save the settings and select the RCOM profile.
hurray.. enjoy.. just enable the data.
FOR ANDROID 4.1.2 - need sim series RCER UC05 / RGER UC (RECR UC06 NOT WORK)
FOR ANDROID 4.4.2 - RGER UC (RECR UC06 NOT WORK)
bro i had the solution to your prblem
kulsforu said:
Hi.
Have just update my droid razr M to 4.4.2. After successfully update, Data is not working. I am using Reliance CDMA sim card.
Please help me if there is any settings or crack to start EVDO data working..
Anyone from India having any solution for this problem? Plz Help..
Click to expand...
Click to collapse
call me at 9371266944.
From the photo of the RGER series SIM that you have shown, it seems you cannot cut that to nano form factor. I can see that this is the old type of SIM card where the circuit section is elongated.
In comparison the RECRU series has a SIM which can be cut to nano size without cutting off parts of the circuit.
So from what you said, users who need data on a phone which accepts only nano SIM cards (e.g. Droid Ultra/Maxx/ Turbo), will never be able to use data.
That is simply not true.
pankajsinghrawat said:
After many research finally i got the way to use reliance evdo on STOCK KITKAT (TESTED ON DROID RAZR M).
1- First of all you need a blank reliance reliance standard omh ruim having series starting from RGER UC XXXX.
Picture attached for reference.
2 - visit reliance store and transfer your cdma no to the new RGER UC XXXX series RUIM.
3 - insert new into handset, then go to SETTINGS>MORE>MOBILE NETWORKS>ACCESS POINT NAMES.
now you can see a + sign in top.
picture attached for reference.
4 - click on + sign and fill the setting as below -
name - RCOM
apn - #777
proxy - leave blank
port - leave blank
user name - net
password - net
server - leave blank
MMSC - leave blank
mms proxy - leave blank
mms port - leave blank
mcc - 404
mnc - 00
authentication type - PAP or CHAP
apn type - leave blank
apn protocol - leave blank
bearer - leave blank
then save the settings and select the RCOM profile.
hurray.. enjoy.. just enable the data.
FOR ANDROID 4.1.2 - need sim series RCER UC05 / RGER UC (RECR UC06 NOT WORK)
FOR ANDROID 4.4.2 - RGER UC (RECR UC06 NOT WORK)
Click to expand...
Click to collapse
CDMA data not working for unlocked XT907 after OS Update to KK!!
s_u_n said:
From the photo of the RGER series SIM that you have shown, it seems you cannot cut that to nano form factor. I can see that this is the old type of SIM card where the circuit section is elongated.
In comparison the RECRU series has a SIM which can be cut to nano size without cutting off parts of the circuit.
So from what you said, users who need data on a phone which accepts only nano SIM cards (e.g. Droid Ultra/Maxx/ Turbo), will never be able to use data.
That is simply not true.
Click to expand...
Click to collapse
where can i find the RGERU series SIM in CDMA web store in mumbai ?
Cos mostly the one i visited dont have these SIM series

[Q] Not registered on network SM-n9005

I am having a problem with my samsung galaxy note 3. I cannot send text or calls. I am having an error message "not registered on network".
Does anyone experience the same problem and know the fix? thanks a lot!
*#06#
Rojohn said:
I am having a problem with my samsung galaxy note 3. I cannot send text or calls. I am having an error message "not registered on network".
Does anyone experience the same problem and know the fix? thanks a lot!
Click to expand...
Click to collapse
you have your IMEI?? or lost it.
i had this problem once so i went into network settings and changed it to manual, selected the network im on and it said registered, switched it back to automatic and it was all sorted. either try that or check imei
nijom said:
you have your IMEI?? or lost it.
Click to expand...
Click to collapse
i have my imei. do you know how to fix the issue sir?
KevandLynds said:
i had this problem once so i went into network settings and changed it to manual, selected the network im on and it said registered, switched it back to automatic and it was all sorted. either try that or check imei
Click to expand...
Click to collapse
i've done that several times but still not working sir
Rojohn said:
i have my imei. do you know how to fix the issue sir?
Click to expand...
Click to collapse
Does your phone also remember the IMEI? Dial *#06# and check if the number matches the original IMEI. If it's NULL or starts with 0049, that's the cause.
If the IMEI is correct, try a different SIM.
Sent from my SM-N9005 using Tapatalk 2
ShadowLea said:
Does your phone also remember the IMEI? Dial *#06# and check if the number matches the original IMEI. If it's NULL or starts with 0049, that's the cause.
If the IMEI is correct, try a different SIM.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
The IMEI is not null or it does not start with 0049. The IMEI on the phone and the box is correct is also correct. Also I've tried different SIM card but still getting the same message "not registered on network".
Rojohn said:
The IMEI is not null or it does not start with 0049. The IMEI on the phone and the box is correct is also correct. Also I've tried different SIM card but still getting the same message "not registered on network".
Click to expand...
Click to collapse
Dial *#1234# and tell me what appears.
Rojohn said:
The IMEI is not null or it does not start with 0049. The IMEI on the phone and the box is correct is also correct. Also I've tried different SIM card but still getting the same message "not registered on network".
Click to expand...
Click to collapse
1- First, put your SIM card into another phone to make sure it works fine?
2- Second, open the Debug ServiceMode Menu and do the following: DEBUG SCREEN > NAS INFORMATION > MM INFORMATION (capture screenshot #1) > Menu - Back > MM REJECT CAUSE (capture screenshot #2).
And post these screenshots for further checking.
To open the Debug ServiceMode Menu:
a- If you have root, install Phone INFO ★Samsung★ app > Menu > 'Secret Codes' > *#197328640# > 'Launch 0'.
b- If you don't have root, open the dialer > *#0011# > Menu - Back > Menu - Key Input > Q0 > wait... until Debug ServiceMode Menu appears.
I have a quite similar problem. My phone is a 3UK (service provider) phone. I have 2 sim cards with me (MTN & Etisalat). My phone (note3) works perfectly fine. I have even rooted to resolve this issue.
Now the issue is whenever i put my MTN sim card it works perfectly fine on Note 3, however the moment i enter my Etisalat sim it will work for 10-15 mins & will stop working. I will have network bars but when i try to make any outgoing or incoming call it does not work.
Also if i use the same etisalat sim with my iPhone 5s it works perfectly fine.
I have tried *#1234# & the information that i got is as below:
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005H3GDMJ2
Some of my friends told me to upgrade it to Kitkat and that might resolve the issue but when i try to check for updates it says:
Your device has been modified. Software updates are not available.
Please let me know what is the solution
Note: I am new to android world. So please consider that..
anuragjiw said:
I have a quite similar problem. My phone is a 3UK (service provider) phone. I have 2 sim cards with me (MTN & Etisalat). My phone (note3) works perfectly fine. I have even rooted to resolve this issue.
Now the issue is whenever i put my MTN sim card it works perfectly fine on Note 3, however the moment i enter my Etisalat sim it will work for 10-15 mins & will stop working. I will have network bars but when i try to make any outgoing or incoming call it does not work.
Also if i use the same etisalat sim with my iPhone 5s it works perfectly fine.
I have tried *#1234# & the information that i got is as below:
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005H3GDMJ2
Some of my friends told me to upgrade it to Kitkat and that might resolve the issue but when i try to check for updates it says:
Your device has been modified. Software updates are not available.
Please let me know what is the solution
Note: I am new to android world. So please consider that..
Click to expand...
Click to collapse
- What does it say when you make a call (incoming/outgoing)?
Please follow my above post and show screenshots for more checking.
- Regarding to upgrading it to KitKat, I doubt that will not fix your issue. However if you want to upgrade, you can flash the stock firmware via Odin. Use Phone INFO ★Samsung★ app > Menu > 'Firmware Browser' to download the correct firmware for your device, and flash it via Odin.
vndnguyen said:
- What does it say when you make a call (incoming/outgoing)?
Please follow my above post and show screenshots for more checking.
- Regarding to upgrading it to KitKat, I doubt that will not fix your issue. However if you want to upgrade, you can flash the stock firmware via Odin. Use Phone INFO ★Samsung★ app > Menu > 'Firmware Browser' to download the correct firmware for your device, and flash it via Odin.
Click to expand...
Click to collapse
When I try to make a call it just says dialing.. And when I try to get incoming call it says switched off..
I have tried to check for firmware in phone info and got N9005XXUGNH1 . Not sure if I should install that or not.
Attached are the NAS info & firmware in phone info.
ShadowLea said:
Does your phone also remember the IMEI? Dial *#06# and check if the number matches the original IMEI. If it's NULL or starts with 0049, that's the cause.
If the IMEI is correct, try a different SIM.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
I have tried to check the IMEi. My imei is not null or starts with 0049.
anuragjiw said:
When I try to make a call it just says dialing.. And when I try to get incoming call it says switched off..
I have tried to check for firmware in phone info and got N9005XXUGNH1 . Not sure if I should install that or not.
Attached are the NAS info & firmware in phone info.
Click to expand...
Click to collapse
1- Please check and make sure if date/time setting is correct? Or it was not correct?
2- In ServiceMode Menu, select CALL END CAUSE and show the screenshot?
vndnguyen said:
1- Please check and make sure if date/time setting is correct? Or it was not correct?
2- In ServiceMode Menu, select CALL END CAUSE and show the screenshot?
Click to expand...
Click to collapse
i have checked the date & time which is perfect.
Do u want all these screenshots with my Etisalat sim inserted or any sim inserted?
When i click on Call end cause it comes back to Service mode.
anuragjiw said:
i have checked the date & time which is perfect.
Do u want all these screenshots with my Etisalat sim inserted or any sim inserted?
When i click on Call end cause it comes back to Service mode.
Click to expand...
Click to collapse
I asked for the date/time settings as in the MM REJECT CAUSE screenshot there is only log from the past. No any new log.
The screenshots you have shown are from the MTN sim card, right?
All info seem to be fine, I don't know why it cannot make or receive a call.
If possible, try to take screenshots for both SIM cards and compare to see if there is any differences.
EDIT: Oh NO, you need to show me screenshots from the sim card that doesn't work, NOT screenshots from the sim card that works fine.
vndnguyen said:
I asked for the date/time settings as in the MM REJECT CAUSE screenshot there is only log from the past. No any new log.
The screenshots you have shown are from the MTN sim card, right?
All info seem to be fine, I don't know why it cannot make or receive a call.
If possible, try to take screenshots for both SIM cards and compare to see if there is any differences.
EDIT: Oh NO, you need to show me screenshots from the sim card that doesn't work, NOT screenshots from the sim card that works fine.
Click to expand...
Click to collapse
Yes i have taken it from MTN sim which is working perfectly fine. Even my etisalat sim works for like 20 mins before it stops working.
Also i am downloading the N9005XXUGNH1 from Sammobile as you have mentioned before. But will it resolve the issue?
Attached is the screenshot of the same.
OK will attach the Etisalat sim & will upload in 5 mins
Attached are the screenshots of MM info, MM reject cause.
I am unable to open CALL END Cause. The moment i tap on it, it goes back to DEBUG Screen
I have tried to compare MM info, Reject cause with both the sim cards entering one by one & found out everything is same in Reject cause.
But MM info there is a slight change in MMC-MNC: 621-30 (MTN which works fine) & MMC - MNC: 621 - 60 (Etisalat which is not working)
LAC: 2ae8, RAC: 9 (MTN) & LAC: 7d15, RAC: 4
There are some changes in TMSI which is think is some sort of id.
Also want to know if I install N9005XXUGNH1 firmware on my samsung note 3 will this issue resolve?
anuragjiw said:
Attached are the screenshots of MM info, MM reject cause.
I am unable to open CALL END Cause. The moment i tap on it, it goes back to DEBUG Screen
Click to expand...
Click to collapse
From the screenshots it appears to be fine on both sim card.
You should take a screenshots when it becomes not working (after 20 min...)
vndnguyen said:
From the screenshots it appears to be fine on both sim card.
You should take a screenshots when it becomes not working (after 20 min...)
Click to expand...
Click to collapse
OK will send the screenshots once it stops working.. BTW thanks a lot in advance..
Also want to know if I install N9005XXUGNH1 firmware on my samsung note 3 will this issue resolve?
EDIT: I found out the problem but unable to find the solution.
Also want to inform you that I tried to select the network automatically once it stopped working & it worked for around 1-2 hours..
Suggest me what to do..

Oxygen OS, root, APN and the meaning of life

Hi All,
I appeal to you keepers of the knowledge to enlight me on some points I need to clarify.
The situation:
I recently bought an unbranded Oneplus 6T and I (still) use stock oxygen OS V9.0.17.
Since a couple of years I've been using a data-only plan with a VOIP SIP account as my main phone service. It was working great on my beloved almost-6-years-old Nexus 5 until I dropped it to it's death. I chose the 6T as replacement because it seemed a good option for rooting and custom ROMs.
My service provider is FIDO in Canada. They offer a very good value data-only plan (15$ CAD for 4GB), but for an UNKNOWN reason to me, with FIDO the SIP calls drop automatically if I use the default autoconfigured APN for LTE. The simple solution to that is to create a new empty APN config and fill it manually. Once done, SIP calls work like a charm (again, I don't know what causes this).
On my Nexus, I was running Android 8.0 which permitted me to modify the APN. But since Android 8.1 Google (don't be evil right) introduced the APN locking for participating providers. FIDO seems to be one of them since I cannot change any APN configuration on Oxygen OS 9.0.17. That renders my phone useless (unless I choose the 3G apn, which honestly sucks).
Now that you know a little bit about my life, here are my questions.
First thing I did:
I rooted my phone with Magisk 20.0 with the intention of modifying the /system/etc/apns-conf.xml and try changing the default FIDO APN configuration with the hope it would work.
I tried by many ways to modify it (using ADB, root browser, root explorer, solid explorer) and I couldn't change the content. Even worse, when I tried to change the permissions to the file to RW using root explorer, the file turned empty (0b) and it's still impossible to modify it (I tried editing it, deleting, replacing it, nothing works).
Question 1: The simplest of ways would be to be able to change the APN. Does anybody knows a trick (using root or not) to do that on stock OOS 9.0.17. Anybody ever tried changing apns-conf.xml?
Question 2: Did anybody succefylly edit system files onstock OOS 9.0.17 using root?
Question 2-A: Does anybody know why I break the file when I change the permission? I'd like to understand what's going on.
Another option that I am considering is using a custom ROM that disables this nonsense APN lock mechanism.
Question 3: Does anybody have a good ROM suggestion that is positively disabling this APN lock and that would allow me to change my APN with FIDO? (I was considering Lineage but I couldn't get a firm answer on the APN unlock capability).
I searched the web for many hours without success, I hope you can help me with this.
Thank you all for your insight.
jfmartel said:
Hi All,
I appeal to you keepers of the knowledge to enlight me on some points I need to clarify.
The situation:
I recently bought an unbranded Oneplus 6T and I (still) use stock oxygen OS V9.0.17.
Since a couple of years I've been using a data-only plan with a VOIP SIP account as my main phone service. It was working great on my beloved almost-6-years-old Nexus 5 until I dropped it to it's death. I chose the 6T as replacement because it seemed a good option for rooting and custom ROMs.
My service provider is FIDO in Canada. They offer a very good value data-only plan (15$ CAD for 4GB), but for an UNKNOWN reason to me, with FIDO the SIP calls drop automatically if I use the default autoconfigured APN for LTE. The simple solution to that is to create a new empty APN config and fill it manually. Once done, SIP calls work like a charm (again, I don't know what causes this).
On my Nexus, I was running Android 8.0 which permitted me to modify the APN. But since Android 8.1 Google (don't be evil right) introduced the APN locking for participating providers. FIDO seems to be one of them since I cannot change any APN configuration on Oxygen OS 9.0.17. That renders my phone useless (unless I choose the 3G apn, which honestly sucks).
Now that you know a little bit about my life, here are my questions.
First thing I did:
I rooted my phone with Magisk 20.0 with the intention of modifying the /system/etc/apns-conf.xml and try changing the default FIDO APN configuration with the hope it would work.
I tried by many ways to modify it (using ADB, root browser, root explorer, solid explorer) and I couldn't change the content. Even worse, when I tried to change the permissions to the file to RW using root explorer, the file turned empty (0b) and it's still impossible to modify it (I tried editing it, deleting, replacing it, nothing works).
Question 1: The simplest of ways would be to be able to change the APN. Does anybody knows a trick (using root or not) to do that on stock OOS 9.0.17. Anybody ever tried changing apns-conf.xml?
Question 2: Did anybody succefylly edit system files onstock OOS 9.0.17 using root?
Question 2-A: Does anybody know why I break the file when I change the permission? I'd like to understand what's going on.
Another option that I am considering is using a custom ROM that disables this nonsense APN lock mechanism.
Question 3: Does anybody have a good ROM suggestion that is positively disabling this APN lock and that would allow me to change my APN with FIDO? (I was considering Lineage but I couldn't get a firm answer on the APN unlock capability).
I searched the web for many hours without success, I hope you can help me with this.
Thank you all for your insight.
Click to expand...
Click to collapse
Have you tried creating a new apn with the info and settings you need?
jestyr8 said:
Have you tried creating a new apn with the info and settings you need?
Click to expand...
Click to collapse
Yes! I tried that many times.
So, what happens is when you have an "APN locked SIM" inserted in the device, you have no access to any edit option. No editing, no adding, nothing. You are in view mode for the APN settings (which is useless really).
In my research I found that if you insert a "not APN locked SIM" you get acces to creating a new APN (and of course editing the actual SIM APN settings).
I happen to have a SIM card (my girlfriend's) that is not APN locked on hand. I tried a couple of times creating a new APN with the FIDO settings but when I inserted back the FIDO SIM my new APN was not in the list of options.
... I should have deepened my research! I failed at that...
What I didn't realize at the time is that when you create a new APN, Android defaults the MCC and MNC parameters with the values associated with the currently inserted SIM!!! I tought it was some kind of black magic settings used by the service provider for it's network to work. But not later than TODAY (I did more research today...) I learned that: MCC = Mobile Country Code and MNC = Mobile Network Code. ****!!!
Sooooo, all I had to do is create a new APN with my girlfriend's SIM inserted and set (along with all the other settings) the MCC and MNC to the values corresponding to FIDO config (which in the past I left as is since I didn't know what they were). Save. Shut down my device. Insert FIDO SIM, reboot, and fuc**ng VOILA!!! The newly created APN is now available and... wait for it... EDITABLE!!! So if I messed-up any setting I can change it and play around with everything like we did when Google was not Evil.
So here I am with my un-activated FIDO SIM and I can confirm that my newly created APN is selectable, but I cannot try a SIP call for now since I've closed my account. Tomorrow I'll get a new subscription & SIM and update this post. But I think this part is solved.
All that being said, Question 1 is partially answered to my greatest pleasure. But I'd still like to hear your experiences about modifying sytem files on OOS with root access.

Categories

Resources