Related
Ok I have the AT&T Tilt obviously and I have been trying to get the operator names that I entered to show up. It still says AT&T on the "Home" Tab and on the "Wirless" tab. But when I set the phone to manually let me search for a tower and it shows the networks available it shows the names I have entered into the OperatorNames folder. Also when I change AT&T(310-410) to say sucks after restart it will swith back to AT&T in the registry. I also tried changing the registry HKLM\Software\OEM\PhoneSetting ONSDisplayRule to 0,1,2,3 originally it was on 4. and still no luck. Am I missing something. And yes I am positive the registry edits are done correctly(did it on the Cingular 8125). And no the phone is not unlocked. *Update* the operator names folder was there already with the registry AT&T(310-410) if deleted it still shows AT&T and returns upon restart. Maybe somebody knows something I don't or I just happen to have a lemon.
Nobody have anything, no idea, well has anyone else had a problem when changing there operator name and it keeps coming back, that could be a start???
Sounds like ATT is your operator. I don't think you can just change that.
Not trying to switch the "Operator" from AT&T to say T-Mobile, just trying to get the Name AT&T changed to say Cingular. But each time I change the registry 310-410 from AT&T to Cingular, it only shows Cingular in the Manual Selection box, but not on the Today Screen. So what I am saying is that it does work, but does NOT show different on the Today Screen. And Resets back to AT&T in the registry on soft-reset. There must be some edit somewhere in the registry to keep it from changing names on the today screen and change back on reset. The Personalizer cab worked, but what I am really looking for is the phone to show me which network I am using and not just AT&T all the time.
What I'm saying is I don't think you can do that.
Jay2TheRescue
Senior Member Join Date: Jan 2008
Location: Sterling, Virginia 20164
Posts: 412
--------------------------------------------------------------------------------
Quote:
Originally Posted by cmortensen
I thought the phone read the operator from the cell tower.
Yeah, but ATT/Cingular devices are setup to override that and show every network as ATT/Cingular. There is a setting in the phone to read the network name from the phone, or from the SIM, by default ATT phones read the network name from the SIM, and all of their SIM cards are programmed to show all networks as either ATT or Cingular for the older ones. Its not a big deal though, its just the network name. My unhacked phones all read AT&T, most of my hacked phones all read Cingular.
-Jay
__________________
HTC Tilt (Kaiser). Stock ROM upgraded to 1.62.502.0 minus bloatware, + many custom tweaks and apps.
Click to expand...
Click to collapse
Maybe Jay can shine some more light on it.
Yea that makes sense I kinda wondered that. Ok then maybe you might know a little bit more why I can take that same sim card and put it in my Cingular 8125 and yes it does say Cingular for the network, but it will also show, for instance in my area, iWireless when it does roam over.
Maybe that phone isn't as locked down as the tilt???
So there probably is a way it just hasn't been found.
So does unlocking the phone change anything?? Or what about non AT&T Tilt Kaiser's do they have the same issue?? Its obviously something that AT&T installs on the setup of the device and puts some settings in the boot registry to block it. Where does the "Home" tab get the Provider Name from because I can get the "Wireless" tab to change, but am unsuccessful on the Home tab unless you use the personalizer.
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
I was wondering if there was a way to use Market Access to get apps from the Verizon and Sprint Android Markets. I have a Captivate now and if it is possible, what steps should I take to get it. Thanks in advance.
thunder8671 said:
I was wondering if there was a way to use Market Access to get apps from the Verizon and Sprint Android Markets. I have a Captivate now and if it is possible, what steps should I take to get it. Thanks in advance.
Click to expand...
Click to collapse
+1 mee too. I hear Sprint has amazing NFL apps.
the Sprint Apps detect whether you are on their network or not.
The sim numeric for Verizon is 310012. Just change to this, and open the market. Remember to backup your current one, so you can put it back to normal when you're done.
argolfermd said:
The sim numeric for Verizon is 310012. Just change to this, and open the market. Remember to backup your current one, so you can put it back to normal when you're done.
Click to expand...
Click to collapse
Say we forgot to backup the current one, what is AT&T's numeric? I'm assuming it is the same for everyone's phone, so if someone could share that, I'd appreciate. If it isn't the case that AT&T uses a numeric that is the same for all devices, is the only solution to reset phone? What exactly does it mean to have my phone emulating a different numeric in the long run?
EDIT: I'll leave that question there for anyone else who ends up having it, but realized restarting phone (as long as you DON'T select "Emulate on boot") will reset the value for you. Anyways, I am curious to know if AT&T's numeric is the same for all phones (I don't see why it wouldn't be).
I use 310004 for verizon market so there most be more numbers per carrier .
Sent from my SAMSUNG-SGH-I897 using XDA App
shoeboxin said:
Say we forgot to backup the current one, what is AT&T's numeric? I'm assuming it is the same for everyone's phone, so if someone could share that, I'd appreciate. If it isn't the case that AT&T uses a numeric that is the same for all devices, is the only solution to reset phone? What exactly does it mean to have my phone emulating a different numeric in the long run?
EDIT: I'll leave that question there for anyone else who ends up having it, but realized restarting phone (as long as you DON'T select "Emulate on boot") will reset the value for you. Anyways, I am curious to know if AT&T's numeric is the same for all phones (I don't see why it wouldn't be).
Click to expand...
Click to collapse
The AT&T SIM numeric in Market Access is 310410.
To make a long story short, I recently purchased a used HTC Hero (sprint). After purchasing I played with the phone for a day or two to see what it can do (my first android phone, after being a Windows phone user) and in the process noticed that my esn was correct but my meid was all zeroes.
Now to skip thru all of the unnecessary stuff, I've been trying to change the meid back to what it should be, the number shown on the sticker below the battery. I've read every guide I can find on the internet. I've googled a hundred different times, I've done everything I can think of but I can't get qxdm to allow me to write the meid to the phone! After I zero out all esn locations, I attempt to write my meid. Everytime I get the same answer: Error response received from target.
Let me recap... I've tried downgrading the radio to stock (and tried other radios as well), downgrading to android 1.5, it's been rooted, I've scanned and scanned and scanned in cdma workshop to be sure I have all esn locations, with airplane mode on and off, I've done memory dumps then went thru them with a hex editor to be sure I haven't missed any esn locations, etc, etc.
After more than a week of trying to get this phone usable again, I don't know what to try next. I've reached the end of my known options with this phone, and could really use some help!!!
did you ever figure out the problem?
No, not yet. This seems to be a nearly dead topic around here, but hopefully someone can help me out.
I might have something that could work for you. Pm me if you want to give it a shot.
Locked & Loaded
""shooter on Deck""
budgreen did you send spc/msl before using the meid write command? example: spc 000000 (your msl/spc)
and please keep us updated if you get it fixed, hopefully between myself and laie1472 we can get you back up and running
message me if you need any more help
whoshotjr2006 said:
budgreen did you send spc/msl before using the meid write command? example: spc 000000 (your msl/spc)
and please keep us updated if you get it fixed, hopefully between myself and laie1472 we can get you back up and running
message me if you need any more help
Click to expand...
Click to collapse
Yep, I did all that every time. And still no go. But, exploring some other options...I DID manage to finally get it. Thanks to help from you and from Klown80. I appreciate it big time.
woot awesome enjoy your repaired hero
For just one post that a lot a stuff well anyways, one problem I see is that on the XT860 rom it doesn´t read the SIM ID but on the XT862 it does. Since in my stupidity something tells me that that maybe related to the fact that is not reading the sim properly, I guess I will go into that route to find out what´s happening.
Just a quick update for ya.
Just installed minimoto version of the XT860 into my XT862 and it worked, the only problem is that it says invalid sim, but interestingly I can receive and make calls, signal indicator works better also. Anyways, I will try to find out how to get the rom to detect the sim correctly later.
Click to expand...
Click to collapse
Re phrasing the question, is there a way to make an xt862 into an xt860, since they are technically the same phone, just with different radios. What I want is to maybe use the phone.apk from the xt860 (that is only gsm/utms) into the xt862, in that way the phone won´t be looking for CDMA settings.
Is that possible?
Click to expand...
Click to collapse
Hi guys, I already searched on google, on xda, on droidforums and I haven´t found a way to disable the Global mode and CDMA mode, because in my country we don´t use CDMA anymore just GSM (GSM with sim card).(since 1990 something, the whole country moved to GSM).
I want my Droid 3 to just have the option between 2G and 3G (that would be Edge and 3G here), the only option I need would be GSM/UMTS. the other 2 options are CDMA and Global and I want to get rid of them.
Also because for some reason in some areas if I am in 3G and I get a call, the call will drop after making some weird sounds and I will get no signal for some minutes, and I will have to manually go into airplane mode and then out to get a signal again.
So I think, since the phone has this global mode thing, I though what the hell, let´s just disable the global mode and cdma mode and that will fix it. I mean, I believe that the phone instead of falling back to gsm mode (from 3G in lower signal areas) it goes directly to global mode, or even CDMA.
For more info, my phone is a Droid 3 XT862, from Verizon, unlocked and brought overseas, using the latest minimoto rom (I wanted something light so minimoto looked good).
I already applied some build.prop fixes and they worked but the ultimate fix would be to disable global and cdma mode.
Is it possible?
Click to expand...
Click to collapse
XDADoog said:
For just one post that a lot a stuff well anyways, one problem I see is that on the XT860 rom it doesn´t read the SIM ID but on the XT862 it does. Since in my stupidity something tells me that that maybe related to the fact that is not reading the sim properly, I guess I will go into that route to find out what´s happening.
Just a quick update for ya.
Click to expand...
Click to collapse
I was wondering if this is possible too, I know there is a line in the build prop that sets gsm to default, but it seems that my droid 3 will change that setting once in a while.
I, too, would like a permanent fix for this.
I do not use Minimoto, but I do use the XT883 radio. I have zero idea how I did it, but my Stock rom (I use SS) does NOT have the network choice. I assume this is what you were aiming for. It only shows the GSM options (2g/3g/auto toggle, Operator select, and APNs menu) and nothing for CDMA. Effectively making my Stock rom GSM only like the XT860. SIM reads fine, calls/text/data all work, no invalid SIM reading anywhere.
I've attached a couple screenshots to showcase this (if it's what you want) and my modified build.prop (incase this is actually what caused it). I've no idea what I've done to the build.prop, I've gone through and randomly changed things in my adventure of doing GSM tweaks, and I mainly use Maverick so my main modifications (that I remember) are there. Use at your own risk, though I doubt it'll do any harm (remove the .txt from the end and make sure you have proper permissions). Remember to backup your originals.
Interestingly enough im having the opposite problem on my XT862. I flashed Minimoto 1.7 to it and I get the "Invalid SIM, 911 calls only" message. Which is weird since my phone works off of CDMA. Anyone else have a clue to remedy this?
I tried your build.prop on the stock ROM with the xt883 radio, but after setting permissions and rebooting, I still have the CDMA network options present, plus the occasional "switch to global" prompt.
--posted from my phone
Skreelink said:
I do not use Minimoto, but I do use the XT883 radio. I have zero idea how I did it, but my Stock rom (I use SS) does NOT have the network choice. I assume this is what you were aiming for. It only shows the GSM options (2g/3g/auto toggle, Operator select, and APNs menu) and nothing for CDMA. Effectively making my Stock rom GSM only like the XT860. SIM reads fine, calls/text/data all work, no invalid SIM reading anywhere.
I've attached a couple screenshots to showcase this (if it's what you want) and my modified build.prop (incase this is actually what caused it). I've no idea what I've done to the build.prop, I've gone through and randomly changed things in my adventure of doing GSM tweaks, and I mainly use Maverick so my main modifications (that I remember) are there. Use at your own risk, though I doubt it'll do any harm (remove the .txt from the end and make sure you have proper permissions). Remember to backup your originals.
Click to expand...
Click to collapse
I have the 862 with the 883 radio and occasionally my phone will lose the cdma/global options entirely but then after a reboot they willl randomly reappear. The first time this happened I thought it was great lol cuz I don't need them anyways but then the box that normally pops up if you lose gsm signal asking you to switch to global popped up but said "no cdma signal detected, switching to gsm/umts mode" which is exactly the opposite of what it normally says. Kinda weird and I have no idea what would cause it since I'm using the build.prop found in the diy thread with no other changes that I would assume many others are using.
Sent from my XT862 using xda app-developers app