I have set de apn but still I have no data conection phone is only on E all the time
Edit I now have data by doing this but still onf Edge no 3g
Hi,
The above method stated by the original poster did not work for me but the following method did:
( I have my sim card in for this)
1) enter the MFG app (dial ##634#)
2) Input the password 277634#*# and press enter
3) Choose No. 7 engineer menu
4) in the engineer sub-menu choose other setting.
5) Choose Set Network Profiles
Let the list populate
6) Scroll down the list and find your appropriate carrier and select the appropriate xml, so for me in the
7) Exit the mfg app, restart phone
8) confirm that data connection is active in settings>mobile network
Check the third post here:
http://forum.xda-developers.com/showthread.php?t=1333150
For some reason mine keeps going back to 2G, but a few numbers and back to 3g only.
My first post. I hope this helps someone else here. I will take you through the steps of updating the Koodo Nexus S to Ice Cream Sandwich 4.0.3, Super User + Root, Radio, and finally APN. This GUIDE is strictly for the Koodo Mobile Network operated by Telus in Canada. I am located in Saint John, New Brunswick and I have been struggling with several aspects of this upgrade especially the lack of 3G after following other tutorials.
Please ensure that you have Clockworkmod installed + super user on a rooted Gingerbread phone.
[WARNING] You must wipe your phone which includes sms, contacts, applications, and the like. I recommend making a backup of your entire device. Search this forum for ways to backup before a complete upgrade. It is rather easy. Google will sync most of your vital information but they won't sync data you create directly on your phone with non-google apps. Once you have your backups made be sure to copy them back your PC.
Now that you have your backup we will download a few files and place them on your SDCARD.
Download the following files:
1. ICS 4.0.3 Official Full Rom: http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip
2. ICS superuser for root: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
4. Radio UCKB2 for i9020a: http://forum.xda-developers.com/showthread.php?t=1116884
Setup
1. Now upload all of these downloaded files to your device's SDCARD via USB Storage.
2. Power off the device.
3. Power on the device into recovery mode. Hold the power button and the volume up. Select recovery using the volume buttons and press the power button to select.
4. Select Mounts and Storage.
5. Format the following: /system /cache /data /boot. Note that I choose not to format /sdcard. It is unnecessary. If you do format /sdcard then you will have to push the files via developer console: adb.exe push file.zip /sdcard/file.zip
6. Go back and select Install zip from sdcard.
7. Select ZD3PyN0t.zip and Install. This will take a few moments.
8. Choose zip from sdcard again and select Superuser-3.0.7-efghi-signed.zip and install. You do not have to install superuser at this point but I strongly recommend it. Originally I was using ICS_su.zip but I believe this is not an official zip but either seemed to work fine. Look on the forums for ICS_su.zip if you have issue with the one I am suggesting here.
9. Choose zip from sdcard again and select XXKB2-radio-nexuss-unsigned.zip and install. This radio is very important. While some other radios might work I found this one to be the most stable for Koodo and identical baseband as Gingerbread was.
10. I lost recovery mode once while doing this an evening ago and I was not sure why this happened. I recommend this additional step at this point. Go back and go to Mounts and Storage. Mount /system. From the Developers console you can run: adb shell rm /system/etc/install-recovery.sh
This automated script can cause you to loose clockworkmod recovery otherwise.
11. Go back and Select Reboot System Now. Wait for your phone to load.
12. At this point you will not have 3G or Data capabilities. You need to setup your google account and wifi. Once the phone is loaded on the home screen it will begin syncing with Google and updating your phone with your data including apps and the like. Once this happens we should now enable 3G. The problem I discovered with my 3G was that the phone was setup for Telus APN. Telus APN will not work with an unlocked Koodo phone in my area.
3G ENABLING STEPS
13. Navigate to Settings > Wireless & Networks > Mobile Networks > Network Operators > Select Koodo
14. Navigate to Settings > Wireless & Networks > Mobile Networks > Access Point Names
Input the following settings for TELUS APN (leaving designated fields blank):
APN: sp.koodo.com
Proxy server: 74.49.0.18
Port: 80
Username:
Password:
Server:
MMSC: http://aliasredirect.net/proxy/koodo/mmsc
Proxy server: 74.49.0.18
Port: 80
MCC : 302
MNC : 220
APN type :
Save (back out of the screen) once you have entered in the details exactly. They must be exact or they will not work. Do not leave any extra data created for TELUS APN.
15. Last step! Turn off Wifi via Settings > Wireless & Networks and you should now see a 3G icon ontop of your bars. You now enabled 3G on ICS!
I just had two friends with Nexus S phones in Atlantic Canada try this and it worked fine for Koodo. I am sure there are similar issues with APN settings for other carriers like Koodo so perhaps this will be of some help to those folks as well.
Thanks very much for this post! it helped alot for me on my I9020A on the nexus beam rom with kodoo now i don't have to wait for ICS!
vamman said:
My first post. I hope this helps someone else here. I will take you through the steps of updating the Koodo Nexus S to Ice Cream Sandwich 4.0.3, Super User + Root, Radio, and finally APN. This GUIDE is strictly for the Koodo Mobile Network operated by Telus in Canada. I am located in Saint John, New Brunswick and I have been struggling with several aspects of this upgrade especially the lack of 3G after following other tutorials.
Please ensure that you have Clockworkmod installed + super user on a rooted Gingerbread phone.
[WARNING] You must wipe your phone which includes sms, contacts, applications, and the like. I recommend making a backup of your entire device. Search this forum for ways to backup before a complete upgrade. It is rather easy. Google will sync most of your vital information but they won't sync data you create directly on your phone with non-google apps. Once you have your backups made be sure to copy them back your PC.
Now that you have your backup we will download a few files and place them on your SDCARD.
Download the following files:
1. ICS 4.0.3 Official Full Rom: http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip
2. ICS superuser for root: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
4. Radio UCKB2 for i9020a: http://forum.xda-developers.com/showthread.php?t=1116884
Setup
1. Now upload all of these downloaded files to your device's SDCARD via USB Storage.
2. Power off the device.
3. Power on the device into recovery mode. Hold the power button and the volume up. Select recovery using the volume buttons and press the power button to select.
4. Select Mounts and Storage.
5. Format the following: /system /cache /data /boot. Note that I choose not to format /sdcard. It is unnecessary. If you do format /sdcard then you will have to push the files via developer console: adb.exe push file.zip /sdcard/file.zip
6. Go back and select Install zip from sdcard.
7. Select ZD3PyN0t.zip and Install. This will take a few moments.
8. Choose zip from sdcard again and select Superuser-3.0.7-efghi-signed.zip and install. You do not have to install superuser at this point but I strongly recommend it. Originally I was using ICS_su.zip but I believe this is not an official zip but either seemed to work fine. Look on the forums for ICS_su.zip if you have issue with the one I am suggesting here.
9. Choose zip from sdcard again and select XXKB2-radio-nexuss-unsigned.zip and install. This radio is very important. While some other radios might work I found this one to be the most stable for Koodo and identical baseband as Gingerbread was.
10. I lost recovery mode once while doing this an evening ago and I was not sure why this happened. I recommend this additional step at this point. Go back and go to Mounts and Storage. Mount /system. From the Developers console you can run: adb shell rm /system/etc/install-recovery.sh
This automated script can cause you to loose clockworkmod recovery otherwise.
11. Go back and Select Reboot System Now. Wait for your phone to load.
12. At this point you will not have 3G or Data capabilities. You need to setup your google account and wifi. Once the phone is loaded on the home screen it will begin syncing with Google and updating your phone with your data including apps and the like. Once this happens we should now enable 3G. The problem I discovered with my 3G was that the phone was setup for Telus APN. Telus APN will not work with an unlocked Koodo phone in my area.
3G ENABLING STEPS
13. Navigate to Settings > Wireless & Networks > Mobile Networks > Network Operators > Select Koodo
14. Navigate to Settings > Wireless & Networks > Mobile Networks > Access Point Names
Input the following settings for TELUS APN (leaving designated fields blank):
APN: sp.koodo.com
Proxy server: 74.49.0.18
Port: 80
Username:
Password:
Server:
MMSC: http://aliasredirect.net/proxy/koodo/mmsc
Proxy server: 74.49.0.18
Port: 80
MCC : 302
MNC : 220
APN type :
Save (back out of the screen) once you have entered in the details exactly. They must be exact or they will not work. Do not leave any extra data created for TELUS APN.
15. Last step! Turn off Wifi via Settings > Wireless & Networks and you should now see a 3G icon ontop of your bars. You now enabled 3G on ICS!
I just had two friends with Nexus S phones in Atlantic Canada try this and it worked fine for Koodo. I am sure there are similar issues with APN settings for other carriers like Koodo so perhaps this will be of some help to those folks as well.
Click to expand...
Click to collapse
Just as a heads up in this section of the tutorial:
APN: sp.koodo.com
Proxy server: 74.49.0.18
I usually do not add the proxy server, because i found that it SLOWS DOWN HTTPS:// requests like crazy! So basically if your trying to access your koodo account from the web browser it's unbearable unless you remove the proxy server under the APN only (Do not remove the one under MMSC)
just a question, is this for koodo ppl because of the 3g network?
Basche said:
just a question, is this for koodo ppl because of the 3g network?
Click to expand...
Click to collapse
Each carrier will have different APN settings. And in my experience, flashing new ROM's tends to delete APN data... so yeah. In that way, this is Koodo specific in order to get 3G working.
Also, radio-specific as well? haha.
I've noticed the KF1 works on Koodo as well.
UCKB2 radio wont work for me. I have tried others as well without success. Is there any way to know which radio I should use on my koodo Nexus?
gagne.vincent said:
UCKB2 radio wont work for me. I have tried others as well without success. Is there any way to know which radio I should use on my koodo Nexus?
Click to expand...
Click to collapse
I've tried KB2 before with success. KF1 also works for me, and is my current radio.
Ironic
The first time I flashed bios I had a power outage and killed my MB.
Today I killed a whole day figuring out what is wrong with my phone, asking on forums, going back to factory defaults and other ROMS, trying radios. Called the neighbour 10 minute ago and asked him about his Telus phone. "The whole Telus 418 region is out today"
I would be really angry if it wasn't so funny.
Thanks for the simple to follow guide. Worked perfectly the first time. I'm actually on Telus so all I needed was to follow up to flashing the radio button everything just worked when I rebooted.
Sent from my Nexus S using XDA App
clockworkmod version
I would just like to add that you need clockworkmod version 5.
I followed a guide for rooting my nexus s which installed clockworkmod version 3 and ran into some problems. Finally after a bit of stress ended up reading up on clockworkmod and pushed the version 5 installer to my phone, installed it and voilà! I was able to run the installs.
Just thought I would specify in case someone runs into the same problem.
Thanks for your work !
It's nice to know that I'm not the only Koodo-er on here.
I didn't use the guide (already figured it out prior) but it's nice to see one, especially one that's easy to read and well written. It's a nice change from the typical.. stuff.. on xda.
It works! Thanks a lot, very helpful guide. I have a few quick questions though:
- Right now my phone is rooted and has SuperUser installed. I checked through Root Check Basic that I'm rooted and it confirmed it. I didn't understand your steps to make sure Clockwork isn't removed though and I skipped them, so now it's gone. If I simply flash Clockwork again, will I lose my data and have to re-flash ICS?
- Will I get OTA updates given that it's still essentially a stock ROM? I don't mind losing root as the only reason I rooted is to get ICS.
Thanks again!
A few comments for other readers considering this guide
I'm a noob, and I know it. These are comments so any other noobs reading through this thread or Googling the problems I had finds what they were looking for. I'm not criticizing your guide in any way as I know there's a basic expectation of competency on xda and you still went far beyond that and did a great job holding my hand through all the steps. I assume some/most of these comments are obvious to people who actually know what they're doing, but here goes for the other nooblets:
- As someone said previously, it seems you need a new version of Clockwork Recovery. The original guide I used to root my phone installed Clockwork 3.0.1.0 (I think?) and it didn't work. I also had other problems (see below) which only popped up after I installed Clockwork 5.0.2.0, so it's possible that it isn't necessary, but always go for the newer version, I guess. You can flash a new version of Clockwork the exact same way you flashed the older one (I actually repeated the steps in my rooting guide but I swapped the old recovery file with the new one)
- Make sure you back your stuff up first, including a list of all the apps you had installed if you think you might forget. Google didn't reinstall my apps at all despite my having repeatedly checked that backing up to Google was selected in my settings in Gingerbread. The Market remembered the ones I paid for, but I had to log into the Market on my PC to see the free ones to reinstall them. Even then, some were missing and I couldn't find the pattern as to why. This could be my bad as I probably rooted and unrooted and flashed about 5 different ROMS trying to figure everything out last night, but better safe than sorry.
- I initially had a problem installing ZD3PyN0t.zip. It would start opening, then abort and give some kind of error message like "cannot open (BAD) - aborted" and then all I could do was enter (power+volume up) mode. Eventually I figured out that somehow the original "ZD3PyN0t.zip" that I downloaded was corrupted and I couldn't even open it on my PC to explore the files inside. Redownloading it and resending it to my phone via "Mount USB storage" in Clockwork Recovery fixed it. I have no idea how it got corrupted, but if you're getting that error message just delete it and re-download. You can check if it's corrupted the same way mine was by trying to explore the files in the .zip from your computer.
- I didn't need to go through the 3G network settings for some reason. The only network it could find was Telus, which it automatically understood as Koodo and worked immediately. I didn't have the same menu options available to me as OP listed, but in the end it worked. Maybe it's because I left my SIM card in the phone the whole time? I'll never know, point is it worked, so I'm not complaining. So I guess give 3G a try before you tinker with the advanced settings and so on. Keep the settings OP suggested on a file in your phone so that if your 3G ever stops working you can easily configure it on the go. [SEE EDIT]
p.s. for anyone who cares, I'm running a Nexus S I9020A on Koodo in Montreal. Battery life and performance so far seem excellent, although I've been using my phone constantly so I haven't been able to check standby battery life yet. Right now I'd say I'm looking at a total "screen on" time of about 5-7 hours, which is slightly better than I was getting on stock 2.3.6. I'll report back if I have battery problems, but so far it doesn't seem like it.
EDIT: 2 things now that I've been using ICS for a few days.
- Battery life is AWESOME. ICS seems to be better at stopping my phone from being "awake" so much when the screen is off. Battery life during heavy use is slightly better than Gingerbread, but during light use it must be doubled or tripled (i.e.: on pace for many days of on-time, whereas I used to be lucky to get 18-20 hours with Gingerbread even on what I would consider a light day).
- I had some trouble setting up my APN settings right. I was having trouble downloading from the Market and a few sites over 3G, but everything else seemed to work (I'd browse to an app in the Market, click download, and it wouldn't start. Then I'd get "app name" could not be downloaded due to an error. I fixed it by deleting the "Proxy" and "Port" settings from my APN. Credit goes to this thread I found:
So, settings that seem to work:
APN: sp.koodo.com
Proxy: [not set]
Port: [not set]
Username: [not set]
Password: [not set]
Server: 74.49.0.18
MMS Port: 80
MCC: 302
MNC: 220
Authentication type: [not set]
APN type: [not set]
APN Protocol: IPv4
Bearer: [unspecified]
Hi! Thanks for your guide, my wife's Nexus S is now running ISC with Koodo... We are having some problems now:
1.- Search Button fires up way more than before, I've tried to fix this with differents Market Apps w/o luck.
2.- While trying to fix this I discovered that CWM was no longer working, I've tried the Step 10 on your guide but CWM keeps "disapearing" with every reboot.
Every time I need to use CWM, I need to install it from ROM Manager App, Reboot in CWM do my stuff, reboot again and losing CWM again.
3.- Again... while trying to fix the Search button problem, I went to /system/usr/keylayout/cypress-touchkey.kl and edited that file, save and then reboot... when I open back the cypress-touchkey.kl, the changes I've made are gone.
Any hint?
EDIT:
So far I just reinstalled CyberGR-MOD and now ICS is running w/o problems, CWM works, and has been almost 36 hours with out Search Button problems (mi wife needs to test that when shes not at home, as we dont have problems with Search Button at home).
Im using AndroidCommander for windows and im loving it, real cake to move stuff, push and pull apps.
Made an account just to say thanks.
It has been super helpful. I was setting up the phone for my GF and was worried when I couldn't get 3G.
I was worried about the battery life but it's nice to hear other people are finding it good. I got 3G up and running!
vamman said:
My first post. I hope this helps someone else here. I will take you through the steps of updating the Koodo Nexus S to Ice Cream Sandwich 4.0.3, Super User + Root, Radio, and finally APN. This GUIDE is strictly for the Koodo Mobile Network operated by Telus in Canada. I am located in Saint John, New Brunswick and I have been struggling with several aspects of this upgrade especially the lack of 3G after following other tutorials.
Please ensure that you have Clockworkmod installed + super user on a rooted Gingerbread phone.
[WARNING] You must wipe your phone which includes sms, contacts, applications, and the like. I recommend making a backup of your entire device. Search this forum for ways to backup before a complete upgrade. It is rather easy. Google will sync most of your vital information but they won't sync data you create directly on your phone with non-google apps. Once you have your backups made be sure to copy them back your PC.
Now that you have your backup we will download a few files and place them on your SDCARD.
Download the following files:
1. ICS 4.0.3 Official Full Rom: http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip
2. ICS superuser for root: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
4. Radio UCKB2 for i9020a: http://forum.xda-developers.com/showthread.php?t=1116884
Setup
1. Now upload all of these downloaded files to your device's SDCARD via USB Storage.
2. Power off the device.
3. Power on the device into recovery mode. Hold the power button and the volume up. Select recovery using the volume buttons and press the power button to select.
4. Select Mounts and Storage.
5. Format the following: /system /cache /data /boot. Note that I choose not to format /sdcard. It is unnecessary. If you do format /sdcard then you will have to push the files via developer console: adb.exe push file.zip /sdcard/file.zip
6. Go back and select Install zip from sdcard.
7. Select ZD3PyN0t.zip and Install. This will take a few moments.
8. Choose zip from sdcard again and select Superuser-3.0.7-efghi-signed.zip and install. You do not have to install superuser at this point but I strongly recommend it. Originally I was using ICS_su.zip but I believe this is not an official zip but either seemed to work fine. Look on the forums for ICS_su.zip if you have issue with the one I am suggesting here.
9. Choose zip from sdcard again and select XXKB2-radio-nexuss-unsigned.zip and install. This radio is very important. While some other radios might work I found this one to be the most stable for Koodo and identical baseband as Gingerbread was.
10. I lost recovery mode once while doing this an evening ago and I was not sure why this happened. I recommend this additional step at this point. Go back and go to Mounts and Storage. Mount /system. From the Developers console you can run: adb shell rm /system/etc/install-recovery.sh
This automated script can cause you to loose clockworkmod recovery otherwise.
11. Go back and Select Reboot System Now. Wait for your phone to load.
12. At this point you will not have 3G or Data capabilities. You need to setup your google account and wifi. Once the phone is loaded on the home screen it will begin syncing with Google and updating your phone with your data including apps and the like. Once this happens we should now enable 3G. The problem I discovered with my 3G was that the phone was setup for Telus APN. Telus APN will not work with an unlocked Koodo phone in my area.
3G ENABLING STEPS
13. Navigate to Settings > Wireless & Networks > Mobile Networks > Network Operators > Select Koodo
14. Navigate to Settings > Wireless & Networks > Mobile Networks > Access Point Names
Input the following settings for TELUS APN (leaving designated fields blank):
APN: sp.koodo.com
Proxy server: 74.49.0.18
Port: 80
Username:
Password:
Server:
MMSC: http://aliasredirect.net/proxy/koodo/mmsc
Proxy server: 74.49.0.18
Port: 80
MCC : 302
MNC : 220
APN type :
Save (back out of the screen) once you have entered in the details exactly. They must be exact or they will not work. Do not leave any extra data created for TELUS APN.
15. Last step! Turn off Wifi via Settings > Wireless & Networks and you should now see a 3G icon ontop of your bars. You now enabled 3G on ICS!
I just had two friends with Nexus S phones in Atlantic Canada try this and it worked fine for Koodo. I am sure there are similar issues with APN settings for other carriers like Koodo so perhaps this will be of some help to those folks as well.
Click to expand...
Click to collapse
Great post, Just a question though, will this ICS upgrade work for the Galaxy Ace by Koodo as well or just the Nexus?
gordo1701e said:
Great post, Just a question though, will this ICS upgrade work for the Galaxy Ace by Koodo as well or just the Nexus?
Click to expand...
Click to collapse
The general procedure will be the same, but you cant flash a Nexus S ROM and radio to a different phone and expect it to work. If you're already rooted and looking for Koodo-specific APN settings this will work, but find a guide and ROM specific to your phone.
Source for "Easy Method"
Tool Suggested: SQLite Editor by Speedsoftware.
If tethering is still working for you then you don't have to perform these steps.
I am not reponsible for any damages to your phone if you perform these steps, it's your choice, backup first.
Click to expand...
Click to collapse
You must be rooted and on Android 4.4.2 with T-Mobile for this to apply for you. This method worked on my Moto X, but may not work on other devices and software versions.
An explanation of how this works and why it's needed:
T-Mobile has had a second APN (Access Point Name) built into Android 4.4.2 called "DUN" and it is meant to be used only when tethering. It's a way for T-Mobile to check and see if you are using your phone, or if another device is using your connection. If it detects another device, it will only load up a webpage on that device that asks you to buy a Tethering option or switch to a Simple Choice plan that includes tethering. What we will be doing is removing the need for built in Wifi tethering to use or create a DUN APN, and then removing the DUN apn for T-Mobile.
Let's begin.
1. Be rooted. If you have an unlocked bootloader, install CWM or TWRP and then flash Superuser.zip or SuperSU.zip in your recovery of choice. If you have a locked bootloader and you're on 4.4.2, you're currently out of luck. You have to unlock.
2. Open SQLite Editor, grant root for it, then under the APPS list, scroll down and tap on "Settings Storage".
3. It will search for databases and find "settings.db", tap on it.
4. While in "settings.db", select "global" from the list.
5. You will see a table with "id, name and value" columns. Tap on the + sign on the top right to add a new entry.
In the name field, name it: tether_dun_required
In the value field, write the number zero: 0
Tap on Save to save the entry, then exit the app.
6. Go to your APN settings (Settings, More > Mobile Networks > Access Point Names) and you'll notice two APN's there. One labeled "DUN" and one labeled "fast.t-mobile.com." Click on the name of "DUN" and you'll see all of its settings. Hit the menu key in the top right, and choose Delete APN.
7. The "fast.t-mobile.com" APN should be set to IPv4 by default on the Moto X, but on other devices it may be set to IPv6. You need to change this to make tethering work if it is IPv6.
8. Reboot and enjoy!
Your traffic will still be monitored for tethering! You should be using a VPN, proxy, User Agent Switcher, etc. to hide your tethering more effectively.
Hi,
Dear All,
Ok, the problem is very famous i.e. i factory reset my device and when powered one like a fresh piece, i cannot add google account on my G900F (can't establish a reliable connection to the server).
i have searched a lot over the internet. Read about the HOSTS files description as well. All i found was the modification of the "etc/hosts" with the clients.google.... following "#" so that 127.0.0.1 localhost is only the operational entity.
My device is un-rooted and just for the confirmation of the above mentioned, i opened the hosts file via HTML Viewer (just readonly) and found that the etc/hosts file on my S5 has 127.0.0.1 localhost only and no any other information, which i think should be available for your device to work normal and google accounts can be added. See attached screenshot.
Need your kind help in resolving my issue please.
Try clearing caches from recovery
Still same issue...
Might be worth factory resetting again
How did you access the HOSTS files without being rooted?
did the factory reset 3 times but nothing, issue stands unresolved.
i opened the HOSTS file through RARLAB. Actually it allows you to view the root folder and all of its contents even if your phone is un-rooted.
Could try removing the device from Google Play
https://support.google.com/googleplay/answer/2407656?hl=en-GB
Create a new Google account as a test to see if the issue is the phone or the account
If that doesn't help, Id flash a stock ROM through ODIN, this will NOT trip KNOX if you are still 0x0
Are you sure all your data connections are working properly, WiFi/3/4G ?
*Detection* said:
Could try removing the device from Google Play
https://support.google.com/googleplay/answer/2407656?hl=en-GB
Create a new Google account as a test to see if the issue is the phone or the account
If that doesn't help, Id flash a stock ROM through ODIN, this will NOT trip KNOX if you are still 0x0
Are you sure all your data connections are working properly, WiFi/3/4G ?
Click to expand...
Click to collapse
ok here are some interesting occurrences:
Worth mentioning that i was operating over Wi-Fi.
1) - i flashed a stock Kitkat ANG2 ROM via odin and the problem still persists.
2) - Then i flashed stock Lollipop BOB7 and still the same.
3) - Then i created a new account via the first sign in page on the phone (after flashing the new ROM), and i was able make a new account(through my phone) but still it was unable to login on the phone.
4) - Then i installed a Proxy/VPN betternet and then i was able add an account successfully and also Play store is working fine.
5) - Means there is some issue with my wi-fi adapter routing (may be inside the phone or the carrier) etc.
6) - Then i switched off the wi-fi and enabled LTE (of my SIM card provider) and connected my phone through it, say what! its working fine.
7) - again i tried over the wi-fi and the issue started to happen again
Well, one important thing, i am using wi-fi which is also a LTE carrier (having the google issues) and the second LTE (which worked fine) is by the SIM card operator.
So , is there any problem with my wi-fi (inside the phone) or may be with the operator from which i am getting my services??
its quite confusing at the moment. well i am going to try the whole thing over the Wi-Fi of another operator and will feedback the results.
Mean while any suggestions ??
Reboot the router you are connected to WiFi from?
Doesn't sound like the phones fault, unless you have a proxy enabled in WiFI settings or something, sounds like the issue is with your ISP/Router
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.