Related
Like most Droid 3 owners I'm sure, I'm tired of paying ~$105 a month for cellphone service through Verizon that I could be paying ~$70 a month for through T-Mobile.
I've read the other thread here associated with unlocking the GSM portion of the Droid 3, but a lot of it seems to be shrouded in maybes and varied successes with a limited pool of test devices to draw on.
From what I gather thus far, the following is true:
- You can unlock the GSM capability of the Droid 3
- You can operate it on T-Mobile
- If you do, you will only get "Edge" connection speeds - No T-Mobile HSPA+ or 3G speeds. "Edge" only, at 512 kb or something like that.
Can anyone confirm this? Is there a way to get a Droid 3 to operate on T-Mobile's network at full speed?
Is there a more reliable and easier to use method to convert a stock VZW Droid 3 to something operable on T-Mobile?
Thanks in advance to anyone who can accurately answer these questions.
The only thing I've seen that works is using the xt883 Chinese ROM and it only gets edge. Edge is fine for me, but I want a better ROM with access to Android market.
Im still learning how this device works; I just installed Safestrap and tried to flash the GSM CM7 ROM today, to no avail. I flashed a custom ROM on my Droid 2 last year, but it's been a while on the G2x which isn't as locked down.
I flashed the CM7 GSM ROM on the safe mode partition, thinking that was how to do it, but I got an error trying to back anything up because /system wouldn't back up. Then when I flashed the ROM it wouldn't boot. Im wondering if I was supposed to flash the ordinary CDMA CM7 first, then use the GSM one, since it's named 3gedit.zip. I haven't tried that yet though, and the fact that /system isn't backing up worries me. I didn't create a partition on internal with Safestrap, but I flashed the GSM CM7 ROM from coreless in safe mode and it wouldn't boot. Got back to non-safe mode and my stock ROM was fine, but I still want to see a good back up :-/
Any ideas from more experienced users would be great. I'm pretty much a blind guinea pig right now lol. I just really want to see CM7 on this D3, and have it work on T-Mobile so I can retire my G2x for a little while.
Thanks in advance
Sent from my DROID3 using Tapatalk
Tutorial
note: This is not tied to any specific rom, it is not using the chinese rom it is simply taking the radio off the chinese rom which is all we need. It hasn't changed anything to me in user space that I have noticed.
I would recommend unlocking, rooting, flashing the radio, and editing the build.prop.
1. Unlock or online sim card unlock code seller but less reliable.
a) Meet the following requirements:
* Must be a Verizon Wireless customer.
* The phone being unlocked must be active on a Verizon Wireless line of service.
* The line of service must be active at least 60 days.
* The line of service must be in good standing for the past 60 days.
* Only one SIM Unlock per line every 10 months.
b) If you don't meet one or more of the above requirements, call anyway. You may still get lucky.
Call 1-800-711-8300 (Verizon Global Support) and ask the representative for a SIM unlock. Occasionally a representative may not know exactly what you are referring to; make sure you are not transferred to a different department. You are in the right place. Explain that they should have a walkthrough on how to do this, and that it allows for the use of local, non-Verizon SIM cards while traveling abroad.
c) Insert a foreign SIM into the SIM card slot on the side of your phone and then enter unlock code.
4. root ----> http://www.psouza4.com/droid3/
5. safestrap and backup in case something goes wrong -----> http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
6. chinese radio ----> http://dropbox.com/u/25454276/radio.zip
7. flash radio ----> http://dl.dropbox.com/u/16206920/moto-fastboot-win32.zip
8. use something like root browser lite(free) to backup to sd card then edit your system/build.prop
gfunkmonk said:
All you have to do is flash the radio.img from SOLANA_SLNCT-57.1.60_Fastboot in fastboot mode
Code:
moto-fastboot flash radio radio.img
then add the following lines to the build.prop
Code:
persist.ril.rssi.enable.param6 = 1
persist.ril.baudrate=230400
I can confirm this works with an AT&T sim in an unlocked phone, tested with stock and liberty 2.0.
Click to expand...
Click to collapse
I have called out, received a call and a text, I have checked my account information with the tmobile app on edge. I have been led to believe that its hardware that tmobile can only do edge since they use some non standard bands.
Credits:
flashing radio - http://forum.xda-developers.com/showthread.php?t=1360157
unlocking - http://community.vzw.com/t5/iPhone-4S/Verizon-iPhone-4S-SIM-UNLOCK-Tutorial/td-p/696707
safestrap - http://forum.xda-developers.com/showthread.php?t=1315982
Even if you go through all of that you I'll still have only EDGE because our radios don't use the 700 MHz. Just sell it and get a phone for T-Mobile.
Sent from my XT862 using XDA App
BenSWoodruff said:
The only thing I've seen that works is using the xt883 Chinese ROM and it only gets edge. Edge is fine for me, but I want a better ROM with access to Android market.
Im still learning how this device works; I just installed Safestrap and tried to flash the GSM CM7 ROM today, to no avail. I flashed a custom ROM on my Droid 2 last year, but it's been a while on the G2x which isn't as locked down.
I flashed the CM7 GSM ROM on the safe mode partition, thinking that was how to do it, but I got an error trying to back anything up because /system wouldn't back up. Then when I flashed the ROM it wouldn't boot. Im wondering if I was supposed to flash the ordinary CDMA CM7 first, then use the GSM one, since it's named 3gedit.zip. I haven't tried that yet though, and the fact that /system isn't backing up worries me. I didn't create a partition on internal with Safestrap, but I flashed the GSM CM7 ROM from coreless in safe mode and it wouldn't boot. Got back to non-safe mode and my stock ROM was fine, but I still want to see a good back up :-/
Any ideas from more experienced users would be great. I'm pretty much a blind guinea pig right now lol. I just really want to see CM7 on this D3, and have it work on T-Mobile so I can retire my G2x for a little while.
Thanks in advance
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
go here http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Thanks for replying. That's where I wound up going on my own because I was trying to use his CM7 last night. Can't seem to get it to flash though. Backing up with Safestrap isn't working either...getting an error because /system won't backup for some reason.
I think I'm gonna flash everything back to stock, uninstall Safestrap, and try the above from the beginning. I'd like to see if I can at least get edge and below on T-Mobile using a US ROM.
Thanks again!
G2x with CM7
D3 stock for now, trying to get T-Mobile compatibility
anathema_forever said:
I would recommend unlocking, rooting, flashing the radio, and editing the build.prop.
1. Unlock or online sim card unlock code seller but less reliable.
a) Meet the following requirements:
* Must be a Verizon Wireless customer.
* The phone being unlocked must be active on a Verizon Wireless line of service.
* The line of service must be active at least 60 days.
* The line of service must be in good standing for the past 60 days.
* Only one SIM Unlock per line every 10 months.
b) If you don't meet one or more of the above requirements, call anyway. You may still get lucky.
Call 1-800-711-8300 (Verizon Global Support) and ask the representative for a SIM unlock. Occasionally a representative may not know exactly what you are referring to; make sure you are not transferred to a different department. You are in the right place. Explain that they should have a walkthrough on how to do this, and that it allows for the use of local, non-Verizon SIM cards while traveling abroad.
c) Insert a foreign SIM into the SIM card slot on the side of your phone and then enter unlock code.
4. root ----> http://www.psouza4.com/droid3/
5. safestrap and backup in case something goes wrong -----> http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
6. chinese radio ----> http://dropbox.com/u/25454276/radio.zip
7. flash radio ----> http://dl.dropbox.com/u/16206920/moto-fastboot-win32.zip
8. use something like root browser lite(free) to backup to sd card then edit your system/build.prop
I have called out, received a call and a text, I have checked my account information with the tmobile app on edge. I have been led to believe that its hardware that tmobile can only do edge since they use some non standard bands.
Credits:
flashing radio - http://forum.xda-developers.com/showthread.php?t=1360157
unlocking - http://community.vzw.com/t5/iPhone-4S/Verizon-iPhone-4S-SIM-UNLOCK-Tutorial/td-p/696707
safestrap - http://forum.xda-developers.com/showthread.php?t=1315982
Click to expand...
Click to collapse
So, I have a couple of lines on VZW, but they are all used by family members on my account, and I don't have a VZW SIM. The guy who sold me the phone said he already unlocked it, and I believe him, but is the SIM an issue and is there any way to know if the phone is still unlocked? Can an unlock be undone after wiping internal sd?
I'm asking because I think I can just not worry about that step, but I want to double check. I put it back to stock 2.3.4, now showing 5.6.890 xt862 instead of whatever the xt883 was. I did this to get rid of the previous owner's Google account. Edge, calling and text were working on T-Mo when I bought the D3 a few days ago. When I put my SIM in now, however, and change it to GSM/UMTS mode, there are no operators available when I tap on the list and of course it doesn't work yet. I understand this is due to putting it back on stock lol, but I'm gonna go ahead and try flashing the radio and seeing what happens.
It's already rooted using zergrush. Has safestrap and I can boot into it by rebooting/pressing menu, but my /system folder won't back up. That's the only sign that something is wrong other than the fact that no ROMs will flash in safe mode. I've already left comments on Hash's site, so I'm waiting over there too. Figured I'd pop in here again real quick
Thanks.
UPDATE (from the other forum):
My Droid 3 is working on T-Mobile for voice and text. This is exactly what I wanted. Got some great in-depth help on this one, especially from @tspx23. Thanks a ton! This will be my daily driver now until we switch to VZW, at which point this will turn into a back up, unless I fail to find something else worth a contract at that point lol.
I might write a guide later on if anyone wants it. The process is easier than it seems, as long as you have it in plain english lol.
Thanks to anyone who contributed to this!
Is it possible to mix this with a current rom instead of flashing a random Chinese one, like infuse with cm7 or liberty?
Tmo has horrible coverage and awful customer service. Cs is all nice to you but lies about everything constantly. They did nothing but screw me. That's the whole reason I'm on verizon now. At least now I have coverage and won't be lied to whether or not I have it, or be told to get wifi and then u can make calls since u don't have service.
Sent from my DROID3 using xda premium
I don't know of anyway besides a sim card to check if its unlocked and I am not sure a verizon one would ask for the sim unlock code even if it was locked but sim cards can be really cheap. If your phone was unlocked that will never be undone, if it was working on tmobile before you reverted to stock then it is unlocked, it would not have worked using tmobile otherwise.
are you using the latest version of safestrap, he released a bugfix version pretty recently? Could you be more descriptive of what you did while in safestrap?
It is not rom specific as far as I know, I am just using the stock one.
@Darksurf, I agree. I never had them but before I moved they didn't cover my old town. Verizon may be expensive but at least they tell you they will rape you at front and explain all charges.
Sent from my XT862 using XDA App
you can also try with at&t in full3g. As they have the same bands the d3 has
Enviado desde mi DROID3 usando Tapatalk
I will see tomorrow if this works with ICS
Radio and build prop edit
I'm staying on T-Mo till they go under. They are cheap and I have unlimited Edge, which is all I can get on this phone anyway lol. Only ten bucks a month for data, since I have an older package from before they tried to hike their rates.
My D3 is having some issues after I reboot, and sometimes just randomly, it will lose all signal and tell me that my preferred operator cannot be found or error connecting. I have been just rebooting and sometimes wiggling my SIM around to see if it fixes, and it does.
Only other thing that is a little weird is my phone thinks it's an xt883, even though I'm on the stock VZW ROM. I'm wondering if this is causing some issues that I'm not qualified to really diagnose lol. Usually after I reboot, I have some of my google apps' names in Chinese, but I'm not sure if that is from radio.img, new build.prop, or from changing my bloatware to .bak.
Also, be advised that if you remove bloat, conversations.apk breaks incoming text if it isn't seen by the system. I added .bak to the end of it and could send texts to my wife, but couldn't get any messages. I changed it back and texting works fine. I use Chomp SMS, but that didn't seem to matter.
Have fun
P/S: also, when choosing operators in settings, you have the option for T-Mobile 2G, AT&T 2G or 3G. Just to confirm ;-) probably because AT&T's 3G bands are the international standard, right?
when you flashed the stock rom back onto it did you delete the /system partition and do a factory reset on your device before you did it?
ericerk said:
Is it possible to mix this with a current rom instead of flashing a random Chinese one, like infuse with cm7 or liberty?
Click to expand...
Click to collapse
I'd love to see someone put these mods into a ROM, but I'm not sure if any of it is compatible with existing ROMs. I also accomplished this on stock. When I get around to flashing CM7 again (or trying to at least lol), I'll post about how it goes.
I'm thinking that when I wiped my phone, the unlock remained but the radio.img that was on the Chinese ROM was undone or lost. Flashing it was easy though, using cmd mentioned earlier in this thread. I just needed help figuring out how to set it up, since I'm a noob at command line lol.
After that, I downloaded adb and tried to use other commands I've found (which claimed to work, but didn't for me somehow) to change out the build.prop. This failure was likely my fault lol but I found it easier to just use Root Browser lite to back up my original build.prop then replace it with the modified one.
I figure that if my SIM doesn't work after flashing some other ROM, I'll just try the two main steps again and see if it works then. If anyone really wants to do this, it isn't too hard or not worth it in my mind. I also figure this phone will be relevant enough for a while longer, considering I am cool with Edge speeds, I certainly won't mind being stuck with VZW's 3G whenever we change over. I am in no hurry to get LTE battery suck or bulkiness either. I'll wait for a little more refining to be done on that end before I upgrade from this phone
I am interested in making the phone compatible on T-Mobile / ATT by flashing XT883 radio. I have one question: Will the "unlocking" turn the phone completely GSM phone so it can no longer work on CDMA network?
Thanks.
Probably until you flash the Verizon ROM back I would assume.
Sent from my XT862 using XDA App
No. XT883 is also CDMA compatible, so the ability to use CDMA should stay. You might need to do *228 though.
You unlock the phone via carrier unlock code, e.g. they give you a code via email or over the phone allowing your gsm functions to work with foreign sim cards (other than the one they come with). After getting the unlock code and flashing the xt883 radio.img (and changing/replacing your build.prop) you can still choose to use cdma. Flashing this radio (which I'm currently using on T-Mobile) doesn't make your phone incompatible with cdma and is reversible. You would simply have to flash the original radio.img and change back your build.prop, or just flash a regular cdma ROM. I plan to do this some time next year if/when T-Mobile goes under and my wife and I switch to Verizon. In the mean time, I only get edge on T-Mobile (using it on AT&T will get 3g), but I have cheap and unlimited data (legacy data plan $10) and a great phone with keyboard. I'm using the stock ROM, rooted, but will eventually try CM7 with the gsm tweak. I will likely have to reflash the xt883 radio.img and change my build.prop (I think).
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img
BenSWoodruff said:
You unlock the phone via carrier unlock code, e.g. they give you a code via email or over the phone allowing your gsm functions to work with foreign sim cards (other than the one they come with). After getting the unlock code and flashing the xt883 radio.img (and changing/replacing your build.prop) you can still choose to use cdma. Flashing this radio (which I'm currently using on T-Mobile) doesn't make your phone incompatible with cdma and is reversible. You would simply have to flash the original radio.img and change back your build.prop, or just flash a regular cdma ROM. I plan to do this some time next year if/when T-Mobile goes under and my wife and I switch to Verizon. In the mean time, I only get edge on T-Mobile (using it on AT&T will get 3g), but I have cheap and unlimited data (legacy data plan $10) and a great phone with keyboard. I'm using the stock ROM, rooted, but will eventually try CM7 with the gsm tweak. I will likely have to reflash the xt883 radio.img and change my build.prop (I think).
Droid 3 with stock xt862 ROM working on T-Mobile via xt883 radio.img
Click to expand...
Click to collapse
i wasn't able to flash the chineese rom, idk why it just wouldn't let me :/
Success!!!
This is a step by step that I used and it worked(Tmobile) for official release ICS:
01. Update to ICS
02. Power off phone and wipe data in Stock Recovery
03. Power on phone and edit the hex values with Radiocomm see: post 29/30 http://forum.xda-developers.com/showthread.php?t=1297714&page=3
04. Power off phone
05. Remove sim card
06. Power phone back on
07. Connect to PC
08. Root
09. Delete STK.apk (edit: you no longer have to delete, just rename to stk.apk.bak)
10. Delete STK.odex (edit: you no longer have to delete, just rename to stk.odex.bak)
11. Modify Build.prop values as is:
ro.telephony.default_network=7
ro.mot.phonemode.vzw4gphone=0
telephony.lteOnCdmaDevice=0
and add this to the bottom:
ro.telephony.ril.v3=signalstrength
12. Power off phone
13. Insert SIM
14. Power on!
15. Dial *#*#info#*#* switch to WCDMA Preferred
Should be good to go!
I'm sorry, but I need to ask a question that is probably frustratingly obvious,
When I go to use the RadioComm tool, the instructions says to put the phone in PC mode. I can't find PC mode on the phone, and whenever I try to use RadioComm, everything is red... the blood-red of failure...
How did you get around this? I've only had the phone for an afternoon (I'm enabling TMobile for a friend) so maybe I just don't know where the button for PC mode is!
Thanks for this. I was about to give up. I thought it was required to downgrade to the last GB rom (which is, apparently, impossible). I'm glad to give this a shot.
Sompom said:
I'm sorry, but I need to ask a question that is probably frustratingly obvious,
When I go to use the RadioComm tool, the instructions says to put the phone in PC mode. I can't find PC mode on the phone, and whenever I try to use RadioComm, everything is red... the blood-red of failure...
How did you get around this? I've only had the phone for an afternoon (I'm enabling TMobile for a friend) so maybe I just don't know where the button for PC mode is!
Thanks for this. I was about to give up. I thought it was required to downgrade to the last GB rom (which is, apparently, impossible). I'm glad to give this a shot.
Click to expand...
Click to collapse
Press the menu (at the left bottom corner), then system settings, choose developer options, then click usb debugging. Connect the usb cable to the pc. usb debugging connected displayed on the top left corner. Slide the usb icon down, tag the connected as media device, then click media device (MTP).
---------- Post added 27th October 2012 at 12:19 AM ---------- Previous post was 26th October 2012 at 11:57 PM ----------
DBoyFresh954 said:
Success!!!
This is a step by step that I used and it worked(Tmobile) for official release ICS:
01. Update to ICS
02. Power off phone and wipe data in Stock Recovery
03. Power on phone and edit the hex values with Radiocomm see: post 29/30 http://forum.xda-developers.com/showthread.php?t=1297714&page=3
04. Power off phone
05. Remove sim card
06. Power phone back on
07. Connect to PC
08. Root
09. Delete STK.apk
10. Delete STK.odex
11. Modify Build.prop values as is:
ro.telephony.default_network=7
ro.mot.phonemode.vzw4gphone=0
telephony.lteOnCdmaDevice=0
and add this to the bottom:
ro.telephony.ril.v3=signalstrength
12. Power off phone
13. Insert SIM
14. Power on!
15. Dial *#*#info#*#* switch to WCDMA Preferred
Should be good to go!
Click to expand...
Click to collapse
Confirm it works on ATT. Thanks
wnandroid said:
Press the menu (at the left bottom corner), then system settings, choose developer options, then click usb debugging. Connect the usb cable to the pc. usb debugging connected displayed on the top left corner. Slide the usb icon down, tag the connected as media device, then click media device (MTP).
Click to expand...
Click to collapse
Haha... It turned out to be just as stupid an error as I thought it would be... I didn't have the correct drivers installed -.- . I installed MotoCast, rebooted, tried again, and it worked! Yay.
Thank you!
Also, more notes for people who are as moto-clueless as me:
Stk.apk and Stk.odex are in /system/app
build.prop is in /system
It now accepts my Tmobile SIM, but it can't find any service. I've looked around, and it seems that lots of people with TMobile are having no luck with stock ICS, but ATT works fine. Any ideas? I changed ro.telephony.default_network=7 to =0 because that's how it appears in my TMobile MyTouch 4G Slide.
Sompom said:
Haha... It turned out to be just as stupid an error as I thought it would be... I didn't have the correct drivers installed -.- . I installed MotoCast, rebooted, tried again, and it worked! Yay.
Thank you!
Also, more notes for people who are as moto-clueless as me:
Stk.apk and Stk.odex are in /system/app
build.prop is in /system
It now accepts my Tmobile SIM, but it can't find any service. I've looked around, and it seems that lots of people with TMobile are having no luck with stock ICS, but ATT works fine. Any ideas? I changed ro.telephony.default_network=7 to =0 because that's how it appears in my TMobile MyTouch 4G Slide.
Click to expand...
Click to collapse
Try using my build.prop file. Heres the link to my post. http://forum.xda-developers.com/showthread.php?p=33261067
Sent from my DROID BIONIC using xda app-developers app
Do you have it working on T-Mobile? I gave it back to him this morning, but I sent him idiot-quality instructions to replace the build.prop. He says it doesn't work. He's on prepaid, so he as decided to just switch to Verizon. (This is a great idea where we live, T-Mobile has 2G and Verizon has 4G...) I hope this is an isolated instance rather than a generic problem with T-Mobile on the Bionic.
If I'm walking with him past an ATT store, I'll see if they'll let me try a SIM, so see if it was just me or if it's locked (or something?)... Unfortunately, there aren't many ATT stores for hours of where we live
Sompom said:
Do you have it working on T-Mobile? I gave it back to him this morning, but I sent him idiot-quality instructions to replace the build.prop. He says it doesn't work. He's on prepaid, so he as decided to just switch to Verizon. (This is a great idea where we live, T-Mobile has 2G and Verizon has 4G...) I hope this is an isolated instance rather than a generic problem with T-Mobile on the Bionic.
If I'm walking with him past an ATT store, I'll see if they'll let me try a SIM, so see if it was just me or if it's locked (or something?)... Unfortunately, there aren't many ATT stores for hours of where we live
Click to expand...
Click to collapse
Yes I have it working on T-Mobile here's a screenshot. The reason 3g/hspa+(4g) doesn't work for T-Mo everywhere with the Bionic is because they are in the process of switching bands to the standard 1900mhz band in the US. ATT users get full use of their band and 3g/hspa+(4g)
Sent from my DROID BIONIC using xda app-developers app
DBoyFresh954 said:
08. Root
09. Delete STK.apk
10. Delete STK.odex
11. Modify Build.prop values as is:
ro.telephony.default_network=7
ro.mot.phonemode.vzw4gphone=0
telephony.lteOnCdmaDevice=0
and add this to the bottom:
ro.telephony.ril.v3=signalstrength
Click to expand...
Click to collapse
that is the part i need explained a bit more.
also Don't T mobile and ATT run on the same Networkish...
I've got a ST(ATT) Sim card for my Droid bionic works fine, cept when i updated to ICS i can no longer send SMS/MMS. Been searching for about 10 days now. no fix.
scarocean said:
that is the part i need explained a bit more.
also Don't T mobile and ATT run on the same Networkish...
I've got a ST(ATT) Sim card for my Droid bionic works fine, cept when i updated to ICS i can no longer send SMS/MMS. Been searching for about 10 days now. no fix.
Click to expand...
Click to collapse
Yes they have the same type of network but they work on different bands. ATT=1900mhz T-Mo=1700mhz(switching to 1900mhz by end of year) The reason SMS/MMS isnt working is because you need to modify the build.prop file in your root folder. Ive attached the 1 click root program for the Bionic, use this to root your phone. After you root your phone you will need to download some type of root explorer so that you can access the root folder. You no longer have to delete the STK files just rename them with .bak extensions. They are located in /system/app. Then access /system and switch to R/W mode. You have to edit build.prop with the values in the guide.
T-Mobile AND AT&T
DBoyFresh954 said:
Yes they have the same type of network but they work on different bands. ATT=1900mhz T-Mo=1700mhz(switching to 1900mhz by end of year) The reason SMS/MMS isnt working is...
Click to expand...
Click to collapse
Works, but i'm only pulling 'Edge' Network. No 3g like before
Thank you VERY much. But i've got some information and a question...
I was too excited to try what you said to do so i didn't go back and read the instructions on post #1.
My phone had the SIM already still in it.
WCDMA was selected
Hex was still set to AT&T/Tmobile.
Then...
-- I Root it.
-- I edit files as given above.
NOTHING CHANGED! CANT SEND SMS STILL!!!
-- Powercycle.
NOTHING CHANGED! CANT SEND SMS STILL!!!
-- Reboot, wipe cache, wipe data/factory reset.
turn phone on: FULL BARS! (had to wait 1-2 minutes. and input SIM password)
Had Voice, but the calls kept failing
--Input APN for ST(att)
SMS/MMS work!!
Voice works
DATA works! ( Shows Edge2 )
My question is, Booted up on: GSM/CDMA Auto (PRL)
GSM = -80dBm
Network: home. ( i have never heard of this.)
IMEI: unknown
my phone number shows on *#*#info, and under phone information -unlikebefore it did not. Yet my IMEI isn't showing... It did before.
The network i had before i made these changes phone displayed ATT as network, not it is 'home'
network type before was HSPA/HSPA+/Edge, not it is just EDGE2.
So i'm not on ATT like before, i am on GSM?
When I send SMS/MMS to my other phone it takes 20 seconds to 5 minutes to show up on her phone.
When I am sent SMS/MMS it takes just as much time to show up on mine.
after about 20 minutes of running the phone SMS send normal speed.
I never did do the "then access /system and switch to R/W mode." Because I don't know what you mean.
when i switch to WCDMA preferred, it took about 3 minutes to load up a signal, The network type is still 'home' before all this it used to be 'ATT'
scarocean said:
Works, but i'm only pulling 'Edge' Network. No 3g like before
Thank you VERY much. But i've got some information and a question...
I was too excited to try what you said to do so i didn't go back and read the instructions on post #1.
My phone had the SIM already still in it.
WCDMA was selected
Hex was still set to AT&T/Tmobile.
Then...
-- I Root it.
-- I edit files as given above.
NOTHING CHANGED! CANT SEND SMS STILL!!!
-- Powercycle.
NOTHING CHANGED! CANT SEND SMS STILL!!!
-- Reboot, wipe cache, wipe data/factory reset.
turn phone on: FULL BARS! (had to wait 1-2 minutes. and input SIM password)
Had Voice, but the calls kept failing
--Input APN for ST(att)
SMS/MMS work!!
Voice works
DATA works! ( Shows Edge2 )
My question is, Booted up on: GSM/CDMA Auto (PRL)
GSM = -80dBm
Network: home. ( i have never heard of this.)
IMEI: unknown
my phone number shows on *#*#info, and under phone information -unlikebefore it did not. Yet my IMEI isn't showing... It did before.
The network i had before i made these changes phone displayed ATT as network, not it is 'home'
network type before was HSPA/HSPA+/Edge, not it is just EDGE2.
So i'm not on ATT like before, i am on GSM?
When I send SMS/MMS to my other phone it takes 20 seconds to 5 minutes to show up on her phone.
When I am sent SMS/MMS it takes just as much time to show up on mine.
after about 20 minutes of running the phone SMS send normal speed.
I never did do the "then access /system and switch to R/W mode." Because I don't know what you mean.
when i switch to WCDMA preferred, it took about 3 minutes to load up a signal, The network type is still 'home' before all this it used to be 'ATT'
Click to expand...
Click to collapse
Some people reported having to wait anywhere from 5 mins to over an hour before the phone fully switched to GSM mode...
Sent from my DROID BIONIC using xda app-developers app
Just follow everything step by step. I learned the hard way that if you deviate even just a little it wont work...
Sent from my DROID BIONIC using xda app-developers app
DBoyFresh954 said:
Yes I have it working on T-Mobile here's a screenshot. The reason 3g/hspa+(4g) doesn't work for T-Mo everywhere with the Bionic is because they are in the process of switching bands to the standard 1900mhz band in the US. ATT users get full use of their band and 3g/hspa+(4g)
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
T-Mobile is in the process of a complete "re-farm" mainly to make their network iphone compatiple. This means that everything on the network should be operating on the 1900mhz band by spring/summer 2013 which is when they are rumored to be getting the iphone. Regardless, if they still don't offer the iphone this refarm allows any unlocked iphone to be used on their network and get full HSPA+. You can bring an unlocked iphone into their store now and they'll put it on their network but if you don't live in an area where the re-farm is complete you'll only get EDGE access.
This update also applies to any other phone that operates on the 1900mhz band, not just the iCrap. T-Mo also just bought MetroPCS which, in itself, is not a huge deal as far as coverage goes BUT they also get all of Metro's spectrum (plus the spectrum they got from ATT and the failed merger) so they are actually lining themselves up to be the carrier with the most available spectrum as the FCC only has so much to auction off. I am seriously considering jumping ship for them even with my grandfathered unlimited data. They've got unlimited everything for cheaper but I have to see how service is.
I honestly was not aware the Bionic was HSPA+... probably just from not researching it as I have VZW anyway right now... My contract is up in March and even though I am grandfathered unlimited I might give them a shot. They actually charge less for "bring your own phone" and their deals are pretty good. Wife wants iphone and with the re-farm she could have one on T-Mo but her contract is not up till March 2014 so the ETF plus unlocked iphone... $1k... um no... Maybe when she sees how awesome ICS is vs GB she'll change her mind...
scarocean said:
Works, but i'm only pulling 'Edge' Network. No 3g like before
turn phone on: FULL BARS! (had to wait 1-2 minutes. and input SIM password)
Had Voice, but the calls kept failing
Click to expand...
Click to collapse
can I ask what you mean when you say you input sim password? Im trying to get it to work on t-mobile... Well I have 2 bionics, one is mine and I got t-mobile working fine using the radiocomm edit, removing the apk/ and odex file listed by DBoyFresh954 and doing the build prop edit listed by him in the same first post. but the 2nd bionic is my friends and I cant get t-mobile working on it. The only thing thats not the same on the two bionics is my friends is HW B 43/11 while mine is HW A 34/11. If anyone might have a fix or can explane the sim unlock that scarocean was talking about please do post or pm me would be most thankful
HELP!!
Okay, so I got my T-Mobile SIM card in today. Followed everything perfectly and still nothing. No service or anything. I double checked my area for coverage and confirmed that T-Mobile does have service here. I'm on stock 246. I rooted, applied the gsm unlock zip, re-named the stk files, edited the build.prop settings, and switched to WCDMA Preferred. I have the HW B version if that matters. I've been looking everywhere and can't seem to find an answer. Could somebody help please?!
Edit: My phone is now showing AT&T as the network. Also noticed that my Signal is reading -81 dBm and 16 asu. Isn't that a good signal?
trulunacy said:
Okay, so I got my T-Mobile SIM card in today. Followed everything perfectly and still nothing. No service or anything. I double checked my area for coverage and confirmed that T-Mobile does have service here. I'm on stock 246. I rooted, applied the gsm unlock zip, re-named the stk files, edited the build.prop settings, and switched to WCDMA Preferred. I have the HW B version if that matters. I've been looking everywhere and can't seem to find an answer. Could somebody help please?!
Edit: My phone is now showing AT&T as the network. Also noticed that my Signal is reading -81 dBm and 16 asu. Isn't that a good signal?
Click to expand...
Click to collapse
I followed post #1 exactly and my Bionic works on T-Mobile.
What do you mean where you said "applied the gsm unlock zip" --- Either I missed this part or do not understand what you are referring to.
Running rooted Bionic on Synergy ROM on T-Mobile.
I do have a question though....
How to prevent phone from going back to LTE when rebooting. Not the worst thing but have to modify the radio each time phone is rebooted???
Also the ones who got it to work as well, are you getting 3G??? I feel as though I am not....
Thanks again to the person who started Post #1 --- Saved me $$ from buying a new phone from T-Mobile.
huskersone said:
I followed post #1 exactly and my Bionic works on T-Mobile.
What do you mean where you said "applied the gsm unlock zip" --- Either I missed this part or do not understand what you are referring to.
Running rooted Bionic on Synergy ROM on T-Mobile.
I do have a question though....
How to prevent phone from going back to LTE when rebooting. Not the worst thing but have to modify the radio each time phone is rebooted???
Also the ones who got it to work as well, are you getting 3G??? I feel as though I am not....
Thanks again to the person who started Post #1 --- Saved me $$ from buying a new phone from T-Mobile.
Click to expand...
Click to collapse
I flashed a zip that does what you did in Radiocomm. I finally got fed up with the problems and went to AT&T and got a SIM with prepaid. Works great! I just could never get the T-Mobile SIM card to work. Didn't go to waste though. Unlocked my wife's Torch and used it for that.
I have no idea how to make the settings stick for reboots. Odd, that your settings don't stay on WCDMA Preferred. Mine stays after reboot.
I think the Bionic can only get 2G until T-Mobile has finished their refarm. I think there's only a couple that have been set. Don't quote me on that though. Haven't really looked into it a whole lot.
Sent from my AT&T DROID BIONIC using xda app-developers app
just a bit more about files and build prop
I have the droid bionic and I was attempting to get my at&t service on the bionic. I have made it as far as the root step. Where do I find the files to delete? I have a folder /system on my PC but I can't find /system on the bionic. Where is the /system/app folder? Do I need to use device manger find it? A few more details would be much appreciated. a list of files and programs needed would be a nice addition to walkthrough. Just a thought. Plz help thanks
semipro bionic said:
I have the droid bionic and I was attempting to get my at&t service on the bionic. I have made it as far as the root step. Where do I find the files to delete? I have a folder /system on my PC but I can't find /system on the bionic. Where is the /system/app folder? Do I need to use device manger find it? A few more details would be much appreciated. a list of files and programs needed would be a nice addition to walkthrough. Just a thought. Plz help thanks
Click to expand...
Click to collapse
Download ES File Explorer. Hit the menu button once you open it and go to settings. Scroll down to root settings and select all options. Go back to the main menu and hit the Up button at the very top. Scroll down and click on "System." Once in you'll see the "App" folder immediately. Click on that and scroll down to the STK apk's. Once your done renaming go back once and scroll down till you find the build.prop. Click it and use the ES note editor to edit the settings.
As far as adding the signal strength to the build.prop goes just scroll all the way down and add it there.
Sent from my AT&T DROID BIONIC using xda app-developers app
When you do this edit, can you switch back to Verizon's CDMA/LTE by switching sim cards or do you need to redo both the apks and Hex edit?
So I've had this DROID Bionic stoed away for over a year now since the company I worked for closed down and never asked for their phone back.
I was using my LG Revo (rooted) for the time being until I started to have some issues with it. So I booted up this phone, put in the VZ sim card and just realized that I've been missing out on so much!
I've been doing some research here and elsewhere and It's a bit overwhelming.
I'm currently on 5.5.886.XT875 and an OTA notification just came up saying "Update (5.5.893.en.US) has been downloaded and is ready to install."
Any help would be great on where to go from here.
Should I do the OTA update or should I just FXZ to ICS or JB? Is there an order I have to do this (Eg. 5.5.886 to 5.5.893 to 5.7.893 to 5.9.902 etc.) ?
It seems like the easiest thing would be to use SamuriHL's House of Bionic. But again, do I have to incrimentally update or can I just jump to a more recent version?
Also, the 5.5.893 OTA update that's on the phone seems to be downloaded from the last time I was in the US. I'm currently in Puerto Rico and the CDMA here only gave me 1x coverage on the LG and no data on the Bionic. So not sure if OTA updates would work here.
I would like to try to use GSM and/or use a SIM from a local carrier. I'm guessing root is needed for that.
Well, thanks in advance.
-Dan
mofongoloco said:
I was using my LG Revo (rooted) for the time being until I started to have some issues with it.
Click to expand...
Click to collapse
My wife has the Revolution and I have the Bionic. I can't stand her phone and hating trying to fix it. I feel your pain!
mofongoloco said:
Should I do the OTA update or should I just FXZ to ICS or JB? Is there an order I have to do this (Eg. 5.5.886 to 5.5.893 to 5.7.893 to 5.9.902 etc.) ?
Click to expand...
Click to collapse
When you use the FXZ you can always jump ahead to the image you have. You just may not always be able to get back. Use the FXZ to upgrade directly to ICS or JellyBean (See next answer first)
mofongoloco said:
I would like to try to use GSM and/or use a SIM from a local carrier. I'm guessing root is needed for that.
Click to expand...
Click to collapse
Yes, you need to be rooted, and the root method for ICS and JellyBean are very different. Functionally, there is no difference in flashing to ICS, rooting, using Voodoo root keeper, and then going to Jelly Bean instead of FXZ to JellyBean and then using the Easy Root image. I founf rooting JellyBean slightly easier for me, but I am familiar with using virtual machines so your experience may vary.
Once you are rooted and on Jellybean, use these directions to enable GSM support: http://forum.xda-developers.com/showthread.php?p=42437715
Following those directions I have had no problem with using my Bionic on T-Mobile. I have read that some hardware Verision other than Version A have issues with GSM, but I don't know what those are. Be sure to thank the original poster of that GSM Guide if it was as helpful to you as it was to me!
Bionic FXZ locations
For convenience, the Bionic FXZ thread:
http://forum.xda-developers.com/showthread.php?t=2240725
And the direct link:
http://sbf.droid-developers.org/cdma_targa/list.php
So, I went ahead and did the OTA update to 5.5.893
This basically didn't do much, so I tried to use SamuriHL HoB to update to ICS. This did not help either, kept getting black screen w/ phone vibrating. I was hoping to use that method to save my data, oh well.
Then, I saw Andy's response (you rock, btw) and I went ahead with the FXZ and was able to get to ICS. This worked great! Best part is, I now have a working Bionic with a Data connection! It is still only 1x speed, but so far the connection here in PR has been more reliable than the Lg revolution.
Right now, Network type and strength shows 1x = -89dBm, data connection is good.
Sometimes, once or twice a day for a couple minutes, it will show 1x = -96dBm and 3G = -32dBm. When that happens there is no data connection on the phone. I have a theory that the local carrier blocks verizon users from using CDMA 3G, because once I'm back on 1x everything is fine.
I'm wondering if maybe I could get Verizon to activate global data services. If I do the RadioComm edit, does anyone know if that would allow me to use the GSM portion of the phone on the Verizon global network? Since technically I'm out of the Verizon area, I would use the local carrier that Verizon leases services through. Is that thought process correct?
The local carrier uses GSM for their 3G network, and they do offer LTE for their own devices.
Again, thanks so much for your help with this.
mofongoloco said:
I'm wondering if maybe I could get Verizon to activate global data services. If I do the RadioComm edit, does anyone know if that would allow me to use the GSM portion of the phone on the Verizon global network? Since technically I'm out of the Verizon area, I would use the local carrier that Verizon leases services through. Is that thought process correct?
Click to expand...
Click to collapse
I am glad I was of help!
I am not sure about activating global service in Puerto Rico: That is something you will need to contact Verizon about.
If you change the RadioComm and buildprop setting to allow GSM, it will not work with Verizon until you change them back. Also, you will need to to a data wipe from recovery to avoid a problem with the phone rebooting over and over again so you can't just switch this from one to the other by replacing SIM cards (I was personally bummed by this).
Not all LTE is created equally: your Bionic is not likely to be compatible with the other phone companies LTE because they use different channels per company.
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Kraizk said:
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Click to expand...
Click to collapse
Yes, twice
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
I'm going to try this now thanks
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Kdenery said:
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Click to expand...
Click to collapse
Try flashing a CM10 ROM. I've always seen the option there. The kitkat ROMs I have used do not have the option except for the Nocs GE.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
-TheEdge- said:
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i'd kinda like to argue a point here as this just happened to me. i am certainly not new to flashing, starting back with the mogul and having almost every sprint smart phone since then unlocked (windows) or rooted (webos and android).
Using TWRP and previously running ecliptic 4.3 i wiped caches, system and data then installed the 4.4.2 from team d3rp and voila... no service no meid no nothing.... yes i have the latest radio on my phone.
i guess my point in this is that there's a number 3 that you didn't mention.
3. sh!t happens and it's not n00b related.
for anyone else that has this issue... flashing CM 10.1 worked for me. i didn't even have to set up anything, it just picked up signal. so i rebooted, wiped and nandroided back to 4.3 and all is well.
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Robert542 said:
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't... it was SuperOneK. i'm certainly not blaming the rom though. especially not when others are flashing it fine. the ONLY thing i can think of possibly happening is a bad download. I was in a rush and didn't check the md5.
I had a similar problem when flashing miui. Nothing worked. Even went back to a sense backup and nothing worked.
Commit failed as well.
Here's what I did to make it work again.
Flashed cm10. Change the network settings for CDMA. (Boom it SAID I had service..but didn't).
Rebooted a few times (probably not necessary).
Flashed a sense 4.3 ROM that was close to stock.
Update msl and all that. Commit.
For me..changed LTE/CDMA to just CDMA (no 4g in wv).
Boom it worked again. Hope this helps!
Sent from my HTCONE using xda app-developers app
Hello All,
Something changed in my phone and not really sure as to what has happened. All of a sudden my phone loses data connectivity and thinks that it is roaming. If I enable airplane mode and disable it, then the phone works for about 10-15 minutes and then loses connectivity again. Running the 12B baseband (been using it for months with no issue) and haven't changed the ROM in quite some time. This started happening on yesterday.
Any suggestions?
The 4G radio seems to have crapped out completely. Getting a replacement sent on tomorrow
Optimus124 said:
The 4G radio seems to have crapped out completely. Getting a replacement sent on tomorrow
Click to expand...
Click to collapse
Damnit. I am having the EXACT same problem, running CM11.
How did you come to that conclusion? I am thinking I'm going to have to restore to stock if I'm going to get Verizon to do anything about it.
EtherBoo said:
Damnit. I am having the EXACT same problem, running CM11.
How did you come to that conclusion? I am thinking I'm going to have to restore to stock if I'm going to get Verizon to do anything about it.
Click to expand...
Click to collapse
I reverted all the way back to 11A stock unrooted. The phone was in 4G for about 5 minutes (if that) and then remained in 3G mode.
Optimus124 said:
I reverted all the way back to 11A stock unrooted. The phone was in 4G for about 5 minutes (if that) and then remained in 3G mode.
Click to expand...
Click to collapse
I'm at the same point. Going to do an Asurion claim since I didn't buy my phone from VZW (Swappa).
I had this problem before when I tried other roms like cm rom and omni rom. I tried to do *228 to fix problem, but made it made it worse. I restored it back to stock and took it to the Verizon store. They put a new sim card in it for free and it fixed the problem. Now i am running stock with simple kernel.
Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great.
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Alright, I'd be lying if this makes any sense to me, but the issue appears to be related strictly to the SIM card.
I had them swap the SIM, it fixed the issue, then it came back. I'm on a new phone now, and it appears to be working. The old SIM did not work on either phone, but the new one does. What makes no sense is the old SIM would work fine in my Galaxy Nexus, but would not work in the G2. Now the new SIM is working perfectly in the new G2 (haven't tried the old one).
I'm baffled.
I've never seen anything make so little sense. The guy at the store told me I would need to replace the SIM again in a few days. Whatever, if it happens again, I'll do just that.
I did the same with my gs3. What ROM are you running?
Sent from my VS980 4G using Tapatalk
The original phone was running CM 11 Nightlies.
I'm currently on stock - not sure if I'm going to stay with CM because the official thread indicates official development is DitW for the G2 .
That's actually strange... I'd expect roaming issues with an Intl ROM but not cm.
Sent from my Nexus 7 using Tapatalk