Related
Hi guys I have a 2 month old Nexus S and for no apparent reason all of a sudden today I noticed I am not getting any network service (australia vodafone).
I've tried removing and trying other sim cards which are known to work. My sim card works in other phones so it's nothing wrong with the sim card. Wifi still works perfectly. I've tried going in and out of airplane mode to restart the antenna and I've tried to turn it off and on again. I've also done a factory reset and erased all data through the android menu as well as the bootloader separately to no avail.
However what I also noticed is even though I did factory resets it doesn't seem to completely reset it as the android version still shows 2.3.3 which I applied using a manual update. The phone had 2.3.1 when I bought it. How do I do a full reset to send it back to 2.3.1?
The phone is still under warranty however if it is a software issue I would rather fix it myself then send it away.
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Additionnal bit of info.
Someone on Cyanogen forums asked me to try to flash the radio through fastboot instead of clockwork recovery..
If I do that, it is able to send the file but it seems unable to write. It gets stuck here:
fastboot flash radio XXKB1-GRI40-radio-nexuss-unsigned.zip
sending 'radio' (4126 KB)... OKAY
writing 'radio'...
(I've tried flashing both KB1 and KB3 through flashboot, same results)
Hello everyone,
I have the same issue. I turned my phone on this morning and it said "no service, emergency call only".
I used wifi to apply the OTA 2.3.4 with hope that it'd fix the issue as I read from my google searches. But it does not.
I tried flashing back to KB3 to run with 2.3.4 as well but that doesn't help.
If the phone can still do emergency call, it means the hardware is OK, right?
any suggestion? Thank you very much.
Opteron.
Did anyone ever find a solution?
you could try dialing *#*#4636#*#*, going to phone information, and looking at your preferred network type (might be the wrong one). you could also go to phone information, push menu, go to select radio band, and try a few different ones. hopefully that solves it, or you might have to flash a different radio/rom
edit: make sure you write down the original preferred network type before you change it. it could screw with what kind of service you get if you set it to the wrong one
Hi,
I am having the similar problem with my Nexus S
Tried the *#*#4636#*#* settings to EURO and GSM only but with no success.
Did anyone ever find a solution?
hi, im just wondering what type of root did you use for the AU nexus s. im not sure what root method to use for the SCLCD :S
thanks
fooraide said:
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Click to expand...
Click to collapse
Hello! did you find any solution or you repaired your nexus s? Im having the same problem. when i try to back to stock from Cyanogen..Any suggestion? Regards
found a solution
hi guys ! I recently had the same trouble that no signals were being received after updating to 4.1.2 but then i dialed *#*#4636#*#* and turned off the radio and turned it on again and now its all fine
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
funkymonk101 said:
Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed
Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)
Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.
1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself
You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.
Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.
Click to expand...
Click to collapse
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Same problem
Having this exact problem. My problem is I do not have access to a windows computer and thus cannot use Odin. I have already performed a Factory reset so I may try the way that involves removing the sim card. I dont know how more people haven't posted on this yet...
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
as far as I can tell this does not work. You must have a sim card to get past the second screen in boot up. There is no other option besides to turn of your phone.
Thank you for the help! My phone as been out of commission for the past 2 days and the OP directions fixed it. However the second post did nothing to help out. Worth a shot though
Does anyone know if this can be done from a Mac?? I am a little desperate here. Ive spent most of Christmas day messing with this.
You'll have to find a Windows computer, or install a windows virtual machine using vmware fusion or parallels desktop.
will this work for us cellular??
rossida said:
easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)
This should now let the ur phone have access to the network and get rid of the roaming issue.
Click to expand...
Click to collapse
This has happened to me twice. The second time I used this method and it worked for me. It was only successful when I switched to the executioner 2.5 rom which was on my sd card. Thanks!
Nvm fixed it
*wrong thread*
killerkiyoshi said:
Nvm fixed it
Click to expand...
Click to collapse
How???
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
pupsinmytub said:
Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas
Click to expand...
Click to collapse
Yall all need to chill out. Just fix your mobile network settings, toggle airplane mode, and you'll be fine.
You have no reason to fear flashing any roms.... With common sense.
Sent from my SCH-I535 using xda app-developers app
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
None of this has worked for me. I have followed the post directions and still have roaming. I am not seeing this option some of you are talking about though " wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)"... is this option supposed to be in the stock ics rom?
Update: the line had been suspended for some very odd reason
Got it working on VZW SG3 for now
This worked for me:
Reboot to recovery and fix permissions (not sure if this step helped just following some other posts) --> change mobile networks to the sim option ---> and most importantly enable National Data Roaming (this is the step that kicked over my signal)
After doing this it has started to let me call out and receive sms. My only concern is what consequences will i have with the national data roaming enabled and secondly when I am in other networks if I will get better signal; i live in a small town and get 1x so I have no idea what will happen till i get into the city but this seems to be a good fix for now. Hope this helps.
Tried all posted solutions and then some, still can't get CM 10.1 working on d2vzw
All,
I have a stock-rooted SCH-I535, and am also unable to get CM 10.1 working without losing the voice connection. It appears that my problem is corrupted NVRAM. Although my IMEI remains correct after flashing 10.1, my phone number and other info (ERI) gets corrupted. After a day of anxious attempts to fix the phone, the only fix I've found is flashing root66 (after which the phone still doesn't boot to the OS), factory reset (allows phone to boot), and then dialing factory-reset code *2767*3855#. For some reason the dialer-initiated reset seems to fix the NVRAM issue while the recovery-initiated reset does not.
After figuring out how to fix the problem, I've tried a handful of ways to get CM 10.1 working properly.
Original try: flash 10.1 over rooted-VRBLK1 using TWRP 2.3.1. After fixing by flashing root66, recovery factory-reset, and dialer factory-reset, I was nervous and made a couple backups.
used the su ; reboot nvbackup commands in this RootzWiki post.
Made a QPST backup with the instructions in this XDA post.
2nd try: factory reset, wipe data/system partitions, re-flash 10.1 with TWRP. This attempt had the same roaming/corrupted phone info result, but this time I was confident because I was armed with the two backup methods above.
I tried using the Samsung MEID RepairV3.5 in this XDA thread, but it wouldn't connect to the phone running CM10.1. I've gotten that tool to connect to the root66 image, so I know I'm following the procedure correctly. However, the developer specifically states that the tool is intended for stock images, so I wasn't surprised that it failed to work on CM 10.1.
with su privilages, I used terminal command "reboot nvrestore". I expected this to work, but it resulted in an unbootable OS. I had to flash root66 and repeat the fix process described at top.
Third try: flashed 10.1 again with TWRP 2.3.1. I tried using the QPST recovery I had created earlier. I got the phone into diagnostic mode (RMNET+DM+MODEM) using terminal commands for AOSP ROMs. For some reason I couldn't get the scripts to work, even with full permissions in the "root" directory -- the script resulted in the phone disconnecting from my computer in MTP mode, but it didn't connect in diagnostic mode. Terminal commands did the trick though -- I may be making some n00b mistake with the scripts. After typing the commands in manually and connecting to QPST, when I told QPST to "restore" the backup, it gave me an error message with incompatible phone, and if I checked the "allow phone/file ESN mismatch" box, the restore failed because the phone didn't respond to the QPST commands. I'm sure the phone was in diagnostic mode because it came up under Device Manager "ports" as depicted in the QPST instructions, so it seems like the corrupted NVRAM was causing problems with making a QPST connection.
Fourth try: TWRP update to 2.3.3.0. Same results as 2.3.1.0.
Fifth try: switch to clockworkmod touch recovery 6.0.2.3. Same result as both TWRP versions.
So, I'm pretty frustrated. I have the phone back up and running rooted-stock VRBLK3. I'd really like to get JB4.2 though, so if anyone can ID the problem, please post! I hope it's a simple fix from a n00b mistake, but after all the fruitless effort above, I expect that it's a more significant issue.
One last thought: I always rebooted into recovery to install the 10.1 image, and I never tried using the ClockworkMod ROM Manager or TWRP-compatible GooManager apps. My wife is tired of me spending the holiday weekend hunkered over my phone, so if anyone wants to try that route please let me know if it works.
The only other idea I have is to install 10.1, then try flashing the VRBLK3 baseband by itself. Again, I don't have the time to pursue this idea (or expertise to know if it's a good one), so any good insight would be appreciated. One last thought: personally, I'm not willing to wander around in voice or data "roaming" even if everything else is working fine. I rely on this phone for daily use, and am not comfortable without the radios working normally.
Happy new year!
thank you. can confrim this method to work for a verity of roms. ha.
vabeachfc3s said:
Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This worked, just reboot the phone after you make this change and you'll have your activated phone back with voice/data. :good:
No Service
I flashed CM10.1-m a few days ago (using this method to root and unlock bootloader http://forum.xda-developers.com/show....php?t=2046439 then flashing CM10.1-m through Odin), and my phone worked flawlessly for 2 days. It started to lag a bit during swipe-style text entry (no tracing line or predictive words appeared), so I rebooted hoping to fix the problem.
After reboot I lost all verizon service. The phone said "No Signal" or "Emergency Calls Only." The phone would not identify a mobile network, and no option for CDMA/LTE was available under mobile network settings, although verizon APN's were still identified. I think I lost my IMEI/EFS but don't know enough to be sure.
First I flashed stock VRALG1 android 4.0.4 without success. However after I flashed stock VRBLK3 android 4.1.1 my verizon service was restored.
I would really like to figure out how to keep CM10.1... touchwhiz is awful. Can someone confirm this problem can be fixed through one of the following methods? http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2&nocache=1
Also don't want to trip my flash counter... any idea at what point this would happen?
Been trying to figure out this problem but can't. Was running Carbonrom 4.3. Was updating to TWRP 2.6.3.0 using terminal emulator (using instructions from the twrp site). rebooted phone after update. That's when the problem arise -- could not make any phone calls.
What I've done:
1 - restored my prior backups (synergy, beanstock, cleanrom) -- did not resolve problem. Has data access, but cannot make or receive phone calls.
2 - re-installed roms from scratch (after full wipes, including format of internal storage/data) -- same result.
3 - checked my IMEI - it's valid, and matches the back of phone.
4 - checked my mobile network setting: cdma/lte/evdo
5 - again, Data works fine: I can surf the web, access Google Playstore & install programs, receive text messages.
...but I cannot make any outgoing calls. And when I make a call to my cell phone, it does straight to voicemail
Any suggestions? Did the SIM card go bad?
finally fixed the problem. Had to Odin back to stock >> took OTA updates >> factory reset, and bingo.
...weird that phone boinked but data worked?!?
epagib said:
finally fixed the problem. Had to Odin back to stock >> took OTA updates >> factory reset, and bingo.
...weird that phone boinked but data worked?!?
Click to expand...
Click to collapse
I've had this happen several times in different circumstances. The fix I've found is to manually set the radio band using the "phone info" app. Under "Phone Information" I click on the menu which brings up an option to select the radio band. For some reason I need to do this while traveling to Canada too, I need to select the PCS band, then go back to Cellular once I reenter the US and want to get back on Verizon. I tried Odin'ing back to stock, and it didn't work for me, but I might have had the wrong stock at the time (I was out of town).
epagib said:
finally fixed the problem. Had to Odin back to stock >> took OTA updates >> factory reset, and bingo.
...weird that phone boinked but data worked?!?
Click to expand...
Click to collapse
Did you have your imei backed up using the synergy method? I had the same problem and with the same exact ROM, Carbon 4.3. When I switched Roms I couldn't make or receive calls but I could use my data and even send SMS. Luckily I had a backup of my imei in the form of a zip file that I flashed in recovery. It fixed it.
Sent from my SCH-I535 using Tapatalk 4
So a week ago I did a fresh install of Lollipop via the factory image for LRX21O, rooted it, and installed Franco's kernel #68. Everything worked great until yesterday as it seems I've lost all mobile data connectivity. I can still make phone calls and text messages, but data is a no go when mobile. So far here's what I tried:
Made sure the APN was Correct
Cycled Flight Mode
Cycled Power
Pulled & Re-Installed SIM Card
Cleared the Cache
Factory Reset
Re-flashed Stock Kernel
Flashed Android 4.4.4 Radio
Re-Flashed Lollipop Factory Image
Restored Previous known working install of Android 4.4.4 via TWRP
Made sure there were no billing issues with my carrier.
Anyone have any ideas? I'm especially concerned and convinced its not specifically a Lollipop problem (though that doesn't mean it didn't cause it) since it did not restore functionality when I flashed back KitKat. I've never used 3rd Party ROMs on this phone, only rooted stock. My carrier is SimpleMobile.
Ron Overdrive said:
So a week ago I did a fresh install of Lollipop via the factory image for LRX21O, rooted it, and installed Franco's kernel #68. Everything worked great until yesterday as it seems I've lost all mobile data connectivity. I can still make phone calls and text messages, but data is a no go when mobile. So far here's what I tried:
Made sure the APN was Correct
Cycled Flight Mode
Cycled Power
Pulled & Re-Installed SIM Card
Cleared the Cache
Factory Reset
Re-flashed Stock Kernel
Flashed Android 4.4.4 Radio
Re-Flashed Lollipop Factory Image
Restored Previous known working install of Android 4.4.4 via TWRP
Made sure there were no billing issues with my carrier.
Anyone have any ideas? I'm especially concerned and convinced its not specifically a Lollipop problem (though that doesn't mean it didn't cause it) since it did not restore functionality when I flashed back KitKat. I've never used 3rd Party ROMs on this phone, only rooted stock. My carrier is SimpleMobile.
Click to expand...
Click to collapse
Maybe you need to contact your carrier?
You're not alone, I'm having the same problem since going to 5.0. I use Red Pocket on AT&T's network. Can't get mobile data working at all. Contacted Red Pocket and they reset my data on their end but still a no-go. Wi-Fi fine, calls and SMS fine. MMS, like data, doesn't work.
I guess I'll pick up another MVNO card to make sure it isn't still Red Pocket's issue. I have another SIM, but unfortunately my T-Mobile card, which is usually in a Lumia 1520, doesn't work for data on the Nexus 5 because that is on their blocked list of phones (stupid carriers).
>> Partial solution was found; still looking for the root of the problem. <<
I recently decided to take the plunge and root my OnePlus One and install sultanXDA's CM 13 ROM on it. It was all going well until I booted up into the ROM and discovered that I couldn't get any mobile data. Everything else was working, calling, texting, wifi, but mobile data seemed to refuse to work. Since I initially flashed sultan's ROM with TWRP 3.0.0, I suspected it was a problem with my modem. Though unable to install TWRP 2.8.6.0 to re-flash everything, I did still flash a new modem via ADB. This didn't help.
I have tried many things to fix this. I rebooted/reflashed. I flashed different ROMs. I tried flashing on TWRP 2.8.6.1, though I believe that one has the same modem problem as the versions after it. As mentioned above I tried flashing a modem over ADB. I took out and re inserted my SIM card. In the end, I tried this guide here to restore my phone to it's original state. The guide flashes the stock versions of everything via ADB. Though it did return me to unrooted COS 12.1, it was not able to resolve my data problem.
After the total reset, all I can think that could be causing it is a hardware problem or that it is caused by something not reset in the 100% restore above.
If any of y'all can help my solve this, or at least offer insight, I would be very grateful.
Preemptive Edit I Guess: This thread was just suggested to me while writing this. I'm going to try the solution here and report back. It's OnePlus' reset to stock method. I'm not expecting much after my first 100% reset attempt, but we'll see.
EDIT: Ok, so the solution above fixed my problem... (edit again: turned out to only be a partial solution. See below.)
I would feel really dumb right now if it weren't for the fact that I slaved over this problem for a good ~8 hours before writing this post. Anyways, I'm not sure how to delete this post or mark it as solved. Sorry for the trouble y'all.
Never delete this post !!
I have the same problem, and I spent much more time to find a solution.
I will try this and will update.
Is it a clean stock rom?
Edit:
Didn't help for me ..
Still the same problem, No mobile internet connection.
Thx anyway.
Yeah, actually I was too hasty is identifying this as the solution. For me, the stock reset brought me back to CM 11 which didn't have a problem with mobile data. But if I try to flash a later ROM or update via OTA, the problem returns. I'm still trying to figure out what is causing it. The only information I can find points to it being a modem problem or APN problem, but I'm sure I have sufficiently checked both of those already.
Either way, I'll keep looking. If I find something I'll return here with it. Good luck
arkasa said:
Yeah, actually I was too hasty is identifying this as the solution. For me, the stock reset brought me back to CM 11 which didn't have a problem with mobile data. But if I try to flash a later ROM or update via OTA, the problem returns. I'm still trying to figure out what is causing it. The only information I can find points to it being a modem problem or APN problem, but I'm sure I have sufficiently checked both of those already.
Either way, I'll keep looking. If I find something I'll return here with it. Good luck
Click to expand...
Click to collapse
Try this:
1) Download the latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
2) Go here and follow step #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
3) Then follow step #2 to install a new recovery (you need to make sure to use TWRP 3.0.0 or the unofficial TWRP if you want to flash modems/firmwares correctly)
4) Download the latest ROM of your choice and install via your recovery
ryanmat said:
Try this:
1) Download the latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
2) Go here and follow step #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
3) Then follow step #2 to install a new recovery (you need to make sure to use TWRP 3.0.0 or the unofficial TWRP if you want to flash modems/firmwares correctly)
4) Download the latest ROM of your choice and install via your recovery
Click to expand...
Click to collapse
I gave this a try, but booting up after step 3 I still had the same problem. If I understand this method correctly, I think it is essentially the same as the other full restore methods I tried.
I think I may have found the problem though. I was looking at OnePlus' guide to installing OxygenOS. In it they said, "do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support." At this point I have repeatedly reset/restored my modem/radio so I don't think that is the problem, but I haven't seen anything about IMEI before. The IMEI is apparently stored in the EFS partition which as far as I can tell, is not touched by any of the restore methods I have tried. I took a look at my IMEI (about phone -> status) and it turns out my IMEI SV is 00. It's supposed to be a 16 digit number. I found a guide to fixing it, but I think I will just contact OnePlus customer support first.
I'll be back later with my results.
arkasa said:
I gave this a try, but booting up after step 3 I still had the same problem. If I understand this method correctly, I think it is essentially the same as the other full restore methods I tried.
I think I may have found the problem though. I was looking at OnePlus' guide to installing OxygenOS. In it they said, "do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support." At this point I have repeatedly reset/restored my modem/radio so I don't think that is the problem, but I haven't seen anything about IMEI before. The IMEI is apparently stored in the EFS partition which as far as I can tell, is not touched by any of the restore methods I have tried. I took a look at my IMEI (about phone -> status) and it turns out my IMEI SV is 00. It's supposed to be a 16 digit number. I found a guide to fixing it, but I think I will just contact OnePlus customer support first.
I'll be back later with my results.
Click to expand...
Click to collapse
Are you flashing each of the extracted .img files from fastboot, exactly like the guide shows, or are you doing something else?
ryanmat said:
Are you flashing each of the extracted .img files from fastboot, exactly like the guide shows, or are you doing something else?
Click to expand...
Click to collapse
Yep, I ran each command listed in the guide and my phone was definitely in fastboot. Each command had a collections of "OKAY"s and ended with a "finished", which I assume means it executed as expected.
I have tried 2 different sim cards in my OPO (of two different companies, one of them as mine), and mobile data worked perfectly. Is it possible that my phone is ok and the problem happened in the sim card?
AND... my IMEI SV is 00 too. please update here if it has a connection.
Thank you !
omersa99 said:
I have tried 2 different sim cards in my OPO (of two different companies, one of them as mine), and mobile data worked perfectly. Is it possible that my phone is ok and the problem happened in the sim card?
AND... my IMEI SV is 00 too. please update here if it has a connection.
Thank you !
Click to expand...
Click to collapse
I'm not entirely sure what you're saying. Did it not work with the first SIM card, but it worked with the second?
Mobile data problem was occured (to me), after I rooted my OPO and tried to flash a new rom.
I still can't understand how it convinced my sim card, but the fact is that I tried two (to be sure) other sim cards which are not mine, and mobile data worked well.
When I returned my original sim card, problem started again.
So I am almost sure that sim card has a connection, but can't understand why. And why it happend precisely now, cause it worked well over two years.
omersa99 said:
Mobile data problem was occured (to me), after I rooted my OPO and tried to flash a new rom.
I still can't understand how it convinced my sim card, but the fact is that I tried two (to be sure) other sim cards which are not mine, and mobile data worked well.
When I returned my original sim card, problem started again.
So I am almost sure that sim card has a connection, but can't understand why. And why it happend precisely now, cause it worked well over two years.
Click to expand...
Click to collapse
sorry to intrude...but looks like mine problem too...but no connection with provider at all...and it worked 1 month normal (stock opo)..
could u flash the modem to resolve this problem?
jpvr
http://forum.xda-developers.com/one...e-plus-one-t3030545/post65841063#post65841063
Why don't you flash twrp flashable modem?
If your network is present but no data , mostly data service problem. Are you pay your mobile bills ?
Are you activate data services ?
Try this
https://www.androidfilehost.com/?w=files&flid=28032
drmuruga said:
Why don't you flash twrp flashable modem?
If your network is present but no data , mostly data service problem. Are you pay your mobile bills ?
Are you activate data services ?
Try this
https://forums.oneplus.net/threads/cos-12-master-fix-thread.307446/
Click to expand...
Click to collapse
...yes i paid my bills ..
- my network connection to provider is dead...it worked perfecly for 1 month out of the box (see original posting for detailed action i took) this thread is about lack of data connection...but also MODEM related???
- tried the brand new simcard in my old Samsung sII... works perfetly, network connection with provider, data connection and calling..so no simcard problem
Long shot. Change any APN settings from IPv6 to IPv4. That was my problem when I had text/voice but no data.
I made a post on this and then called att gophone, due to seeing other sims working on this thread, and he helped me to fix. Posting my fix here in case others with isue find this post instead of mine.
Turned off wifi.
Turned off cellular data.
Went to APN and changed the apn (ATT Go Phone) from pta to nxtgenphone.
Turned on cellular data.
Finally had H+ above he signal bar, but had an X inside the bar.
Don't know if he did anything on his end, but the X went away after a couple of minutes.
Data was working, albeit kinda slow.
Turned off phone for three minutes per ATT rep.
Rebooted.
Data still slow, but it is at least working. Thinking I need to flash different modem. Battery usage has been higher the last day or two since I flashed c7 anyways.