Just in case this post gets moved, I want to identify my device as the Verizon Samsung Galaxy S3 (i535).
To give a little background on my issue, I have an issue with the device. When I first got it back in July, first thing I did was root the device. Naturally, since it was a new device, I was working with experimental methods... a couple weeks ago I thought to download CyanogenMod 10.1 (nightly build) to flash it with 4.2 and rid myself of the persistent OTA update that as we all know could not effectively install because of the measures I took to root. So, I boot into recovery and flash my custom rom. BAM! As it turns out, I did not have an unlocked bootloader and my phone was now teetering on the verge of being a $600 paperweight. I got that dumb yellow triangle saying unofficial firmware detected or some nonsense like that... Anyway, I look around the internet and decided that I was going to revert back to a stock rom using Odin, and then proceed to unlock my bootloader and root the device (I followed method 3 here) I used some touch recovery console that I have never heard of before (backups incompatible with ClockworkMod recovery) and something must have failed because my back up would not flash. I took the hit on losing most everything and reflashed successfully the custom rom mentioned earlier.
After about a week, I noticed the device began to drop data. 4G would just stop at random parts of the day, and I would have to disable and enable the data to get it to reconnect. At this point I was still able to make and receive phone calls and texts. After about 3 days of this, I concluded it was more than likely a bug in the custom rom, and that I could not live with it... so I redid the a fore mentioned tutorial and left the phone as a stock/unlocked/rooted device. The data issue continued, but with a twist. I was now unable to make or receive phone calls or texts. No matter what I did, I could not do anything and the 4G would only stay connected for a matter 5 minutes or so. When I logged into my vzw account, it identified my device as an unknown non-verizon device. Customer service walked me through various soft/hard reset techniques and nothing worked. They also suggested I try a new SIM card, which failed to work.
So, I turn to the bright minds of the android community. I have already decided not to invoke the Verizon warranty offered, where the result is they take my malfunctioning phone in flawless cosmetic condition and replace it with a "like-new" phone in working condition, because I think it's garbage that a warranty would give out used crap (should fix or replace). I have not contacted Samsung customer support yet because I wanted to see what my options were. I've already attempted flashing different radios and nothing seem to make any difference. If I have to, I will revert it back to stock again and invoke Samsung's warranty program, but I would much rather keep the phone. As it sits, I am stuck with my Motorola Droid Razr Maxx, and that just doesn't cut it.
So I ask, is there anything that can be done? Anyone know of a fix for my situation? I saw something about this in my quest for an answer and I don't know if my situation is a fit for this fix. If anyone has any knowledge of my issue and a work around for it, it would be greatly appreciated. I am at my whits end.
It sounds like you've done your homework on your problem.. The only thing in your post I didn't see was your sim card.. Maybe pulling it wait 2min restart. Shut down and insert,, or maybe a reprovision of the sim may be in order..
Ahaaaa....!!!
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
HHF2 said:
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
Click to expand...
Click to collapse
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
mkruluts said:
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
Click to expand...
Click to collapse
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
HHF2 said:
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
Click to expand...
Click to collapse
Ok. So I tried the reprovsioning mentioned above. When my phone rebooted I was on data and able to make phone calls. Score! However, I checked the IMEI and it said 0. So, thinking that it was just a matter of time before my device began to stop working again... I did the IMEI fix. Now my phone is placing calls and holding data without issue. The OTA updates are flooding in and installing without issues.
I would like to point out, while I feel better having done the combination of both reprovisioning and IMEI fix, ultimately the initial reprovisioning did appear to resolve the issue.
Thanks to everyone for the assistance provided.
Related
Alright, so I just got my Galaxy S3 about 2 weeks ago. As I can't stand the look of Touchwiz, I rooted my phone, unlocked the bootloader, and put AOKP build 3 on there right away.
Everything was working great, except for my lack of Picasa sync, so I flashed BlackBean 5, then JellyWiz, and eventually went back to AOKP build 4. Wanting to get my Picasa sync, I tried flashing a few custom GApps builds, and then reflashed AOKP b4 fresh with the custom GApps.
After booting my phone back up, the "Activating" screen came for about 5 minutes, before it said that it failed. Checked my phones settings, and my IMEI was at 0. I flashed my phone back to stock, then used QPST to restore my IMEI.
IMEI is now displaying properly, but I am still totally unable to get any sort of connection to the Verizon network; voice or data. Do I have a brick? Furthermore, if I do, will relocking the bootloader, running TriangleAway to reset my flash count, and unrooting/factory reset on the stock rom be sufficient to return the phone to Verizon, or will they be able to tell that I messed with it and void my warranty?
reprovision your device with the dialer code *2767*3855#
next time follow the guides stickied before flashing...if you would of did the nv backup via terminal emulator then you would of never lost imei in the first place.
can terdayou
droidstyle said:
reprovision your device with the dialer code *2767*3855#
next time follow the guides stickied before flashing...if you would of did the nv backup via terminal emulator then you would of never lost imei in the first place.
Click to expand...
Click to collapse
Thanks for this; I can't really tell if it works yet because I put my Fassy back in service on this line temporarily, but I will be able to find out tonight when I have a chance to call Verizon. It has improved my situation, though -- I am now seeing signal whereas before the reprovision I had the Ghostbusters/No Smoking No Sign in place of a signal bar.
I unfortunately didn't see any of the stickies as I found all of the instructions I needed my googling and grabbing things from one place or the other. I did find that thread when looking for a solution to this, though, and I have to say that the people on the Development board for this phone are amazing; they have really done an amazing job getting everything that one would need right on the front page.
Also; *would've
Any flashing you did while your bootloader was unlocked wont be counted in the flash counter.
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've figured out how to fix it! First, I went to Section 5 of this http://forum.xda-developers.com/showthread.php?t=1762709 thread and odin-ed back to stock. Next I fixed my IMEI using a guide I found on xda. It was the second part of thishttp://forum.xda-developers.com/showthread.php?t=1804117 thread that says "IMEI is already corrupt".
Next, I did a bunch of things that I don't think I should have done and I ended up with a soft brick phone so I went and flashed back to stock via odin by following this http://forum.xda-developers.com/showthread.php?t=1840030 guide. I don't really know if it was necessary and I ended up getting stuck on the activation screen. If at any time you can not get past the activation screen, the third post down from here shows how to get past it so you could go to your settings and check them out or unlock your bootloader or whatever it is you need to do. But this whole part may not be necessary.
This is the part that I think completely fixed the phone. Probably the most important part of this whole guide. You have to dial *2767*3855# from a completely stock rom (root66 or others). It factory reset my phone and somehow the calls work, although it always says I'm roaming
A couple days ago I rooted my s3 and flashed the CM10.1 ROM. It had problems with mobile data and connecting to 4G and phone calls, so I tried out a bunch of different ROMs before deciding it had to be something else.
I figured out that my IMEI had been erased and since I didn't have it backed up (and I have no idea where my nandroid backup is or what happened to it) I had to manually restore it using some NV items reader writer tool and some other similar tool. It worked but there was something else, I think it was called ERI, was set to none. I kept trying stuff and ended up doing a factory reset. I attempted to unroot my S3, I have no idea if I succeeded in unrooting.
What I just did was soft brick my s3, not completely sure how, but I did then re flash root66 using odin successfully and now I'm back to the activation screen. Now it is stuck trying to activate the phone, but it fails every-time, and I can't do anything but restart the phone. So I restart the phone and have to go through the set up screen again and it tries to re-activate but fails and goes through the whole thing again.
Could someone please help me?
According to the Verizon website the phone is activated.
Update 8:24 PM EST: I have gotten past the activation screen but it says that the phone is out of service and when I try to call someone it says that the "mobile network is not available". Please help.
Since nobody is here to answer me, I will post the answer once I figure out what to do, just in case somebody in the future has the same problem.
I'm going to start by re-rooting my phone. I'll let you know how that goes and if anybody else could help me out that would be great. Thanks.
UPDATE 7:45PM EST:
I successfully re rooted the phone via odin and tried to start it up to no avail. Next I tried to flash a ROM, but I must have forgotten to unlock the bootloader since I couldn't even get the phone to boot completely. Right now I'm flashing back to the vzw root66 rom and then I'm going to re root and try to unlock the boot loader.
UPDATE 8:07PM EST:
I finally figured out how to get past the activation screen and I unlocked my bootloader. Before I flash AOKP I'm going to see if I could fix everything else. I think I'm pretty close to a solution. If anybody else is having the same problem send me a message or reply here, I'll try to answer your questions if you let me know what you've done.
I really just need a way past the activation screen. After that I think I could figure out what to do.
Sorry your having problems. I wish I could help but never ran into that problem so everything you said went over my head otherwise I would of fine a lot of research. At least now you are learning more and more.I just figured I would respond since no one else did.Good luck.
Sent from my SCH-I535 using xda premium
http://forum.xda-developers.com/showpost.php?p=30182790&postcount=1
Have you tried this?
defkult said:
http://forum.xda-developers.com/showpost.php?p=30182790&postcount=1
Have you tried this?
Click to expand...
Click to collapse
Yes, I managed to bypass the activation screen but now I still can not make any calls.
mikeman45 said:
Sorry your having problems. I wish I could help but never ran into that problem so everything you said went over my head otherwise I would of fine a lot of research. At least now you are learning more and more.I just figured I would respond since no one else did.Good luck.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks.
Well I suppose it is hard for a phone to make calls when it isn't activated.
Goodluck on your quest though.
Thanks for the help, I finally got it working.
myoussef0 said:
Thanks for the help, I finally got it working.
Click to expand...
Click to collapse
What was the main problem?
Sent from my SCH-I535 using xda premium
In case someone else has this problem...When I flashed pure 4.2.1, I couldnt get past activation and then found out how to bypass the screen. Tap once in each corner of the screen to bypass activation screen. Then once at home screen go to settings>more(right below WiFi/Bluetooth/data)>mobile networks>CDMA subscription. NV will be selected, change it to RUIM/SIM. Reboot phone. Worked perfectly for me.
No mobile network found
jmarch said:
In case someone else has this problem...When I flashed pure 4.2.1, I couldnt get past activation and then found out how to bypass the screen. Tap once in each corner of the screen to bypass activation screen. Then once at home screen go to settings>more(right below WiFi/Bluetooth/data)>mobile networks>CDMA subscription. NV will be selected, change it to RUIM/SIM. Reboot phone. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for this post. I ran into the same problem (flashing CM 10.1) with my first S3 phone but did not know how to fix it (wish I saw your post ahead of time). I returned phone to stock via Odin and was able to exchange for a second S3 phone via Verizon (since I have phone insurance). I flashed AOKP ms 1 (jb 4.1.2) on second S3 phone and noticed it was hanging on activation and also said no mobile network when trying to make a call. Luckily, the phone spontaneously rebooted on its own and then started working. Previous to my first S3 phone, I had a Galaxy Nexus. Never ran into any problems with the Galaxy Nexus and almost tempted to go back to it since the S3 seems buggy when flashing a new rom. I am afraid I'm going to brick yet another S3 and be out $400 since I don't think phone insurance will allow me to exchange a second time since this probably alert them to the fact that I'm flashing custom roms.
Also, under mobile networks>system select be sure to change from home to automatic. Reboot.
jmarch said:
Also, under mobile networks>system select be sure to change from home to automatic. Reboot.
Click to expand...
Click to collapse
All was working fine until I tried to do this. At first nothing was selected and everything was working, but when I tried selecting automatic and rebooted it selected home for me and it is impossible to change back to automatic without it automatically changing it back to home against my will.
ok so here's the deal folks. I've been trying to fix this problem on my ATT Skyrocke since the 21st. I had flashed a copy of the Liquid Smooth ROM with all data working. Bear in mind, this S2 is net unlocked and APN settings are changeable with my sim card in, and everything is set to Straight Talk APN settings. When LS ROM was installed, everything worked fine, til this fateful day of the 21st where everything just stopped... No network, no data, no nothing. Every once in a while my network shows up and allows me to make short phone calls ranging from 45 seconds to 10 minutes, and sms/mms are even more widely spread on being able to receive. After going through my EFS folder, it seems that the phone is missing a critical file named nv_data. I have everything else in the EFS folder that should be there, at least from my experience, but my data still will not come back up. SOMEONE PLEASE TELL ME THIS IS FIXABLE!!!!!!!!!!!!! I'm losing my mind, considering this is my only work phone for my business, and as of yet, i don't have enough income from this business to buy a new phone.
EDIT*****
Before I forget, which I already did once, I have tried the following steps to fix this:
1: Bought a new sim card tray through ebay - no change
2: Flashed back to stock ROM - (multiple times) no change
3: Flashed multiple older roms - no change
4: Ran the EFSFix off of this: http://forum.xda-developers.com/showthread.php?t=1611796
Currently looking at performing a dark side wipe to install a new custom rom, but not sure if this will work yet or not.
420tuprophit13 said:
ok so here's the deal folks. I've been trying to fix this problem on my ATT Skyrocke since the 21st. I had flashed a copy of the Liquid Smooth ROM with all data working. Bear in mind, this S2 is net unlocked and APN settings are changeable with my sim card in, and everything is set to Straight Talk APN settings. When LS ROM was installed, everything worked fine, til this fateful day of the 21st where everything just stopped... No network, no data, no nothing. Every once in a while my network shows up and allows me to make short phone calls ranging from 45 seconds to 10 minutes, and sms/mms are even more widely spread on being able to receive. After going through my EFS folder, it seems that the phone is missing a critical file named nv_data. I have everything else in the EFS folder that should be there, at least from my experience, but my data still will not come back up. SOMEONE PLEASE TELL ME THIS IS FIXABLE!!!!!!!!!!!!! I'm losing my mind, considering this is my only work phone for my business, and as of yet, i don't have enough income from this business to buy a new phone.
EDIT*****
Before I forget, which I already did once, I have tried the following steps to fix this:
1: Bought a new sim card tray through ebay - no change
2: Flashed back to stock ROM - (multiple times) no change
3: Flashed multiple older roms - no change
4: Ran the EFSFix off of this: http://forum.xda-developers.com/showthread.php?t=1611796
Currently looking at performing a dark side wipe to install a new custom rom, but not sure if this will work yet or not.
Click to expand...
Click to collapse
goto READ THIS B4 POSTING | THE MOST Common Questions Answered HERE read/do q)25.d and borrow someones active att sim card, if after that phone still doesnt work right then its some kind of hw failure
hey vin. actually i had tried that thread and instructions for such already. although i went ahead and did it again in hopes that maybe i just did it wrong, but no change.
Here's a little update:
The baseband is known, running on I727UCMC1 baseband, but the IMEI number shows up as 0/00. I spent the entire night searching the forums here and over at androidforums.com and ran through google. There's no listing of the baseband being known, but the imei number being corrupt. Maybe I'm just using the wrong keywords... IDK but I do know this is really strange. I've never ran into this issue before.
So anyone know why the Baseband would be known, but the IMEI corrupt?
420tuprophit13 said:
hey vin. actually i had tried that thread and instructions for such already. although i went ahead and did it again in hopes that maybe i just did it wrong, but no change.
Here's a little update:
The baseband is known, running on I727UCMC1 baseband, but the IMEI number shows up as 0/00. I spent the entire night searching the forums here and over at androidforums.com and ran through google. There's no listing of the baseband being known, but the imei number being corrupt. Maybe I'm just using the wrong keywords... IDK but I do know this is really strange. I've never ran into this issue before.
So anyone know why the Baseband would be known, but the IMEI corrupt?
Click to expand...
Click to collapse
baseband aka radio has nothing todo w/the imei.
as to why imei got corrupted, idk why it happened and i dont know if theres a fix for that
edit: a bad radio might corrupt the efs folder though not sure if thats what happened to u
it seems you might have a corrupted efs folder
search for corrupted imei
try this http://forum.xda-developers.com/showthread.php?t=1611796
>> 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.