Related
Just rooted my Canadian Telus Milestone phone and successfully installed CyanogenMod 7. As I am new here, the forum software will not let me post a link to the instructions that I followed. You'll have to add the http stuff to the beginning to make the following link work.
web.cs.dal.ca/~darndt/other/moto-milestone-flash/
I used the Telus 2.2.1 ROM, and then CM7 version: update-cm-7.1.0-RC2.1-11.05.11-Milestone-signed.zip
Eveything works great, except that I cannot enter the APN information for my carrier (Fido / Rogers). Settings | Wireless and Networks | Mobile Networks | Access Point Names is the path I followed. Pressing "menu" at this point gives the option "New apn", which I select. Then nothing. Blank screen. No 'form' to fill in like one usually gets on this phone.
The other option on that screen is "Reset to default". I tried that as well. There are no APN settings available to choose from.
\system\etc\apns-conf.xml is on this phone, and there are three entries there for Fido. None of them are being picked up by the phone, and I have no data connection.
The telephone works. Wifi works. All the apps work. I just cannot enter the Fido APN values, which I know, and which I know work. This phone has run on the Fido network for over a year with no trouble prior to installing the CM7 ROM image.
I've tried posting at (http//android.doshaska.net/cm7, but Nadlabak is but one guy, and he appears to be swamped.
Any suggestions?
Frank.
Frank616 said:
Just rooted my Canadian Telus Milestone phone and successfully installed CyanogenMod 7. As I am new here, the forum software will not let me post a link to the instructions that I followed. You'll have to add the http stuff to the beginning to make the following link work.
web.cs.dal.ca/~darndt/other/moto-milestone-flash/
I used the Telus 2.2.1 ROM, and then CM7 version: update-cm-7.1.0-RC2.1-11.05.11-Milestone-signed.zip
Eveything works great, except that I cannot enter the APN information for my carrier (Fido / Rogers). Settings | Wireless and Networks | Mobile Networks | Access Point Names is the path I followed. Pressing "menu" at this point gives the option "New apn", which I select. Then nothing. Blank screen. No 'form' to fill in like one usually gets on this phone.
The other option on that screen is "Reset to default". I tried that as well. There are no APN settings available to choose from.
\system\etc\apns-conf.xml is on this phone, and there are three entries there for Fido. None of them are being picked up by the phone, and I have no data connection.
The telephone works. Wifi works. All the apps work. I just cannot enter the Fido APN values, which I know, and which I know work. This phone has run on the Fido network for over a year with no trouble prior to installing the CM7 ROM image.
I've tried posting at (http//android.doshaska.net/cm7, but Nadlabak is but one guy, and he appears to be swamped.
Any suggestions?
Frank.
Click to expand...
Click to collapse
I would do a full wipe and start over (installing CM7).
I run my phone on rogers and sometimes fido and have tried most (all?) ROMs on this forum and have never heard of this issue.
You dont need to re sbf the phone. Just do all 3 wipes and reinstall CM7, google apps and choose telus baseband.
If it doesnt work for CM7, give another ROM a try...
Sent from my Milestone using XDA Premium App
Thanks. I'll give that a shot.
Now, you say all 3 wipes. The only wipe that shows up in Androidiani Open Recovery 1.46 is the Dalvik Cache. There are no entries in OR 1.46 for the other two. How do I wipe data and cache?
Thanks for the help. This is the first clear response I've heard so far.
Frank.
Caz666:
OK, quite by accident I found out that OR 1.46 has two additional menu items below "wipe Dalvik cache", but one has to SCROLL to get to them. The remaining two items: factory reset and wipe cache were both there. Once I cleared everything, reinstalled CM7, reinstalled Google apps, and set the baseband to Telus, my phone rebooted clean, and immediately connected to Fido - voice AND data!!!
Funny how the simplest of things can trip up a newbie.
I've been a hobbyist programmer in C and Pascal, I've been running Linux on my home and business computers exclusively for over 5 years, yet I was lost on this new platform.
So satisfying, however, to finally get it to work.
Frank.
My phone is Verizon Droid 3 XT862.
It can't use cdma 3g or 1x network.
SMS and voice is normal. WIFI is normal too.
If i use GSM card, same problem appears.
I flashed the rom , changed the file named 'ppp-rils.option'.
But nothing happened.
Please help me.
thanks.
powerword said:
My phone is Verizon Droid 3 XT862.
It can't use cdma 3g or 1x network.
SMS and voice is normal. WIFI is normal too.
If i use GSM card, same problem appears.
I flashed the rom , changed the file named 'ppp-rils.option'.
But nothing happened.
Please help me.
thanks.
Click to expand...
Click to collapse
Fully restore your phone using my Fast / Easy unbrick method, just search the general section. (All it does is restore your phone to complete stock.)
You can try other stuff, but this method seems to fix most issues that aren't "easy" to fix.
I will try this method.
But I want to know if there are something can be changed or flashed other than this rom.
I want to fix my phone's network.
It not work on cdma , gsm or wcdma.
I flash xt883 rom, but nothing happened.
Can i flash radio? Change hardware setting.
who can tell me.
powerword said:
I will try this method.
But I want to know if there are something can be changed or flashed other than this rom.
I want to fix my phone's network.
It not work on cdma , gsm or wcdma.
I flash xt883 rom, but nothing happened.
Can i flash radio? Change hardware setting.
who can tell me.
Click to expand...
Click to collapse
You don't need the xt883 ROM in order to use the phone on any foreign gsm. The phone must be unlocked by Verizon, then you need to flash the xt883 radio.img, then edit/replace the build.prop. I would flash back to stock first, since the xt883 is a weird ROM, but you probably don't have to. There are already plenty of threads where the explanations have been given, so look around: search Verizon D3 on T-Mobile, D3 on AT&T/T-Mobile, etc.
You will have to turn off 'automatically select operator' in settings and choose manually the one you're using. T-Mobile users will only get edge and below, while AT&T users will get 3g.
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
BenSWoodruff said:
You don't need the xt883 ROM in order to use the phone on any foreign gsm. The phone must be unlocked by Verizon, then you need to flash the xt883 radio.img, then edit/replace the build.prop. I would flash back to stock first, since the xt883 is a weird ROM, but you probably don't have to. There are already plenty of threads where the explanations have been given, so look around: search Verizon D3 on T-Mobile, D3 on AT&T/T-Mobile, etc.
You will have to turn off 'automatically select operator' in settings and choose manually the one you're using. T-Mobile users will only get edge and below, while AT&T users will get 3g.
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
Click to expand...
Click to collapse
I flashed xt862 rom .
Calls and text is OK whether GSM or cdma.
Network is wrong whether GSM or cdma.
I changed APN settings, nothing happened.
What can i do next.
powerword said:
I flashed xt862 rom .
Calls and text is OK whether GSM or cdma.
Network is wrong whether GSM or cdma.
I changed APN settings, nothing happened.
What can i do next.
Click to expand...
Click to collapse
I'm not sure what is wrong with your connection, but mine has problems sometimes where the phone will not recognize any available gsm networks. It's sometimes like this after I reboot my phone, but if changing my settings doesn't work, rebooting again will usually work.
Is your phone unlocked by Verizon? Did you flash the xt883 radio.img since changing your ROM? Did you replace your build.prop file with the tweaked one? I will try to find these resources for you if you still need them, but you should be able to find them by searching if you haven't already. After doing these things, you just have to reboot then go to your settings and tell it to prefer gsm. On T-Mobile, you wont get umts. On AT&T you will get gsm and umts.
In settings, you need to select wifi & network settings -> mobile networks -> network mode -> then choose gsm/umts, back to mobile networks -> under gsm/umts settings, click select network, then choose gsm only for T-Mobile or automatic for AT&T, then click operator select, select network and choose your operator. Select automatically will have a check box next to it and you should deselect it. I didn't have to put in my apn settings, because my sim card provides those automatically.
If these settings tweaks don't work for you then I really have no clue what will fix it because it is likely that something else is wrong. I can't be of much more help without seeing the device. I would suggest to keep playing around in settings and just use your head to see why it's not connecting. If you are getting voice and text service on your carrier, data shouldn't be a problem if your settings are done correctly.
Good luck!
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img & custom build.prop
[HOWTO] / [GUIDE] SPH-L720 Domestic SIM Unlock T-Mobile:AT&T:metroPCS:Straighttalk
Streamlined Guide for Domestic T-Mobile GSM Unlock for SPH-L720
Credit for all of this goes to @autoprime and @nicotheandroidguy
A few notes: I used Windows 7 for the odin flashes , my phone is a SPH-L720 and it is not active on the Sprint network, also the sim card from t-mobile was inactive (brand new from t-mobile store.) and it has a bad esn. I am located in the Phoenix az market so I'm able to take advantage of the 1900mhz band that tmobile has here.
I'm unsure of how this will work with mnvos or other primary carriers and frankly I don't care at the moment, this is my primary phone. Update: confirmed hspa+ for tmobile, metroPCS, straight talk and AT&T.
I HAD MY NEW UNACTIVATED TMOBILE SIM CARD IN THIS ENTIRE TIME
1) First I reverted my rom to a stock MF9 rooted touchwiz rom, instructions and one click odin here:http://forum.xda-developers.com/showthread.php?t=2486134 I’m trying not to straight copy and paste someone else’s work so take a look at that post if you need a clean start. If you are coming from non stock you will need to boot into stock recovery and wipe data/cache before you get started. (I also later used SAC’s rom after a failed attempt at an AOKP fix and it worked as well ) you can switch to any ROM later and the unlock will stick.
2)I rebooted the phone and followed the instructions listed here in post #1 http://forum.xda-developers.com/showthread.php?t=2415587
3) I went to the dialer and typed *#0011# which brought me to the "service mode" Menu.
IF YOU HAVE TROUBLE GETTING THE HIDDEN MENU TO OPEN DO NOT FEAR! I had a ton of trouble at first. In some builds you need to activate an option by adding a line to your build.prop or changing the no flag in efs/hiddenmenu to ON. Google it, there is a ton of help out there.
4) Press the left menu softbutton (the menu button that lights up and vibrates when you touch it) then press the either the button “select” or “Key Input” and type the number 1 or 2 into the box, if nothing happens press menu and select the “back “ button then repeat. This app is sort of like a tin can radio, you can kind of tell that it’s working, but it doesn’t work well.
Depending on if you pressed 1 or 2 in the dialogue box it will take you into either an UMTS or CDMA menu. If you are in the umts menu, press the menu button and select back, this should then proceed to the next step.
5) Select CDMA, then 1.COMMON, press next page twice until you reach page three of COMMON and select 8.PREF MODE SET and select GSM_WCDMA_ONLY
6) Press menu and back until you are at the main menu and select [1]UMTS, then select [1]DEBUG SCREEN, then select [6]PHONE CONTROL, select [2]FAKE SECURITY CONTROL and make sure it is set to ON
7)Press menu and back and select [3] NAS CONTROL. We are going to check a few different settings in this menu so remember how to get here cause I don’t want to repeat myself.
[1] CIPHERING CONTROL = OFF
[2] INTEGRITY CONTROL =ON
[3] SIM CLASS CONTROL = UMTS
[4] REVISION CONTROL = DO NOT TOUCH
[5] RRC(HSPA) CONTROL = DO NOT TOUCH
[6] DUALMODE IMPROVEMENT CONTROL= DO NOT TOUCH
[7] NAS AVOID SECURITY CONTROL= OFF, 0
[8] BIP BLOCK = 1
8) Press menu and back twice, you should be on the PHONE CONTROL menu. Select [7] NETWORK CONTROL, select [1] GFC and make sure that it is set to [1]GSM/(E)GPRS/WCDMA REL8 .
9) Press menu and back and select [2] BAND SELECTION and select WCDMA/GSM ALL for both WCDMA and GSM band preferences. I selected the ALL choice for LTE as well even though I know it isn’t supported for TMOBILE.
10) Under the NETWORK CONTROL menu we just came from select [4] AQUISITION ORDER and change it to [3]UMTS_GSM
11) Press menu and back until you are in the PHONE CONTROL menu and select [5] SIMULATION , press the [2] SW WATCHDOG button 6(six) times and then the [3] HW WATCHDOG 6(six) times. Nothing will happen at all to let you know if you have done this correcctly but as soon as you finish the sixth press on HW WATCHDOG reboot the phone manually:manually:manually IMMEDIATELY . I’m not sure what this does or why this works but @nicotheandroidguy seems to have divined that this is the vital part of the process.
YOUR PHONE STILL WILL NOT HAVE DATA OR VOICE WHEN YOU REBOOT FROM THE WATCHDOG TAPS DO NOT PANIC!!!!!!!!!!! (hopefullly you have your towel with you)
12) WIFI that sonofa up and search for apn settings shortcut and build.prop editor in the Play Store.
Go into the build.prop editor and add the following two lines:
ril.sales_code=LOL
ro.csc.sales_code=LOL
REBOOT PHONE MANUALLY now.
Now Install and create a shortcut on the home screen and select to open. Press the menu soft key and select add apn.
Use:
Name: T-Mobile
APN: epc.tmobile.com or fast.t-mobile.com (for LTE devices)
Proxy:
Port:
Username:
Password:
Server:
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS proxy:
MMS port:
MMS protocol: WAP 2.0
MCC: 310
MNC: 260
Authentication type:
APN type: default,supl,admin,dun,mms
13) Go into your android settings, select wireless networks, you should see the network mode set as wcdma only do not change this, we set this in the Service Mode Menu , Check that your roaming settings are set to for roaming data/ international data etc.also make sure that there are no roaming guards left on. (roaming guards will only allow you to uncheck GSM and GSM data under international roaming.)
14) reboot
15) profit
At this point I had full access to the TMOBILE UMTS/HSPA+ network and voice/text/mms were working.
At this point you may change roms, be careful not to update past mf9 as you may be unable to downgrade to mdc. YOU MUST DOWNGRADE TO MDC MODEM FOR THIS TO WORK.
If you use a non touchwiz rom you can still access the tellinfo menu by pressing *#*#4636#*#* and selecting WCDMA only and manually adding the apn.
GOOD LUCK! let me know what needs changed in the guide as well.
If you have questions it's useful to know your Baseband /kernel/ rom.
Nice. Will it work with t-mobile in Los Angeles?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Thank you for this thread, I will try again with these steps.
A few notes:
imbmiller said:
3) i went to the dialer and typed *##0011# which brought me to the "service mode" menu.
Click to expand...
Click to collapse
This should be *#0011# I believe
imbmiller said:
5) Select CDMA, then 1.COMMON, press next page until page three of COMMON and select 8.PREF MODE SET and selet GSM_WCDMA_ONLY
Click to expand...
Click to collapse
I had to go 9. NEXT PAGE > twice before doing 8.
gibrannz said:
Nice. Will it work with t-mobile in Los Angeles?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
According to this :https://t-mobile.jive-mobile.com/#jive-document?content=/api/core/v2/documents/5736
Yes it will. Hspa+ only though.
the.joeba said:
Thank you for this thread, I will try again with these steps.
A few notes:
This should be *#0011# I believe
I had to go 9. NEXT PAGE > twice before doing 8.
Click to expand...
Click to collapse
Np Man, and good catch, fixed. I'll check out that step 8/9 and fix accordingly.
Thank you so very much. I believe opening up the bands made the difference, but I'm now connected to T-Mobile.
You rock so much!
the.joeba said:
Thank you so very much. I believe opening up the bands made the difference, but I'm now connected to T-Mobile.
You rock so much!
Click to expand...
Click to collapse
HELL YEAH MAN! I'm stoked that you were able to get it working. I pulled most of this info from the other threads but I'm glad if it made it easier.
got working for att post paid
Thanks to everyone here.
ka26 said:
Thanks to everyone here.
Click to expand...
Click to collapse
Most excellent! If you fiddle with acquisition order and make it gsm_umts it might identify your network type correctly.
My 1st newbie post:
Thanks for OP's excellent post!:good:
I have a Sprint Galaxy S4 is with stock MF9 (not unlocked).
I have spent days reading about how to get a rooted/unlocked MJA S4. But still could not find answer to the questions:
1. Will this also unlock international sim?
I guess yes, as domestic is harder to unlock. But want to hear the confirmation.
2. You mentioned you used MF9 rooted.
If I unlock it, then update to MJA, will that void the unlock?
3. Does this unlock works with MJA? If it works, do I need to unlock MJA first?
4. If I want a rooted & unlocked S4 with stock MJA, what is the simplest way and the correct order to achieve this goal?
Can I update to MJA, then root, then unlock?
Or do I need to root the MF9, then unlock, then update to MJA, then root?
If I update to MJA first, I can't go back to MF9, correct?
Thank you very much!
staplestaples
staplestaples said:
My 1st newbie post:
Thanks for OP's excellent post!:good:
I have a Sprint Galaxy S4 is with stock MF9 (not unlocked).
I have spent days reading about how to update to MJA and root/unlock it.
But still could not find answer to the questions:
1. Will this also unlock international sim?
I guess yes, as domestic is harder to unlock. But want to hear the confirmation.
2. You mentioned you used MF9 rooted.
If I unlock it, then update to MJA, will that void the unlock?
3. Does this unlock works with MJA? If it works, do I need to unlock MJA first?
4. If I want a rooted & unlocked S4 with stock MJA, what is the simplest way and the correct order to achieve this goal?
Can I update to MJA, then root, then unlock
Do I need to root the MF9, then unlock, then update to MJA, then root?
Thank you very much!
staplestaples
Click to expand...
Click to collapse
Ok
1)i am unsure of whether mja can be unlocked internationally or domestic . If you read the first direction it actually instructs you to downgrade to mdc modem. I'm pretty sure the reason has to do with the options available to you in the hidden menu.
2)i used mf9 rooted as a starting point to downgrade to mdc to perform the international unlock. Autoprime said in the thread that upgrading to mf9 would keep the u lock however I haven't successfully upgraded to mf9 and kept the domestic unlock. I'm going to try to get it to work today but not with mja until there is a reliable downgrade option.
3)i have no idea. I wouldn't suggest trying until there is a reliable downgrade option.
4)i would really slow down and read the international unlock guide from @autoprime I think it will answer a lot of your questions. Like I said I would wait to upgrade to mja if you want a for sure domestic Sim unlockunlock.
Thank you very much, imbmiller.
I will just wait patiently for the MJA solutions before upgrading to MJA/root/unlock.
imbmiller said:
Ok
1)i am unsure of whether mja can be unlocked internationally or domestic . If you read the first direction it actually instructs you to downgrade to mdc modem. I'm pretty sure the reason has to do with the options available to you in the hidden menu.
2)i used mf9 rooted as a starting point to downgrade to mdc to perform the international unlock. Autoprime said in the thread that upgrading to mf9 would keep the u lock however I haven't successfully upgraded to mf9 and kept the domestic unlock. I'm going to try to get it to work today but not with mja until there is a reliable downgrade option.
3)i have no idea. I wouldn't suggest trying until there is a reliable downgrade option.
4)i would really slow down and read the international unlock guide from @autoprime I think it will answer a lot of your questions. Like I said I would wait to upgrade to mja if you want a for sure domestic Sim unlockunlock.
Click to expand...
Click to collapse
So would this also work for AT&T sim? has anyone else tried? Btw, was thinking of updating to 4.3 and MJA but i guess i will have to hold off on that if i want sim unlock international or domestic? I am on MF9 with sim international unlock right now. Would I have to go down to MDC to get this to work?
Also, if you want to go back to sprint again, how would you do it?
wildpig1234 said:
So would this also work for AT&T sim? has anyone else tried? Btw, was thinking of updating to 4.3 and MJA but i guess i will have to hold off on that if i want sim unlock international or domestic? I am on MF9 with sim international unlock right now. Would I have to go down to MDC to get this to work?
Also, if you want to go back to sprint again, how would you do it?
Click to expand...
Click to collapse
You can use MF9, MDL and MDC for the domestic unlock.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi thanks so much for putting this together all in one place!
Hi I'm on MF9, rooted, locked.
So really the two major steps are:
1. Do int'l unlock first (autoprime)
2. Then do domestic unlock
My question - after you get both unlocks working and say you have your phone working on tmobile, what do you need to do to get it working on Sprint... rather, is the phone operatable on both Sprint and Tmobile? Or do you have to do some tinkering to get it back to working on Sprint again. I'd like to have the flexibility of popping SIMs in and out and switching carriers at will, Sprint included (b/c I don't want to cancel Sprint just yet...eventually, but not immediately). Thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
Another question
When you're tinkering with swapping out modems and APN settings, does doing a nandroid backup prior help so when you have an "oh sh!t" moment, you can just do a full restore...? Or is what's backed up in nandroid outside (excludes) these changes? Thanks.
laoh said:
Hi thanks so much for putting this together all in one place!
Hi I'm on MF9, rooted, locked.
So really the two major steps are:
1. Do int'l unlock first (autoprime)
2. Then do domestic unlock
My question - after you get both unlocks working and say you have your phone working on tmobile, what do you need to do to get it working on Sprint... rather, is the phone operatable on both Sprint and Tmobile? Or do you have to do some tinkering to get it back to working on Sprint again. I'd like to have the flexibility of popping SIMs in and out and switching carriers at will, Sprint included (b/c I don't want to cancel Sprint just yet...eventually, but not immediately). Thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
Another question
When you're tinkering with swapping out modems and APN settings, does doing a nandroid backup prior help so when you have an "oh sh!t" moment, you can just do a full restore...? Or is what's backed up in nandroid outside (excludes) these changes? Thanks.
Click to expand...
Click to collapse
OK the answer to the first question is to put your sprint sim card back in then put your phone back in to lte/cdma auto through the tell info app through Google play device info then change it in to lte/cdma auto.
Answer to the second question is that the nandroid might help you in a oh sh!t moment but the modem and settings for the unlock stay after a factory rest but a other update could kill it. A stock Odin flash and dailing ##72786# could also kill both unlocks.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Someone on this thread got it to work. I'm unsure if Att has hspa+ tho so you might be relegated to edge
Nevermind, it works on Metro it just matters the SIM http://forum.xda-developers.com/showpost.php?p=47624568&postcount=568
Did you install hiapn and add the apn? What baseband are you on? What rom and kernel? I'm not super positive about mvno s but I'd probly go back to the beginning and start over.
imbmiller said:
Did you install hiapn and add the apn? What baseband are you on? What rom and kernel? I'm not super positive about mvno s but I'd probly go back to the beginning and start over.
Click to expand...
Click to collapse
Sorry I had to edit my post. It did work. There are two different GSM SIMs the one with the dot seemed to work. I Got Edge, 3G, and H+. It is awesome. I also still have 3G with Sprint with the SIM in. I got two phones in one. Thanks.
So I've been on T-Mobile for the last 24 hours but my HSPA+ signal is weak and slow (under 1mb), while my co-worker on T-Mobile (and a T-Mobile phone) has full HSPA+ signal and speed (5-9mb).
Any thoughts on what could be the cause?
I'm running CM11 on MDC. I'll try some other combinations tonight to see if things change.
This may be an old question, but I've been unable to find an answer...
I have an off-contract verizon Droid 3. So I flashe the radio ROM with the Chinese 883 variant. I took it to the UK and put a "3" SIM into it. I got voice + txt, but I didn't get data.
(I didn't have a PC in the UK so I couldn't do more testing... had to wait until I got home)
OK, I come back to the US and I do some testing...
I rebuild from scratch with 5.7.906. I force the machine into GSM mode. Then I use "Network System Information" (NSI). I see my SIM card; my UK phone number, MMC, MNC. But, of course, it doesn't work in the US becuase the phone won't talk to US GSM networks with Verizon firmware.
I change the radio to the Chinese radio.img, as per http://forum.xda-developers.com/showthread.php?t=1406812 - I also replace build.prop, /system/lib/libmoto_ril.so and /system/etc/ppp/peers/pppd-ril.options
Now I reboot and I can see the GSM network (T-Mobile, in this case), but NSI doesn't get to see SIM contents; no phone number, no MNC, no MMC. And so I'm back to phone+txt but no data; the APN isn't picked up.
Do I need to do something else to get data working?
(Probably if I leave it with the Verizon radio ROM then next time I go to England I'll get data, but it means I don't get the SIM working while in the US).
sweh said:
This may be an old question, but I've been unable to find an answer...
I have an off-contract verizon Droid 3. So I flashe the radio ROM with the Chinese 883 variant. I took it to the UK and put a "3" SIM into it. I got voice + txt, but I didn't get data.
(I didn't have a PC in the UK so I couldn't do more testing... had to wait until I got home)
OK, I come back to the US and I do some testing...
I rebuild from scratch with 5.7.906. I force the machine into GSM mode. Then I use "Network System Information" (NSI). I see my SIM card; my UK phone number, MMC, MNC. But, of course, it doesn't work in the US becuase the phone won't talk to US GSM networks with Verizon firmware.
I change the radio to the Chinese radio.img, as per http://forum.xda-developers.com/showthread.php?t=1406812 - I also replace build.prop, /system/lib/libmoto_ril.so and /system/etc/ppp/peers/pppd-ril.options
Now I reboot and I can see the GSM network (T-Mobile, in this case), but NSI doesn't get to see SIM contents; no phone number, no MNC, no MMC. And so I'm back to phone+txt but no data; the APN isn't picked up.
Do I need to do something else to get data working?
(Probably if I leave it with the Verizon radio ROM then next time I go to England I'll get data, but it means I don't get the SIM working while in the US).
Click to expand...
Click to collapse
Grab a T-Mobile prepaid SIM so you can test further. You shouldn't have to replace any files except the radio and build.prop for the 883 Chinese radio from the Verizon XT862 radio/build.prop.
MrObvious said:
Grab a T-Mobile prepaid SIM so you can test further. You shouldn't have to replace any files except the radio and build.prop for the 883 Chinese radio from the Verizon XT862 radio/build.prop.
Click to expand...
Click to collapse
OK, I rebuilt back to Verizon factory just so I have a clean slate.
I don't have a T-Mobile SIM but I do have an (expired, deactived) UK Virgin Mobile SIM.
I put that in the phone with the Verizon Radio ROM and, as expected, it won't connect to AT&T. NSI will show me the MNC, MCC, phone number and othe SIM details.
I switch to Chinese ROM and build.prop... and I can still see the details! This is something new...
OK, with that level of success I switch back to the 3 SIM card. And... no data.
So:
Verizon Radio and build: 3 SIM visible in NSI but won't connect. Virgin SIM visible in NSI but won't connect
Chinese Radio and build: 3 SIM _not_ visible in NSI. Connects for voice+txt, no data. Virgin SIM visible but won't connect ('cos expired)
Hmm, looks like some interaction between the radio and the SIM. Odd!
Sorry I meant get a T-Mobile SIM so you can test the 883 radio.
What testing are you proposing? Other than "data works with a T-Mobile SIM" of course
Since the MNC and MMC aren't visible with the Chinese ROM and the 3 SIM, no APN is selected and so no data... with the Virgin SIM the MNC and MMC are visible and I can see APNs in the APN settings screen.
all i ever did was 1. get unlock code , 2.flash 883 radio , 3. change build,prop.
have to root first of course.
never ran into an issue except once when i accidentally erased some files in the system folder.
I have never understood why install xt883 radio when xt862 works great with gsm networks (all G/E/3G/H connection modes with data). Is there any reason for doing that?
trethon said:
I have never understood why install xt883 radio when xt862 works great with gsm networks (all G/E/3G/H connection modes with data). Is there any reason for doing that?
Click to expand...
Click to collapse
The xt862 radio is unlocked for gsm networks outside the US, but will not allow US GSM SIMs from T-Mobile and AT&T to work.
doogald said:
The xt862 radio is unlocked for gsm networks outside the US, but will not allow US GSM SIMs from T-Mobile and AT&T to work.
Click to expand...
Click to collapse
It's not the SIM, it's the network. A UK "3" SIM won't join T-Mobile or AT&T with the Verizon radio ROM, but it will with the alternate ROM.
SOLUTION
Hi and morning to you. I work for your carrier (TECH SUPPORT) so i think i know what the issue is. you can call them and verify this i'm sure they will agree but dont mention my name
3 sim card only works on 3g network and when you put the phone in a 2g phone it dosent. i know the droid 3 is 3g but like you there are 80 % d3 owners having same issue of no 3g data. when you root and install a rom the data capability goes away. try this .......
set up a new apn WITH ► NAME : 3, ► APN : THREE.CO.UK and go to last option ► apn type and type the word "default" then save and reboot. dont forget to activate mobile data. i think it will at least give you 2g kind of internet. i have droid 3 and i took it when i was in the u.s and now in india
lemme know it it works. forgot to mention....there is patch to get 3g data working (google) it.
Lycanist said:
lemme know it it works. forgot to mention....there is patch to get 3g data working (google) it.
Click to expand...
Click to collapse
No this doesn't work because the MNC and MCC aren't visible and so the phone won't select the APN.
Sad it dosent work. Why dont you upgrade phone to Droid 3 stock (download unbrick Droid .bat from Droid 3 developement unbrick/root 1st post and then start from scratch like rooting , safestrap stc ) in case if u flash n if there is no signal then activate roaming. I have done d same.
Sent from my XT860 using xda app-developers app
---------- Post added at 09:39 AM ---------- Previous post was at 09:28 AM ----------
Hi again, try this n lemme know if it worked
Go to d link n read apn modify via *#*#
http://forum.xda-developers.com/showthread.php?t=1633163
Sent from my XT860 using xda app-developers app
Lycanist said:
Sad it dosent work. Why dont you upgrade phone to Droid 3 stock (download unbrick Droid .bat from Droid 3 developement unbrick/root 1st post and then start from scratch like rooting , safestrap stc ) in case if u flash n if there is no signal then activate roaming. I have done d same.
Click to expand...
Click to collapse
That's exactly what I did; I reflashed to 5.7.906 using moto-fastboot. With the VZW radio ROM I can see the SIM MNC MCC but (of course) it won't talk GSM in the US. With the Chinese radio ROM it'll talk to the network but without data 'cos it doesn't see the MNC MCC.
The whole question is moot now 'cos I've now got an S4 and cut the SIM to size; that works just fine
sweh said:
That's exactly what I did; I reflashed to 5.7.906 using moto-fastboot. With the VZW radio ROM I can see the SIM MNC MCC but (of course) it won't talk GSM in the US. With the Chinese radio ROM it'll talk to the network but without data 'cos it doesn't see the MNC MCC.
The whole question is moot now 'cos I've now got an S4 and cut the SIM to size; that works just fine
Click to expand...
Click to collapse
I've ported xt861 (2.3.6) rom to xt862 (called it cROM) to use it in Europe/Poland, but have same problem with data transfer. The solution was:
1. download full apns-conf.xml file with most of world networks apns (about 160kb)
2. copy the file to /system/etc/apns-conf_0.xml
3. create two links
ln -s /system/etc/apns-conf_0.xml /system/etc/apns-conf_.xml
ln -s /system/etc/apns-conf_0.xml /system/etc/apns-conf.xml
4. reboot
Try this (from terminal):
su
rm -R /data/data/com.android.providers.telephony/databases
reboot
I just got my wife a Nexus 6 from Craigslist. I foolishly didn't 100% test the phone and I think I got a lemon or something.
Her phone has never connected to LTE. I've tried manually changing APNs, swapping SIM cards with my phone to see if the card is bad, checking the phone settings by dialing *#*#4636#*#*, etc... And everything is identical to my Nexus 6 with no luck. I went to a T-Mobile store just now and they couldn't figure anything out.
Two questions:
1. Is there anything else I can do to get LTE activated?
2. Can an LTE radio be damaged or disabled somehow?
I'm at my wit's end here... I'm hoping y'all can help me get it fixed.
Thanks!
1st is the phone running stock or a custom rom? .second try to reset your apn setting to default and using the setting that the phone provides in apn
It is stock, no customization or rooting.
I'll try the default when my wife gets back from the store and report back.
Reset APN to default settings, no luck.
The previous owner was on a smaller carrier, like a Metro PCS or something similar... Can't remember, but I don't know if their settings are different than T-Mobile's.
Yes their settings are diff... metro is fast.metropcs.com for apn inside and tmobile is fast.t-mobile.com. You can try clicking the apn make sure its fast.t-mobile.com and check the ipv and set to ipv6 and ipv4 for roaming. Then at the very bottom under MVNO select None. Then restart phone. If your still not pulling up data you may want to push a radio image to the device possibly and maybe the radio firmware is screwed up since your not original owner of the device.
All the APN settings are correct and identical to my working Nexus 6.
Are there tutorials on how to push a radio image and where to get said radio image?
https://www.androidpit.com/how-to-update-nexus-5-bootloader-and-radio - Nexus 5 instructions but they are the same just download nexus 6 files instead from here
https://dl.google.com/dl/android/aosp/shamu-mob30i-factory-21357b09.tgz - MOB30I Latest Marshmallow files...
When you follow that guide you could just flash-all command it and flash marshmallow stock in its entirety... it would flash latest bootloader and modem with it or you can extract the modem and bootloader files from the file and follow the guide. If you dont care whats on device you may want to just flash the whole thing and skip the extracting the modem and bootloader parts.
**Obviously since you'd be replacing the nexus 5 files with 6 files aka shamu instead of hammerhead change the names in the commands you type in fastboot. Just a reminder.
Thanks so much for the help!
I'll try this later and let you know if it works.
hermunn123 said:
Thanks so much for the help!
I'll try this later and let you know if it works.
Click to expand...
Click to collapse
No problem and best of luck on it.
hermunn123 said:
I'm at my wit's end here... I'm hoping y'all can help me get it fixed.
Click to expand...
Click to collapse
Enter into the bootloader and check the Product/Variant information within. For the US, it should read "shamu XT1103" followed by the memory size and a hexadecimal string. If it reads "shamu XT1100", you have the international model, which would explain the trouble you're having. Another possible explanation, especially if the model is "shamu XT1103", is that the device is blocked on T-Mobile.
To answer your questions:
1. If you have an international model, you may be able to activate the missing bands necessary to support LTE here in the US. Otherwise, flash the latest ROM from Google, as there are settings in the services menu you accessed which once selected cannot be changed unless a new ROM image is flashed.
2. LTE radios can both be damaged and disabled. The LTE could be disabled in the service menu, or the hardware is damaged.
Strephon Alkhalikoi said:
Enter into the bootloader and check the Product/Variant information within. For the US, it should read "shamu XT1103" followed by the memory size and a hexadecimal string. If it reads "shamu XT1100", you have the international model, which would explain the trouble you're having. Another possible explanation, especially if the model is "shamu XT1103", is that the device is blocked on T-Mobile.
To answer your questions:
1. If you have an international model, you may be able to activate the missing bands necessary to support LTE here in the US. Otherwise, flash the latest ROM from Google, as there are settings in the services menu you accessed which once selected cannot be changed unless a new ROM image is flashed.
2. LTE radios can both be damaged and disabled. The LTE could be disabled in the service menu, or the hardware is damaged.
Click to expand...
Click to collapse
I have same problem. I have XT1100 on T-Mobile, but I can only use 3G. How to see which LTE bands on this devices are activated?
If you have an XT1100 in the US you're missing bands 2, 4, 12 and 17. Of those, bands 2 and 4 are the most important as AT&T and T-Mobile both use those bands extensively. And unlike the US model, Verizon and Sprint won't work at all. Search the General forum, as there is a thread on how to add bands to the radio. Be warned however. When I attempted it on my Galaxy S4 I nearly bricked the device.
Also (and I know its basic) but check under settings ---> mobile ---> preferred network type and make sure it says LTE (just on the off chance it was switched somehow)