Related
Ok, I've tried my best to figure this out on my own and now I need some help.
Had my CDMA Hero flashed to Cricket a few weeks ago on talk and text. Just found out that I can get Sprint service, so I want to activate on Sprint instead of Cricket.
Here's what I've tried so far...
1. Latest RUU (1.56) installed successfully. Data in ##3282# seems to have stayed the same.
2. Manually changed my MSID and MDN to the correct Sprint settings given to me by tech support. Still won't activate or Update Profile.
3. Executed ##786#. Still won't activate or Update.
4. Reset User Name in ##3282# and committed. Still won't activate.
5. Called and double checked that my ESN is free and clear. It is. Tried all above procedures, still no luck.
6. Wiped Dalvik, and caches through Recovery 1.5.2. Also wiped phone through the white screen boot up procedure with the volume key. Still no luck.
From what I've been told by tech support, if none of these things gets my phone to activate on Sprint, then I need to get my phone flashed back to Sprint since it's currently flashed to Cricket.
Can anyone give me any advice? Is anyone else on Sprint, maybe even in the Eastern NC area, who wouldn't mind giving me some edittable settings from ##3282# or other things to check?
Getting a little frustrated but not giving up yet. I can't afford or have the time to wait until I can afford to take this phone somewhere and get someone else to do it for me. If anyone can help me out, I'll be happy to write a fully detailed guide on this whole thing for anyone else who has this problem in the future!!
Another bit of info. I just tried flashing the RUU again, since my phone wouldn't even boot on the last ##786# I tried. To get it ready to use RUU again, I loaded my Fresh 1.1 nandroid, ran rhe RUU again, and now there's a change.
My passwords for ##3282#, etc. are no longer "000000", and they're back to the default "190320". Does this mean that I'm no longer unlocked? Am I making progress now?
Grr.
LMAO man... I was in the same position as you ... but I was in Metropcs...so first of all to flash it to metropcs I went to a store called WirelessToyz and they did it for me, I got tired of metropc's slowness and I wanted to go to Sprint, so I had a hard time doing it until I went back to WirelessToyz and they flashed it back to sprint, even tough you flash the RUU that does not make it run on Sprint , when they "flash it" they do something else, long story short go to wherever you did that and flash it back to sprint, you might need to pay money.
I've been having a problem where I would swap ESN's on Sprint for another phone and then go back to the Android Vogue and notice data would not be working. In WM there is an Update Profile icon that can reinitiate this. Is there something similar for Android? If not, how do you guys suggest getting data working for someone who swaps phones back and forth often?
Run Android from SD. AFAIK, we don't even have access to the operator settings like in WM.
That's what I thought. I still prefer to run it straight from NAND though I take you guys just flash to WM and then back to Android in order to get data working?
I run from SD, but that is correct. Though I don't think most people swap phones like that. Do becareful with doing too many flashes though as some people attribute it to killing their phones.
Ok so you repaired the Vogue's esn? The problem is that your data setting and passwords are different on your Vogue. I don't know if your android rom has epst. Go to the phone and dial ##778#, if it works you can see your settings. Just try to match them as close as possible to your currently working phone. To edit these values you will need your SPC (msl codes). Typically for phone you need to enter your MDN #(your phone #) and your MSID #. For data you need to match up your MIP settings, MIP Default profile and MIP Custumer Profile 1. Just step through all the settings and match them up with the original phone. Since both are Sprint phones their should not be that many differences.
In the past I have just done a reinstall of an Offical WinMo image from Sprint then get data and phone working. For data go into Settings, phone, internet settings, and run that (I can't remember what the function is called). That should provision your data. Once you are up and running then you should be able to flash back to Android and be fine. In provisioning this way, there may be an issue where it changes your passwords and your original phone may not have data. I have had it happen where both phones would work and sometimes the data on the original does not work. You can dial ##778# in both and compare to make sure they are the same.
If you go into the WinMo section and search you can find information about getting data to work. If you don't find it there try going into the Mogul WinMo section and search. Getting data to work on a WinMo was very common issue when flashing different Roms and is virtually the same process for all WinMo phones. On the WinMo side it's been pretty thoroughly covered on XDA and PPCGEEKS.
You could try a search at mobile-files.us and mobile-files.com. They tend to cover a lot of what you are doing here.
EPST is a executable file that comes with the WinMo roms and is usually in the Windows folder.
I wonder if someone could actually re-code a new version that would work on Droid/Linux?
How do the new Droid phones that come from Sprint get programmed?
I haven't tried this yet, but I wonder if you're just switching back and forth if you really need the provisioning. I've switched back with the flash back to WinMo method, but noticed that the MSID and other data is already still in there. It does go through a data provisioning process of some sort, so maybe it is necessary. But still, if it's already been activated on the phone number previously, it seems like there's some slim chance it might not be necessary to flash back to WM to do a simple ESN swap back.
Has anyone tried it? I'll probably try out my TP2 on Android for a few days again soon now that sound is working, but then get frustrated by the parts that still don't work well and flash back to the Vogue again. So maybe I'll try it then if nobody else has.
You need to switch back to windows mobile in order to activate, even if the phone has the mdn and msid programed in it still has a provisioning code it sends out so you can activate it but you just won't have data
Sent from my HERO200 using XDA App
a quick history of what I've done so far
Sumsung I897 captivate from ATT unlock and being used on Telus network was working great for about 4 days, then all kinds of problem started cropping up.
Phone came unlocked, I rooted using update.zip from xda, installed rom manager and started removing ATT bloatware, entered SMS and APN info which worked fine.
Yesterday I noticed that where I once got good reception I was now getting nothing and would have to drive down the street before I would get something descent. I thought maybe I'd put it back to stock with rom manager and see if that would help which it did not. It actually made it worse, decided to go all out and use the Odin3 one click downloader just to make sure I was back to stock firmware. This didn't work either but now I can enter the SMS and change the preferred network type but it doesn't save. Preferred network type is grayed out and even though I can change it it never save same as SMS.
Now I can't hold connecting in my living room where my wifes Milestone gets full bars. I tried taking the phone to where I had the best signal and change the preferred network, SMS, and set the network operator but it doesn't save any info, can't find on operator half the time on manual or auto and gave me an error and logged it to #*9900#
I've been at this for 2 days straight and can't figure out how to get it right back to stock, it seems to keep hanging onto the same preferred network and not saving anything I enter.
What can I do to get back to stock, and it has to be something that wipes everything clean, clean, clean, because even the GSM disconnects stay logged under *#*#4636#*#*
***I desperately even tried pulling the batt and SIM card for the night in hopes that would do something.
So, if I'm understand what happened correctly, you bought an unlocked Captivate, rooted it, deleted some bloatware, entered your Telus APN info and everything worked awesome for about four days. Now everything has gone down the hole. Is that right?
If that is the case, then we need to figure out what changed. Using Odin3 would have definitely put you back to stock/unrooted your phone, I don't think you could go back any further than that. If I were you, I would act like I first got the phone. As in, I would do everything you did to it, as if was day one. At one point, everything worked fine. Try to recreate that. You can always look into exchanging it or perhaps Samsung customer support can give you a little more insight to what's going on. Here's the number if you want to try them out.
Samsung customer service - 1.800.726.7864
Thanks, I've gone through the process a few times today from start to finish trying to figure it out ... maybe some of the problems aren't real problems and just limitations that I didn't know where their. I've since flash with odin3+re-partion to the bone stock i897UCJF6 as in not the one click method. It loaded fine but still have the same issue, I can't set preferred network type or get it to keep the number entered into SMSC. I think if I can get passed that I'll be be one the up side of winning. I keep noticing that the log of GSM disconnects never clears or the usage statistics under *#*#4636#*# , I'm thinking its in the same area that other bad data is being held onto instead of being cleared when flash firmware or factory reset.
Is anyone able to change preferred network type? maybe I was never able to change it but I think I should be able too.
I may be wrong in assuming this but I don't think ATT is going to be interested helping me connect one of their handset that I'm trying to use on foreign network, but I could be wrong and is an open option.
*#*#197328640#*#*
debug screen
phone control
network control
band selection
wcdma band
wcdma all
menu->end
used this to lock my phone to WCDMA only so that problem is solved
*** never mind posted to soon it still didn't stick after rebooting
be carefull using the service menu as I have no idea what most of this stuff does
I got the SMS service number issue fix by taking out my sim, swapping in another known working sim from the same network, setting the service number, pressing update and then swapping back. Before every time I tried to update the service number it spit out an "update error" can anybody tell where the SMS config data is stored? on the phone or sim.
The only problem I'm having now is with reception which maybe fixable if I can set the preferred network to WCDMA only. But the button for that option is a light blue colour vs other phones that I can change this setting on. Does the blue mean anything like a locked function or something that set by the firmware as unchangeable?
*** SOLUTION ***
Thank cellzealot for reiterating how to bypass the initial device/account setup wizard, as well as his and a few others' findings with the RadioComm tweaking.
All I had to do was pop my homemade Bell microSIM I cut out from my old fullsize one in, complete the steps outlined for the RadioComm patch and the four corner touch trick to bypass the setup wizard.
(Starting in the upper left corner, simply touch all four corners of the visible screen in a clockwise rotation, ie: upper left, upper right, lower right then lower left).
*** SOLUTION ***
--------------------------
Hey all, just got my D4 in the mail today and have been trying to get the GSM functionality working for a few hours. I live in Canada, bought it used from eBay and so I don't have a Verizon account, nor do I have access to anyone with one.
I had no trouble at all using RadioComm to change the 8-byte string as per the threads on this and a few other forums, but I'm still getting the "This SIM card is from an unknown source" pop-up when I click the Android to begin the initial setup of the phone... and there is no way I can find around it.
I can see the signal bars now that I have a micro SIM that I've activated with my carrier (Bell Mobility) inserted into the microSIM slot in the back of the phone, but it still doesn't want to let me boot up. The only options in the pop-up telling me about the Unknown SIM are either Emergency Call or Power Off.
Anybody have any ideas? I've tried flashing up to the 219 fastboot as well with no luck, and of course applied the RadioComm edit immediately afterwards. I have a feeling that the phone only needs to be initially setup and then I'd be able to boot it up, because as I mentioned I can see that it's getting a signal but doesn't want to let me get into the initial user setup.
(And no, I'm not a n00b. Check the Droid 3 forum... )
Forgot to mention that the eBay seller didn't include their SIM so I don't have a Verizon micro SIM card, unfortunately for me. I have a ****ty feeling that I need to have one in just for the initial device setup then I'd be able to swap it out.
Argh!
You don't need a SIM to go through the setup process. Try it without a SIM. When you've completed the process reboot with the SIM and try to change the network manually. The SIM is unknown pop-up won't go away, I can tell you that much. When I was on 215, 219 and even AOSP/AOKP the pop-up came as soon as I entered my PIN. So don't worry about that. Sometimes it took a few minutes to get a signal. Recheck with RadioComm.
I had Safestrap on my system and that worked immediately. But the non safe system would not connect. Only after a couple of days. I can't remember if this is because I modified my build.prop.
If you're willing, you could try the ICS leak. I applied it and am very happy with it. It has settings for CDMA/GSM/World. Worked right away (had to setup APN). As you may have read, updating COULD take you off the official update path. But for me it was worth it.
It won't go anywhere but the screen that says "SIM Unknown"; the only two options it provides are two buttons on the bottom of the gray screen with the aforementioned message to either go into Emergency Dialer or Power Off. It's really frustrating! If I could just get past the setup part, I know this will work.
I can see the signal bars and can receive calls and receive texts (as well as reply to them, but I can't initiate them).
It also says Bell in the notification bar.
I am pretty tempted to do what you suggested and was debating it earlier, but haven't been able to get a concrete answer: has anyone tried to flash back to .215/.219 after applying the leaked update?
Yes and you will softbrick your phone! After updating to ICS the will phone run on a new kernel. Flashing SBF with an older kernel won't work.
The only thing I can think of is boot without SIM. Then edit your build.prop (you will need root). And hope now you can click "OK" at the bottom of the Unknown SIM pop-up.
Try chaning this in build.prop, reboot and check if you're able to click OK when the pop-up appears:
ro.default_usb_mode=2
persist.ril.modem.mode=2
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.gsm-routes-us-smsc=0
These are the values I changed (apart from increase heap and wifi timing). Hopefully now you can click on OK so the screen goes away.
That's the problem, though, I can't edit any files or change anything because I can't get past the setup screen. I appreciate the help though!
I've tried without a SIM inserted and it just says it needs to have one, then prompts me to either Power Off or Emergency Dial, just like the other message about the Unknown SIM.
At any point in time did you ever have a Verizon SIM card inserted in your phone? I'm really perplexed about this one.
I don't think I'm going to try flashing the ICS leak just yet, just in case. Especially if it's not presently rootable.
I'm sure I'm not the only person this has or will happen to, I bought the phone from an American owner on eBay but I live in Canada and have inserted a Canadian GSM/UMTS carrier's SIM inside.
Nobody from Canada, either with Telus, Rogers or Bell with a D4 out there that managed to get it working?
Well, I plugged away at it long enough and finally managed to get past the initial setup screen, at least into the Settings menu so I could enable adb and installing unknown apps. That's all I needed...
Eventually a Smart Actions notification popped up and actually allowed me to set up a Smart Action without going through the setup, so I just made one that inevitably let me into the Settings menu and that was all she wrote.
Weird that this was happening though. I clearly have the GSM functions working as I can make and receive calls, but the phone is acting as if it is still locked and doesn't want to operate with a non-Verizon SIM.
I'm running .219, in case anyone was wondering.
But now you're passed the screen right? So why not root and try editing the build.prop. Like I wrote, this is all I edited and was able to use the phone with and without a SIM in it.
I did have a Verizon SIM, but I took it out at some point, before I had GSM working! It took me some days to get GSM working on 215 and 219. Wouldn't work without the edited build.prop! If you're afraid of testing, install safeboot. Then flash 215, update to 219 and use that one for testing.
You can bypass the initial setup screen by touching the four corners of the screen going clockwise starting at the top left. That will allow you to use the phone normally after that, but the unknown SIM error will persist.
cellzealot said:
You can bypass the initial setup screen by touching the four corners of the screen going clockwise starting at the top left. That will allow you to use the phone normally after that, but the unknown SIM error will persist.
Click to expand...
Click to collapse
I knew I remember hearing that somewhere. You sir, are a lifesaver. My previously mentioned workaround was okay but this is significantly easier. Especially considering I bootlooped my phone tinkering with build.prop settings and wasn't able to luck out and get that Smart Actions popup while stuck at the initial setup screen.
Thanks a million for your help!
(You too, Die Bruine. Trust me, I'm not afraid of making build.prop tweaks, I've been at this game for a while... )
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
rmx36 said:
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
Click to expand...
Click to collapse
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first. EDIT: NOPE! Flashing the stock kernel from the ROM did not do it. Looks like total reformat/flash is next!
markwebb said:
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first.
Click to expand...
Click to collapse
I just got my Nexus 6 and I am also on Verizon and had the cell coverage drop too. I backed up my apps with titanium backup and did a factory reset and signal came back. I only had it for a day and went to Canada and on my way back to the US I noticed the cell bars were gone. I was just rooted and boot loader unlocked and otherwise stock. I read online that others had this issue when they got to places in the US that had little or no signal. I also noticed that under cellular network settings it loads up with Global under the preferred network type even though it has an option for "LTE (recommended)" and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected. With global selected it works perfectly with calls and LTE, so not sure what that means or if my selecting LTE made it drop the signal after going back from Canada.
Yep, total flash of factory image fixed it. Sigh. Early enough in the day for me to get everything set up again.
Same. About to do it too... I've done too many factory resets with this already. Kind of annoying.
I am in the same boat. Had no problems until I flashed bliss 1.5 then was stuck on 3g. Tried a clean flash of Slim and still stuck on 3g. I will try a stock rom but I am not very hopeful at this point. It's looking a like a reformat here as well :/
Ended up having to format everything and start from scratch again. I'm running a stock ROM now and in weary to try another cm ROM
Don't know if it'll help, but try LTE Discovery app in the Play Store. I use it from time to time to reset my data connection.
Having the same issue, running CM12 daily, have been for a week or so. Midday today it drops LTE, 3g data was working, then a few minutes later to no data. I didn't change anything, nothing new installed. I did reboot the phone at some point before this but that is all...
My only fix was to backup via trwp, restore stock rom, factory reset, reboot & let sim activate, then restore cm12 via twrp... it's a 20-30 min fix all said and done.... pita
Maybe its something Verizon is doing, because I didn't change anything and then next thing you know no data. I hope it's a simple fix for CM12 but I see this popping up more the last few days. Hopefully someone will figure it out. I like CM and prefer it over stock but I am not going to do this multiple times a day just to keep CM...
lohonda said:
...and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected.
Click to expand...
Click to collapse
I just checked and global is still an option for me. I've bounced back and forth, looking to see if anything changes..
Same thing has happened to me last night, lost connection to VZW cell and data. Looking at the field test menus, it seems like the SIM/device understand GSM but NOT CDMA anymore. So I believe the issue has something to do with that. Tried everything, but will nuke and repave most likely....also lost Global as well. and LTE Discovery shows GSM stuff nothing for CDMA
Tried the SIM in another device and it works so its not the SIM.
OK I tried a world of things to recover like some of you may have....its something in Userdata because if I flash everything but userdata it wont work. I am going to try and recover from the backup I had before this happened to see if that works....otherwise rebuild from scratch
will post back
UPDATE: So restoring a backup seems to be ok once you get the SIM back.
Having the same issue over here as well... After a month or AI of having the 6, now I randomly drop service where I would normally have full LTE. I almost NEVER get LTE now and am at most on H with a couple bars then it drops out again. Have also.noticed WiFi connection is very shakey.
Any one find a fix?
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
th3g0d said:
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
Click to expand...
Click to collapse
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
quidpro said:
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
Click to expand...
Click to collapse
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Edit: OK, just pinpointed MY issue. I have to wait for the "no service" text to change into "emergency calls only" before entering my pin or I don't have any service just the exclamation mark :/
th3g0d said:
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Click to expand...
Click to collapse
Thanks. I told her about it and she will give it a try, or just remove the pin altogether as a test. It is a weird issue. She is missing important calls from her elderly parents at night and it is rather frustrating. Turning wifi off also seems like a bad fix.