Hello! I have a problem with my fascinate. I flashed aokp build 37 and was able to use it for about 2 days when suddenly the data and calling just stopped working. the signal bars still work however. So i odined back to eh03 stock and the 3g icon still does not come up and I am still unable to make calls. Could anyone please help me? thank you!
I assume you have flashed the correct eh03 stock package and that you have the correct radio package flashed as well. So as far as I can tell if you flashed everything correctly, then that really only leaves one more possibility unfortunately. Something tells me it us not the fault of aokp.
Sent from my SCH-I500 using Tapatalk
i have flashed back to stock multiple times before just fine. and im sure its not aokp but probably something stupid i did. I just cant figure it out.
thats odd, i am getting service now after waiting for a couple of hours. very strange.
update: it has been on and off throughout the day today. something is definitely wrong.
Do you guys think a dmu reset would work? Or is that just for data? Because I'm not able to make calls
I have concluded that my phone only does not work at my home. I'm currently at school and it is working perfectly. I live near los angeles this is very strange. It was not like this last week.
Sent from my SCH-I500 using XDA
I called verizon and they made me jump through some hoops trying to get my phone to work but no luck. They said its a device problem but I find that hard to believe when my phone works perfectly fine outside of a 2 mile radius from my house.
Sent from my SCH-I500 using XDA
I would suggest the prl update. I'm not sure what the number is, #22981 or something...don't quote me!
Also, check out the Glitched build for AOPK for the Fascinate. You may enjoy it better than standard build 37.
i have done *228 and did option 1 and 2 when i was away from home already but my phone was still borked as soon as i go home.
luke949 said:
i have done *228 and did option 1 and 2 when i was away from home already but my phone was still borked as soon as i go home.
Click to expand...
Click to collapse
Out of curiosity did you reflash gapps? Just trying to think of suggestions.
If your stock aopk37 you may need a different kernel and it may work outside of home area because of different towers or networks. Hmmm....very odd.
Sent from my SCH-I500 using Tapatalk 2
Yes I reflashed gapps and the problem persists in stock eh03, stock aokp, and glitched aokp.
Sent from my SCH-I500 using XDA
I was having a similar issue
Last Saturdat morning I woke up to a phone (AOKP milestone 5 and Glitch v14 B6 I500) that was in a boot loop. Nothing had changed for weeks so other than not charging my battery that night, it was a loop without a cause.
Yesterday I followed Droidstyles script (Back to CM7 EH03 then to Glitched AOKP Build 37 with a stop at build 2 per instructions).
At first I had a moble network connection but the service was poor (As usual) so I called *228. The ROM knew I was doing an activate / update so it removed access to the dialpad. The Verizon function ahs 2 options but it's without I dialpad I couldn't select 1 or 2 so I waited. The robot on the other end of the line stopped asking me to press 1 or 2 and said the phone was being programmed. Then I tried to make a call and the "No Mobile Network" sign" appeared. Last night I flashed the Glitch 14 kernel and my phone worked fine for 24 hours then I tried *228 again and No phone.
As I was writing this note I had an idea what would happen if I rebooted plain old reboot? I did that and all of sudden I have a working phone again.
I have this same problem. (I've flashed AOKP build 36, 37, and 38...)
I have 3g signal. (sometimes) But I can't make or receive any calls/text messages. What the hell is going on? I have updated my profile and PRL... I called sprint, did a whole bunch of resets, going into the dial pad #*#* or whatever. Still not working after 10 agonizing hours. Someone please help.
Since you can't use the number pad when activating you can call *22890 to activate and *22891 to update the PRL. That's pretty much standard for any MTD rom.
Sent from my SCH-I500 using XDA
Related
I got a droid eris from a friend who switched to that apple thingy. It is still going to be a bit before I can get it activated, so I started playing with it. When I first got it, he had wiped and factory reset it, and it would connect to 3g and get signal. I skipped activation for now. Here's what I did in order:
I followed this guide http://theunlockr.com/2010/09/22/how-to-root-the-htc-droid-eris-unrevoked-method/ to get clockworkmod recovery installed.
I installed this rom http://forum.xda-developers.com/showthread.php?t=944430 and once again just skipped activation. I set up wifi and discovered the world of android
Today I noticed there were no signal bars and an "x" by them when I turned off airplane mode. On the lock screen it said "No Service". My verizon razr gets full bars so I know I'm in range. After trying a few things like reflashing cyanogen, I followed this: http://forum.xda-developers.com/showthread.php?t=792026 and used the rom that also flashes the radio.
It's now un-rooted, clockworkmod is gone, and its on the stock 2.1 verizon firmware. It still says "No service". I'm at a loss. Did I permanently destory this phone somehow, or is there a way to fix this and get cyanogen back on and working with service?
Update: After trying activation about 10 times and constantly getting a no service error, I decided to try to manually program a verizon prl. I went to emergency call and did a ##3424# to go into usb programming mode for QXDM. Out of nowhere...SERVICE! I backed out and hit Activate and viola! Automated voice lady was there to tell me it couldn't activate(yet). I powered the phone down and put it on a shelf. I'm not touching the dang thing until I get it activated. Now I'm wondering a few things. First, what the heck happened? Second, after I get it activated, is there a chance this will happen again after rooting and installing cyanogen?
As soon as you activate it, it should be fine
Sent from my ERIS GSBv2.0 using XDA App
the kid escobar said:
As soon as you activate it, it should be fine
Sent from my ERIS GSBv2.0 using XDA App
Click to expand...
Click to collapse
Right, but the state it was in I couldn't activate it. I somehow randomly got it to be able to activate again if you see my update tho.
I just know from experience that when I forgot to pay my bill a while back, I did not have any service bars or anything until I called them up later that day and reactivated it. It seems like when you first got the phone for some reason even though it wasn't activated it showed that the phone had a data signal. I could be misinterpreting the issue though.
Sent from my ERIS GSBv2.0 using XDA App
I've had that happen a couple times flashing themes.
Wiped data/cache fixed once other time never figured it out, just reformated sys/data/cache and flashed sbf.
All was back to norm then. :s
Sent from my DROIDX using XDA Premium App
the kid escobar said:
I just know from experience that when I forgot to pay my bill a while back, I did not have any service bars or anything until I called them up later that day and reactivated it. It seems like when you first got the phone for some reason even though it wasn't activated it showed that the phone had a data signal. I could be misinterpreting the issue though.
Sent from my ERIS GSBv2.0 using XDA App
Click to expand...
Click to collapse
That's weird. But from a first boot 100% stock the phone still connects to the network. Otherwise there's no way to get it activated. So no matter what, when functioning properly on a cdma network it should have bars if you're in range of a tower. Now it is functioning properly, and I have signal at the initial setup and activation screen.
So I installed CM7 following the wiki on there site, using Revolutionary.io Everything worked fine, got s-off, installed the CWM recovery and then installed CM7. Well when I boot to CM7 the phone is telling me that it is no longer activated. It worked perfectly before. Ive rooted several EVOs on Sprint in the past and have no issues, didnt know if anyone had has some similar problems before and what they did to fix it.
This is a common Revolutionary bug.
You can try to take the battery out for a full minute and then go to settings, update, update profile. Then update the PRL. This did not work for me.
If that fails you need to try to send text messages and record the error codes when they fail. Call sprint from a different phone and give them those codes (dont tell them you rooted or s-off'ed) Hopefully you get someone with half a brain and they ask you for the IMEL code (behind the battery) and reset your phone. It took me 3 calls (and resets) to Sprint over a week but finally it stuck. On a friends phone it only took 1 reset by Sprint to get it to work. If you have any call or text failures after Sprint resets it you need to call them again.
I personally believe this is caused by a failure in the hands-free activation mechanism preformed after running Revolutionary.
Is it possible that you flashed a GSM rom aka the wrong radios? I'm assuming you mean it has no network connections by "not activated", some more detail might help you get a solution quicker.
Good luck!
Well after some reading, people were saying that I should go back to stock and then reactivate. So I did that and when back to CM7 and and nothing. Others were saying to play with the MSL buy dialing ##3282 or 228 but I didn't have the code for it so I just went back to CM7 and it turns out it works now. Not sure why but who the hell cares. Sucks that Revolutionary has those issues. Its worked great for me so far.
I had this happen too right after I rooted a week ago using Revolutionary.
It's no big deal and you don't need to waste your time switching roms or jumping through hoops just call Sprint and tell the your phone just stopped receiving calls.
In my case my 3g data worked but not texts or calls. I called Sprint and just said my phone wasn't making or receiving texts or calls and I wasn't sure why.
They just reset something on their end or whatever they do and I was good to go. No need to do anything else.
Sent from my PG86100 using xda premium
So, all of a sudden my GS4 doesn't want to connect to VZW's network. I can't place any calls, send texts or receive any calls or texts. LTE is working fine. I've tried all of the different provisioning codes, but none of them go through because as soon as I tap the call button I just get the error message "Mobile network not available".
I've flashed different ROM's to see if that clears it up, rebooted, wiped, restored... everything. Nothing seems to be working.
Also, in About Phone>Status, the IMEI field is populated and has a bunch of numbers and stuff in it, so it appears normal. Everything appears normal. Here's what it says in About Phone>Status:
Network: Verizon Wireless
Mobile network type: LTE:14
Service State: Out of Service
Roaming: Not Roaming
Mobile network state: Disconnected
And yes, before any asks, I am in a spot where I normally get coverage, so I know that's not the problem.
Anyone have any ideas on how to fix this?
UPDATE: Restored to a 3 day old backup and all is well again. Upon the first boot I still got the same error message when I tried to place a call so I then dialed *228 and got a little messaging saying I was now activated, and everything is working now. So yeah, I don't really know how I fixed it, but whatever as long as it's working.
S4 signal issues
ive been having same issue Network not availiable and also where i normally have 4g service i know only get 3g.Ive flashed several different roms still same issue.Could this be glitch in vzw AWS system?Is there any other radios we can flash?
I'm surprised it worked after *228. That's a good way to nuke a sim, making it unusable.
Sent from my SCH-I545 using Tapatalk 4 Beta
ive been having same issue Network not availiable and also where i normally have 4g service i know only get 3g.Ive flashed several different roms still same issue.Could this be glitch in vzw AWS system?Is there any other radios we can flash?
Click to expand...
Click to collapse
bump. did you ever get this solved? im having the same thing
Same thing here. Connection is intermittent. 4g/3g comes and goes. Tried reflashing different roms, factory wipes, nothing seems to work. Does anyone have a fix for this yet?
Its a Verizon system error. they're fixing it as we speak. I went to the store and thats what I was told.
Sent from my SCH-I545 using xda app-developers app
Sounds like they fed you some bs. I took an alcohol wipe and cleaned the contacts on my sim card. Seems to have helped but I'm still experiencing issues.
Sent from my SCH-I545 using Tapatalk 4 Beta
njg9837 said:
Sounds like they fed you some bs. I took an alcohol wipe and cleaned the contacts on my sim card. Seems to have helped but I'm still experiencing issues.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Is that so? Because someone else next to me came in with the same problem. And they showed me the Verizon Alert.
Sent from my SCH-I545 using xda app-developers app
Same issue, however i can send and recieve texts, just no in or out calls. Im not sure if my issue was due to me trying to simunlock but that when it started right after. I did make a backup with the EFS using TWRP and was thinking of restoring that, but do you think that just doing the *228 will do the trick? or restore the backup to the prior EFS and do the *228. Kinda concerned that someone said here that doing the 288 call can mess up the sim, why is that excactly?
Did u use twrp or cwm to restore, if twrp, did u do a full wipe first? And can u describe the steps done? I have the same issue and did the restore but I'm still having this issue. I did not do a full wipe cause I thought twrp did this automatically. But also if a full wipe it's done, does this mean we need to reflash the Rom and then the backup? Looking back on my s2, I remember the fone not booting due to missing this step but that was w cwm. Let me know if u would, thanks
phantomberry said:
ive been having same issue Network not availiable and also where i normally have 4g service i know only get 3g.Ive flashed several different roms still same issue.Could this be glitch in vzw AWS system?Is there any other radios we can flash?
Click to expand...
Click to collapse
I did the hard reset to my fully flashed pageplus phone (verizon s4) and when i tried to activate it using normal verizon network, i cant make calls or send text but the 3G data is working fine. Any help on this please?
So a few days back I decided to install cloudy and messed with the build.prop a little bit. I was having 3g and roaming issues so I decided to try jasmine v2. Same issues there as well. Then I went back to v1.1 and now I'm back on fully rooted stock. My problem is if I fully pull the battery, wait a few seconds, and then boot back up I am able to get 4g for about 10 seconds or so, after which time the phone always mysteriously jumps back to 3g and never leaves from there. Seriously weird. While I was having the issues with Cloudy I dialed *228 because I read something about updating the preferred roaming list (and looking back I realize I shouldn't have done this!), but I always get 4g for a few seconds after booting up still...it just always goes away. Anyone have any useful suggestions?
I'd stop by a verizon store or give them a call and get a new sim card.
ohlin5 said:
So a few days back I decided to install cloudy and messed with the build.prop a little bit. I was having 3g and roaming issues so I decided to try jasmine v2. Same issues there as well. Then I went back to v1.1 and now I'm back on fully rooted stock. My problem is if I fully pull the battery, wait a few seconds, and then boot back up I am able to get 4g for about 10 seconds or so, after which time the phone always mysteriously jumps back to 3g and never leaves from there. Seriously weird. While I was having the issues with Cloudy I dialed *228 because I read something about updating the preferred roaming list (and looking back I realize I shouldn't have done this!), but I always get 4g for a few seconds after booting up still...it just always goes away. Anyone have any useful suggestions?
Click to expand...
Click to collapse
hawkswind1 said:
I'd stop by a verizon store or give them a call and get a new sim card.
Click to expand...
Click to collapse
I might be stuck doing this, as since Cloudy I've tried Jasmine 2.0, 1.1, the stock root deodex rom by Beans, all with normal wipes and advanced wipes prior to flashing. Lol I even used my Verizon to temporarily switch my phone line to an old crappy non-smartphone I have laying around and then back to the G3 thinking maybe possible that could somehow "restore" proper programming or something, all with no dice! Needless to say, it was a late night at that point.
Then I got to thinking, that maybe the full restore guide here on XDA (that I've used before) might do a more "full" restore than simply flashing a new rom. So I did that, and so far my issue appears to be fixed! More testing is still needed at this point, but if there's anyone who comes across similar issues, you might try that. I'll report back once I know for sure if this was the solution. Thanks!
You don't *228 a 4G phone, they update their PRLs, on their own, on boot. You may have fried your SIM card.
spotmark said:
You don't *228 a 4G phone, they update their PRLs, on their own, on boot. You may have fried your SIM card.
Click to expand...
Click to collapse
Yep...as the OP clearly says, looking back I realize I shouldn't have done that It didn't hurt my SIM card.....I'm not an expert by any means, but I feel like something must have somehow gotten seriously borked with the radio or something, I really don't know - all I know is using the "full restore to stock" instructions with the .tot and LG flash tool, everything is back up and running great again. Figured I'd share my experiences on the off chance anyone else has any similar issues!
So, have you re-done all the work to reinstall Cloudy ? If so, did the 4g to 3g drop problem return ? I am not sure from following thus threading the problem was with Cloudy.
Sent from my VS985 4G using Tapatalk
spotmark said:
You don't *228 a 4G phone, they update their PRLs, on their own, on boot. You may have fried your SIM card.
Click to expand...
Click to collapse
trent999 said:
So, have you re-done all the work to reinstall Cloudy ? If so, did the 4g to 3g drop problem return ? I am not sure from following thus threading the problem was with Cloudy.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
I'm not sure exactly where the problem came in, whether from Cloudy or not, but I'm not refreshing it to find out lol, as I was still having definite drop to 3g and never return problems, along with it saying I was roaming during those times. I'm just gonna stick with the stability of the rooted stock US rom for now
ok the long story short is i have been doing this for years and this is the first time i have ever had this issue so please bear with me. I have been trying everything to get cm13 to work right on my phone and i was reading about taking an older version of it that worked as i wasent getting text messages and in the cellular option it was force closing on the carrier settings. anyway i went to cm 12.1 and that was working so i dirty flashed cm 13 over that. that is when i screwed it up. I can no longer get voice or text. data is in and out with a x in the signal area. i have relocked and ruu'ed back to stock and it doesnt help. i have tried reinstalling a new rom after unlocking and while the rom with work with wifi i lost all my data for sprint. when i try to profile update it will but if you do a ##72786# it will show my MDN or phone number as no along with the prl which shows 00000. I thought i could fix it by just adding it in via ##3282# but when i commit it it says commit failed and restarts. What is really weird is i cannot edit it CDMA workshop either. it says it fails in the NV dir number or whatnot. im very confused as usually i can fix anything that happens but nothing seems to work....anybody help with this??
I had this happen. A relock , Ruu and several factory resets finely worked for me. Only advice I can offer is reset and power cy me a few times
Sent from my HTC0P3P7 using Tapatalk
sin-cal said:
I had this happen. A relock , Ruu and several factory resets finely worked for me. Only advice I can offer is reset and power cy me a few times
Sent from my HTC0P3P7 using Tapatalk
Click to expand...
Click to collapse
after i switched phones to my wifes old phone which was the same and a few reformats it is now working again.