I'm posting this on the four android-related forums that I participate in, in hopes that someone has seen this before and knows what to do.
Here's what I had:
- Droid 2 Global, unlocked, rooted, with Fission ROM, using Rogers Wireless, a GSM network in Canada
- it had been working just fine for 5 months
Here's what I did:
- Used RSDLite and the SBF loader to flash the stock 2.4.330 firmware as seen here: http://droid.koumakan.jp/wiki/SBF
- ended up with a bootloop, as the directions said I would. cleared data and cashe, no problem, phone booted.
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- Used stock recovery mode to upgrade to 4.5.607 (gingerbread) firmware as seen here: http://droid.koumakan.jp/wiki/4.5.607_Firmware
- I used the file linked to from here: http://www.droid-life.com/2011/08/22/gingerbread-build-for-the-droid2-global-leaks/
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- rooted phone using the adb method that is out there. rebooted and confirmed root access. installed a couple apps that need root. tested phone functionality, all was well. used APN backup/restore and APN Manager to make backup files of my APNs
- As described here, http://droid.koumakan.jp/wiki/CyanogenMod Installed Droid 2 Recovery Bootstrap and ROM Manager in order to flash CWM. rebooted into CWM, factory reset, installed the latest release (10/06), and rebooted
- started up phone, switched to GSM mode, phone app crashed immediately (as is to be expected, based on known bugs), rebooted for it to take effect
Now here's the problem:
- phone can make calls and receive texts with no problem, but cannot get data. wifi also works.
- went into wireless settings, mobile networks, access point names, nothing shows up. Clicked "add APN". entered the APN info that had worked for me before at the past two junctions. hit menu button, then save. takes me back to the APN screen, but no APN shows up.
- repeated this cycle a few times following reboots, etc. Eventually the phone gets to the point where the "add APN" button will not even come up when the menu key is hit.
- during the above, was also checking the "network operators" setting. The phone does locate all of the networks that are "in the air" but no matter which one I choose it will tell me "your sim card does not allow a connection to this network"
- used root explorer to check /data/data/com.android.providers.telephony/databases/telephony.db. There is a list of about 1500 APNs. There are multiple entries for Rogers including all of the ones I tried to enter that appeared not to save.
- used APN backup/restore and APN manager to attempt deleting existing APNs, restoring the ones that were known to work, etc. Nothing works. These programs do work, and when I check the telephony.db file I can see what they have done to the file, but they are unfortnately unable to make any APN "stick" at the APN screen, and apparently that is the only way that it will work.
more info:
- I've noticed that the list of rogers entries seems to get larger and larger as I go through this process multiple times. I may be wrong, but it seems that this telephony.db file might not actually get changed or updated when you flash a new kernel/firmware/mod/rom to the phone.
- I'm sure that the lack of a list of APNs and the "sim card does not allow connection" message are related. For whatever reason there seems to be a bug in CM7 where the telephony.db file has problems "talking" to the APN screen in settings. But it must not affect most people.
- yes, I have tried a new SIM card.
- yes, I have tried clearing cache, data, dalvik, and fixing permissions.
- Anyone else on Rogers Running CM7 on a D2G? If so, I'd love to talk to you. Maybe I could convince you to send me a working CWM backup. I imagine that if you're a conscientious rommer, you have a backup made folling a fresh install of CM7.
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Edit: I have a XT860 which is in for repairs - once I get it back and I have a reliable daily phone I plan to experiment with the new GB based CM4D2G. Hopefully this week...
leobg said:
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Click to expand...
Click to collapse
Yes, everything works really well with stock rom. I was quite impressed, as it was my first GB experience. Unfortunately, as with cars, I am all about the "options", and I can't seem to let go of a feature once I have experienced it. I love CM7 and I really want to make it work for my D2G.
I posted this same thing at the rootzwiki thread, and one of the head developers said "You my friend may finally have identified where the gsm data issues are coming from. it isnt just you, it's 98% of the gsm users that arent having data". Another user got me to change a couple of permissions. I thought he was onto something but it didn't work, either. Nonetheless, I think I brought enough attention to this issue and also gave them something to work with through all my trial and error. I am optimistic.
But, for now, I think I have to take CM7. I want my data! I am really tempted to just give stock GB a shot. But Blur scares me. Most people don't seem to like it, though I admit I don't fully understand what Blur is! I see there is MIUI and apex, angel Hexen and VenusX. I might have to try them first.
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
greek_lover_69 said:
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
Click to expand...
Click to collapse
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
seventieslord said:
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
Click to expand...
Click to collapse
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
I wish it was that easy, but it's not. I have tried a number of solutions similar to that but no dice. I appreciate the attempt though.
Sent from my DROID2 GLOBAL using XDA App
For the record I have that problem on the D2g flashed with the latest builds of cyanogen rom, (with the same SIMs perfectly working on D3 and D2g with the stock rom), and the airplane mode trick doesn't works too.
So far I haven't found a solution
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Thanks, i guessed that if a proper fix may be hard to find, a workaround was easy enough, I'll try it later with the gingerbread froyo.
dobosininja said:
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Click to expand...
Click to collapse
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
seventieslord said:
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
Click to expand...
Click to collapse
I gave this a try, and no dice. Too bad.
Thanks anyways.
The Solutor said:
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
Click to expand...
Click to collapse
I now own a D3. CM9 is doing the exact same thing to me!
I tried what you said and I am still not getting data. phone and texts work though, just like before.
I followed directions to wipe everything as suggested in this post:
http://forum.xda-developers.com/showpost.php?p=20485148&postcount=146
Was using Alfa 13 just fine, but on Alfa 17 I can not get cellular data to work. Confirmed my WAP settings are correct for my carrier.
My baseband it says its a i9020xxkf1 and everything else on the phone works. I can access the market, wifi works, account sync if i have wifi on. I have doubled checked every possible setting. But it will not bring up a data connection over the cellular radio. It even takes calls over the radio. Just no data connectivity.
Any suggestions or reasons why this is occurring? I can easily swap back to an older nandroid image of alfa 13, but I would really like to get on a new version etc.
(Also, I would have made this post in the right dev section, but i lack 10 posts to gain access to it.)
Have you tried removing and replacing your SIM card ?
Also, check if your data counter has a limit set on
You could also manually configure your APN settings with your carrier's settings
Unfortunatly I have done all of those things. It doesn't even attempt to connect to data. I sit at 4 or 5 bars of signal and it never even connects to EDGE/3g at all. Yet if I flip back over to my older image it works flawlessly.
i have also problem with version 17, but i can't post it to developer forum (newbie here)
problem is that i can't hook on any network, no calls no messegas, i'm using croatian tele2/t-mobile....sometimes it connects but still nothing, no calss etc.
also problem (not so much a problem but a solution) when i installed ROM it went to bootloop, all you have to do is remove battery and power up again, and voila, it works, same problem happened when i installed gapps (same solution worked, everything installed from CWM latest version)
there were also posts regarding cwm not stiking after installing cynogen, i had no problem with it, i have latest cwm 5.0.2.3 (think so), sticks like hell tried couple of roms, still sticking
cheers
I have the same problem here... ICS 4.0.3 and my 3G stopped to work.
also tried new 18 version, still no luck, i'm staying on cynogenmod 7 (GB), only ICS version that worked was MUI but i don't like it very much....
http://forum.xda-developers.com/showthread.php?t=1398691
It has been messed around with a fair bit. Various methods have worked for different people. YMMV. I myself had such an issue with the stock FW (of all FWs...).
I've been pulling my hair out for a couple of weeks with this. SMS inbound + MMS inbound/outbound works. SMS outbound does not work.
This started when I upgraded to a CM11 nightly. I've also tried a pretty decent AOSP custom ROM (see http://forum.xda-developers.com/nexus-s/development/rom-aosp-kitkat-4-4-2-mod-nexus-s-build-t2410844) with the same result. No custom kernels have been tried, which leaves me to think that it must be related to the CM11 crespo kernel, as the AOSP custom ROM mentioned is based off of the CM11 kernel.
Using latest version CWM, I completely wiped (system, data, sdcard, cache, dalvik, you name it) and installed these ROMs. I've checked, double-checked and triple-checked the APN settings. I've gone into my mobile provider's store (Koodo, in Canada) and gotten them to test the SIM card in another phone - everything worked fine, so it's nothing on their end. They verified the APNs as well.
There have been other reports of this being an issue - see http://forum.xda-developers.com/showthread.php?t=2561308 for instance. They say that changing some setting in Voice+ (something that accompanies Google Voice?) is a good workaround... however, being in Canada prevents me from doing anything with Google Voice. I found the APK and manually installed it (can't install from Google Play as I'm in Canada), but couldn't sign into it, so couldn't see any settings. So, I'm left with NO outbound SMS until there's a fix or someone tells me what I can hack via terminal/shell. If there is anything.
Someone has also created a JIRA against CM11-M2-crespo (https://jira.cyanogenmod.org/browse/CYAN-3157) to which I added some details, but it's been closed for lack of a log file. Not sure how to create that, but will likely look into it soon.
Does anyone have any input? This is driving me nuts. Thanks.
EDIT: Added solution below.
Apparently this is a SIM card issue, related to the SMSC number. I have no idea how it got out of wack, but playing with the SMSC settings helped things to 'just work'. How to get into the SMSC settings screen:
- Dial *#*#4636#*#*
- Go into Phone Information
At the bottom of the resulting screen, you can try Refreshing. That seems to have done it for others. In other cases, they had to manually Update with a new number.
KitKang
Have you tried KitKang EurosKank's rom.
Because I have no problems with the SMS on it.
KnoMeNot said:
Have you tried KitKang EurosKank's rom.
Click to expand...
Click to collapse
No, I haven't - but I see it's using a CM11 kernel as well, so likely will exhibit the same problems... but I'll give it a shot tonight, along with any other suggestions people might have.
Thanks!
KnoMeNot said:
Have you tried KitKang EurosKank's rom.
Click to expand...
Click to collapse
Ok, I just tried EurosKank's cm-11-20140117.0925-crespo - exact same failed result. I'm so confused. How can it work for some people, but not others?
Link to download it here (credit to AICP CM devs on their google plus page): https://plus.google.com/101577397694816898663/posts/GS4FcdKVomX
From the comments of the post, this is a write up of what is working:
I did dirty flash and all still works. I'd love to see a change log but I know that's asking a lot.
Boot time was fairly quick after flash approx 60 secs.
File explorer still can't see the sd card but as optix told me before, you can use rootbrowser app or just go to settings storage and you can see and manipulate sd.(I believe it's due to a superuser issue not related to ROM.)
BT worked fine for me last night on previous build except when not using it auto disconnected but as soon as media was played again it auto connected and plays normal. Will test BT further.
Also I know that cm theme manager is based on cm's C-apps and it's code base hasn't been updated to work in SDK 24 ie n-7.0 but I'm sure that will come soon.
There is a delay when connecting calls. The delay seems less when placing calls then when receiving. As long as the caller is patient it does connect. This might not be a Rom issue as I use Greenify and I've read some where that this issue had been encountered on other Roms.
As long as you can deal with the stock N theme, 20-30 ssecond call cconnect delay, and not having Xposed untill it's updated to work on SDK 24 then this is totaly daily driveable.
PS thank you to the Devs, please tell me how I can be of service helping or testing and I'm all yours.
Click to expand...
Click to collapse
Who wants to try?
not i, said the fly. still happy with MOAR 7.0
following nightlys
I have the sprint g900p and am following the nightlys build for cm 14, so far I've ran into a few issues, rotate doesn't always work, it is dependent on app. YouTube works but the stock cm chrome will not. Also I cannot send any SMS unless I force the radio to move from LTE to 3g.
And of course the SD card issue.
Just so you know, started with stock ROM, updated everything, clean Odin flash with twrp.
If you need any info let me know otherwise I'll post as I find bugs.
I have been using a Droid Mini for many years now, and am still quite happy with it. One of my few complaints, is that the radio does not play nicely with Canada's Bell/Telus LTE network.
I've used the versions in both 4.2.2 (doesn't hand off to HSPA properly after a call or MMS, repeated service drop-outs) and 4.4.4 (hand-off is fine, but LTE connection is started/lost many times a day regardless of signal strength). While the latter one is an improvement, there are other weird bugs that seem to come with 4.4.4 ("this SIM is from an unknown source" errors which randomly kill your connection, prompting to connect to WiFi when opening apps even if all available relevant settings have been disabled).
I know the radio firmware from the Moto X is compatible, but I have a few questions before I start toying with this as it is my daily driver:
Is it OK to flash the radio partition from a newer major version? (Lollipop radio to Kitkat)
Is MSM8960PRO_BP_23255.140.93.00R the best option available? What is included with the available CyanogenMod releases?
Is the radio partition the only one that must be flashed to support this?
What's the easiest way to backup the partition before I try to update it?
Does anyone know if there is a working repository for the XT1030's stock images?