Related
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.
Ok it started with my first triumph. got it 2 weeks ago lasted all about 3 days and it went dead locked up wouldnt even come on. But whle it was working the stock rom wouldnt connect to wifi no matter what i tried, reset, battery removal, airplane toggle, cleared everything the whole shot. then i installed froycream sandwich and cm7 reloaded and they both worked great the wifi connected no problem. until the phone died.
Enter phone number 2. i had to track down because there werent any anywhere for 100 miles in any direction besides the one i found in a outta the way radio shack. got home the wifi connected right away no problems on stock i thought to myself hmm musta been something wrong woth the first phone from the word go, anyway installed cwm 5.0.2.6, then installed cm7, got all my stuff set up and wifi was working fine. went to bed woke up and went to connect to wifi and nuthing again when you turn wifi on it scanns says connecting and then says disconnected every few mins or so it will try and connect but it just continues to loop. i flashed back to a backup of stock and it connects again. tried froyocream sandwich v1.3 and cm7 reloaded by whysor 3 different builds.
ok so ive been flashing back and forth and and clearing this and that and trying different things , doing things in different order, installing different builds, trying to get it to work.
in between custom roms i decided to restore back to stock and see if it would connect stock again or not. at first it didnt, then i rebooted and tried again and it finally connected...woohoo. i was actually afraid that if i changed anything i would lose functionabilty again. but i flashed froyocream sandwich 1.3 again and cfrossed my fingers and sure enuf it connected when i got all setup. i have successfully used it on and off wifi for the last half hour anyway so ill keep posting my results ive seen a few people have kinda similar probs maybe we can figure it out , im looking through logcat files to see if i can see anything funny but................
I had this problem once before, I had to boot into clockwork go into advanced & wipe dalvik cache, then flash the OC kernel again & all was well. That's if your running CM7 reloaded.
I've run into this issue also
I was having issues on my rooted verizon galaxy s3 running beans version 15. I would get a circle on data when tethering. I went back to root66 learned my IMEI and ERI were set to zero and now they are at 5 and the correct things...I have data I've had it 4g LTE that is and can tether just fine. I'm using my phone currently to ask this question. I cannot dial or send texts...on beans it just says dialing with no tone on root66 it would say no network available. My # shows my service is there...when I click LTE/CDMA in network it says searching and I hit ok. I don't know if that means it needs to search first or what...I really don't know what to do I have searched all day and done everything I know to do and now I'm just lost. I also did *228 and it said my sim wasn't registered then I rebooted and did it and it worked....so no clue what is going on.
Under phone status my phone said Service State: Out of Service when on root66 but now it says In Service. Still don't understand this.
Mobile network state: connected in root66 it was trying to connect randomly.
Phone #: Correctly displayed
Prl and ERI Version: 15211 and 5
Device State: normal.
Everything seems good : (
StriferZer0 said:
I was having issues on my rooted verizon galaxy s3 running beans version 15. I would get a circle on data when tethering. I went back to root66 learned my IMEI and ERI were set to zero and now they are at 5 and the correct things...I have data I've had it 4g LTE that is and can tether just fine. I'm using my phone currently to ask this question. I cannot dial or send texts...on beans it just says dialing with no tone on root66 it would say no network available. My # shows my service is there...when I click LTE/CDMA in network it says searching and I hit ok. I don't know if that means it needs to search first or what...I really don't know what to do I have searched all day and done everything I know to do and now I'm just lost. I also did *228 and it said my sim wasn't registered then I rebooted and did it and it worked....so no clue what is going on.
Under phone status my phone said Service State: Out of Service when on root66 but now it says In Service. Still don't understand this.
Mobile network state: connected in root66 it was trying to connect randomly.
Phone #: Correctly displayed
Prl and ERI Version: 15211 and 5
Device State: normal.
Everything seems good : (
Click to expand...
Click to collapse
I'm having the same problem. I haven't yet gone back to Root66, because that is going to be a major pain (really REALLY don't like using ODIN and haven't found a flashable zip to use from CWM), and my phone has had trouble staying connected to a computer ever since I took it out in a snowstorm a few months back, so I'm nervous that doing stuff via ODIN is going to end poorly. This was after I flashed to Carbonrom 1.7, which is Android 4.2.2. Initially I got stuck on the activation screen, with no phone number, nothing, but after I switched my CDMA subscription mode from NV to RUIM/SIM, I got the phone number and PRL version back. Phone number now appears correct, and PRL version is 15223. IMEI still reads 0, though. I had an IMEI backup from back when I first flashed from ICS to JB, but restoring it doesn't seem to have any effect. I'm going to keep looking for a flashable Root66 zip, and if not I'll see if I can get something to work via ODIN (or see if I can maybe get the AOSP modem solution thing to work though the script I found didn't run) and report back. I don't do a whole lot of phone calls, and data is working fine, so it's not a hugely pressing issue, but I do want to get this solved ASAP. If anyone's got any thoughts or input, I know we'd both appreciate help. In the meantime, I'll press on and we'll see what happens.
adiv.paradise said:
I'm having the same problem. I haven't yet gone back to Root66, because that is going to be a major pain (really REALLY don't like using ODIN and haven't found a flashable zip to use from CWM), and my phone has had trouble staying connected to a computer ever since I took it out in a snowstorm a few months back, so I'm nervous that doing stuff via ODIN is going to end poorly. This was after I flashed to Carbonrom 1.7, which is Android 4.2.2. Initially I got stuck on the activation screen, with no phone number, nothing, but after I switched my CDMA subscription mode from NV to RUIM/SIM, I got the phone number and PRL version back. Phone number now appears correct, and PRL version is 15223. IMEI still reads 0, though. I had an IMEI backup from back when I first flashed from ICS to JB, but restoring it doesn't seem to have any affect. I'm going to keep looking for a flashable Root66 zip, and if not I'll see if I can get something to work via ODIN (or see if I can maybe get the AOSP modem solution thing to work, though the script I found didn't run) and report back. I don't do a whole lot of phone calls, and data is working fine, so it's not a hugely pressing issue, but I do want to get this solved ASAP. If anyone's got any thoughts or input, I know we'd both appreciate help. In the meantime, I'll press on and we'll see what happens.
Click to expand...
Click to collapse
I had an issue installing carbon rom too a while back but just went back to stock and then redid everything from there...this is my first time encountering such a huge issue that I can't solve on my own. Everything seems FINE now..IMEI everything was repaired and fixed. Odin takes around 12-15 minutes if you wanted to try that...How did you change your subscription mode? Maybe there are some things I haven't tried yet....if so I'd like to know how and where.
StriferZer0 said:
I had an issue installing carbon rom too a while back but just went back to stock and then redid everything from there...this is my first time encountering such a huge issue that I can't solve on my own. Everything seems FINE now..IMEI everything was repaired and fixed. Odin takes around 12-15 minutes if you wanted to try that...How did you change your subscription mode? Maybe there are some things I haven't tried yet....if so I'd like to know how and where.
Click to expand...
Click to collapse
System Settings>More...>Mobile Networks>CDMA Subscription.
I had issues with Carbon 1.6.1, and flashed back to 1.5, which was great except that occasionally normal-pressing the home button would start registering as a long-press until I rebooted. Decided to try Carbon 1.7, then this happened. As I understand it, though, whether or not your IMEI gets borked is a bit of a matter of chance, not necessarily ineptitude on the part of a ROM's developer team. That's why you're encouraged to backup your IMEI before any serious system modification. Dunno why my backup isn't working, though... that part is what's most annoying.
adiv.paradise said:
System Settings>More...>Mobile Networks>CDMA Subscription.
I had issues with Carbon 1.6.1, and flashed back to 1.5, which was great except that occasionally normal-pressing the home button would start registering as a long-press until I rebooted. Decided to try Carbon 1.7, then this happened. As I understand it, though, whether or not your IMEI gets borked is a bit of a matter of chance, not necessarily ineptitude on the part of a ROM's developer team. That's why you're encouraged to backup your IMEI before any serious system modification. Dunno why my backup isn't working, though... that part is what's most annoying.
Click to expand...
Click to collapse
Man I don't know. I only use my phone when it comes to calls and keeping up with anything work and personal. I don't know where to begin..wish I could reset everything lol
StriferZer0 said:
Man I don't know. I only use my phone when it comes to calls and keeping up with anything work and personal. I don't know where to begin..wish I could reset everything lol
Click to expand...
Click to collapse
That you can do. There are multiple guides out there for completely resetting back to stock, for situations like needing to return a phone to Verizon and wanting to erase any trace of your fooling around with OS components. For me, I seem to be completely unable to connect the phone to computer via USB, so ODIN is completely out. Thinking I might bring it to Verizon and see what they can do. I've currently got it on JellyWiz RLS13, which is based on the stock TW JB OTA, so hopefully that's close enough that it won't throw any flags for them and they can do some magic or something and reset the IMEI.
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
TenderloinShadow said:
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
Click to expand...
Click to collapse
Go into About Phone -> status check your IMEI and PRL and such are they still there?
buhohitr said:
Go into About Phone -> status check your IMEI and PRL and such are they still there?
Click to expand...
Click to collapse
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
TenderloinShadow said:
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
Click to expand...
Click to collapse
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
The problem i had i couldn't recieved calls. Everything worked fine..
I ended up getting new sim card then the employee dialed *73 then my fone was back in action
buhohitr said:
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
Click to expand...
Click to collapse
yeah I figured that would have to be the answer from the beginning. Have to Odin back to stock first, won't be able to do that for probably another 3-4 hours because of a work meeting that's about to start, so I figured I'd ask around.
If anyone has any other ideas, I'm open to them. Otherwise I'll reprovision tonight and report back.
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
beepea206 said:
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
Click to expand...
Click to collapse
+1
Flash back to stock, or a stock based rom with stock messaging. Try to force the message through. My messages stopped sending on aosp messaging and was persistent through rom flashes. I eventually forced it through using touchwiz messaging.
Sent from my SCH-I535 using Tapatalk 2
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.
UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO
artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon