Related
So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
Is there a method/software that can backup carrier info? Buddy of mine wants to upgrade to 4.4.2 but he is flashed to Selectel Wireless and that would wipe out his carrier info and have to dish out another $50 to get reflashed again. Was hoping there was a way to backup that info... install 4.4.2 and then reload the info.
No?
define carrier info. Do you mean his IMEI and baseband version?
Mtsprite said:
define carrier info. Do you mean his IMEI and baseband version?
Click to expand...
Click to collapse
Hate to sound stupid, but whatever info you might lose doing an upgrade or even a Factory Reset. He did a reset a couple days after having his phone flashed from Verizon to Selectel and his phone wasn't working right. Was making calls but they were showing up as another number and ended up having to pay the guy that originally flashed it... another $50 to reflash and fix it. Thought there be some method to save this info. I can only imagine there must be a way, as there must be people into messing with roms who have to go through this process each time.
Free can of beer for the correct answer.
Maybe an NVbackup in terminal might do the trick. I don't know. If you figure it out let me know. I'm thinking about flashing another rom and seeing what happens. When I originally had a guy flash selectel I had to be on a TW rom. After this I restored a nandroid of nameless and still had service although in both cases my new number never showed up in about phone / status. I was told to use 8sms to change my phone number in there and then it would show up. On my first flash before I was told about the 8sms trick, I went home and was unable to do anything, no service. I went back flashed TW in his office. Did the 8 sms trick, then restored the same namless nandroid. All is well. Knock on wood. Last night I wanted to wipe data cache and instead of doing it in CWM or actually phil's touch, I did it in the phone settings and it wiped my friggin internal sd partition. What a freaking bummer. Luckily there was nothing super important on there I keep most important stuff on my external SD. I might try tonight to flash a TW just to see if my signal gets a bit better but I'm going to try to figure out how to backup my settings first. The second time there, the owner did the reflash and told me about the 8sms. He was clueless about flashing different roms. There's got to be a way to backup all the needed information in an AOSP rom, or an app, I just gotta figure out how. If you figure this out let me know
Thanks and good luck
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
Click to expand...
Click to collapse
Try restoring via fastboot for a clean slate. I understand from your post that you're flashing via custom recovery.
gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day
Click to expand...
Click to collapse
CM12.1 may flash the new radio that OxygenOS flashes, from which there is not necessarily an immediate return.
Possible you have that new radio. See here:
https://forums.oneplus.net/threads/oxygenos-back-to-cm11s.296219/#post-10851703
gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
Click to expand...
Click to collapse
Can you still see your baseband and IMEI? Go into Settings/About Phone for the baseband version and Settings/About Phone/Status for the IMEI.
Transmitted via Bacon
Baseband is unknown and there's no mention of IMEI anymore... does that mean I lost my IMEI/it got corrupted? Am I screwed? I planned on trying the fastboot restore but only as one of the last resorts. If CM12.1 use the same radio then my 12.1 should work but that doesn't either. Nothing works. I've tried CM11s, CM12, CM12S, CM12.1... sigh...
I think I had a modem/efs backup in one of my nandroids and I tried restoring that too with no luck
Restored one of my CM12 nandroids and now I have a baseband of "DI.3.0.c6-00230-M8974AAAAANAZM-1". For some reason or another, that doesn't look right to me even though I've never really paid attention to what the baseband ever listed. Still can't seem to locate my IMEI #. I did the #*#*4636*#*# and the cell radio is on and turning it off and one still only shows emergency calls only. Obviously I'm not going to try to call 911 just to test if the radio gets service. However, I can see my IMEI # so I guess that's good. I must have some bad firmware update. Guess I'll copy out all my stuff to my otg usb and fastboot restore and see if that helps unless there's something else I can try.... please let me know...
gqukyo said:
Baseband is unknown and there's no mention of IMEI anymore... does that mean I lost my IMEI/it got corrupted? Am I screwed? I planned on trying the fastboot restore but only as one of the last resorts. If CM12.1 use the same radio then my 12.1 should work but that doesn't either. Nothing works. I've tried CM11s, CM12, CM12S, CM12.1... sigh...
I think I had a modem/efs backup in one of my nandroids and I tried restoring that too with no luck
Restored one of my CM12 nandroids and now I have a baseband of "DI.3.0.c6-00230-M8974AAAAANAZM-1". For some reason or another, that doesn't look right to me even though I've never really paid attention to what the baseband ever listed. Still can't seem to locate my IMEI #. I did the #*#*4636*#*# and the cell radio is on and turning it off and one still only shows emergency calls only. Obviously I'm not going to try to call 911 just to test if the radio gets service. It really does look like it's my IMEI # that got jacked... what can I do now?.... :T
Click to expand...
Click to collapse
You've got a corrupt EFS partition. There's a thread detailing how to fix your situation in our general section.
Transmitted via Bacon
tried to flash the persist.img from http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 but that just prevents my phone from booting up properly. I only see the OnePlus logo with not Powered by Android on the bottom...
I take it back, it does show the powered by android but only for a split second then it stays on the OnePlus logo and doesn't do anything... :T
Restored back most recent cm12.1 nandroid and now I do see IMEI number in the about settings but still only emergency calls only... Guess its a good start, no sure what else I can do at this point.
Now you see your imei but you dont have the signal,it means your modem file does not work.So the first thing to do is backing up the efs then you can flash 44s modem and proximity patch.Probably it will work.It worked for me.
Ok there may be hope then. Just flashed the 44s modem then nandroided back to my CM11s then flashed modem again just in case lol. Don't recall seeing a proximity fix but it's ok as long as my cellular connectivity works, I'll deal w/ other issues later. Otherwise all I have is an expensive media player... lol it's booting up now so we'll see... *fingers crossed*
Nope didnt work...going to try a fresh CM12 install...
Trying to flash roms and in the wizards it always states I don't have a sim installed so I'm not sure it's my modem that's messed up or if it's something else related to hardware related to the sim. The sim itself works in my other phone... tried a different sim and it's still emergency calls only. don't know what to do now. doing all this and it's still not working so I doubt even the fastboot restore would work... might just have to rma... which would probably take 4eva...
Pls flash your nandroid backup which gave you the imei first,after gain your imei ,back up it,then you can flash what rom you like,if you dont have your imei,just flash your imei backup.The most important thing is to back up your efs.
Sent from my A0001 using XDA Free mobile app
Think my efs is fine as I can see the IMEI now but no matter what nandroid and fresh install I try, I can't get the cellular connectivity to work. I backed up all partitions just in case.
gqukyo said:
Think my efs is fine as I can see the IMEI now but no matter what nandroid and fresh install I try, I can't get the cellular connectivity to work. I backed up all partitions just in case.
Click to expand...
Click to collapse
Being able to see your IMEI doesn't necessarily mean your EFS is ok.
Transmitted via Bacon
Well tried the persist.img but that didn't work so what else can I do?
The one thing that would definitely fix your issues would be if you had an EFS backup. I don't know why people don't do this. Without that I have no idea what you can do.
Transmitted via Bacon
Never had that issue before and I've own android phones from the HTC Hero. Lesson learned though, thankfully it's still under warranty and it's not that expensive a phone...
gqukyo said:
Never had that issue before and I've own android phones from the HTC Hero. Lesson learned though, thankfully it's still under warranty and it's not that expensive a phone...
Click to expand...
Click to collapse
Not all Android phones employ an EFS partition. I'd never heard of it before this phone but a bit of research on my part revealed the importance of an EFS backup.
Transmitted via Bacon
That would make sense then. As I was reading about EFS, seems like it was mostly Samsung phones. I guess I can try a fastboot restore... nothing else to lose. lol
Doh! apparently there is something to lose when fastboot restoring... phone stopped booting back up correctly after a few fastboot restores and now it won't even turn back on... lovely... at least I had a expensive android media player before, now I have a brick... lol
Edited - Sorry
I have the same issue with all verisons of CM12. I get No service. Although the XNPH44S radio was the best. Meaning I could atleast see 3-4 bars for about 1 second and then off for a couple of minutes and then back on again for 1 second and so on. I believe it is a problem with not having a proper radio. One plus should release a better working radio in my opinion. I am on PTEL Mobile network (uses T-Mobile). So until we get a good working version of the radio I think some people like us are stuck on cm11.
>> 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.