[Q] Droid X programming code? - General Questions and Answers

I have searched and searched for how to get to the programming menu for the DROID X.
We bought this phone from a guy that flashed it to Metro PCS and it worked perfect.
We want to use it for Metro as well. But for some reason the workers say they need a programming code for it because it's not one of their own phones. We tried telling the worker the model number because I guess sometimes you can get the code from the M#, but it didn't work. I have searched online that you can do ##PROGRAM and then send, then 000000, but the only screen we had was the "Touch the Droid to activate" and it has Emergency call and Change language at the bottom. We tried typing ##PROGRAM 000000 in the E. Call but it just tells us it's not an emergency number.
Since we've called the MetroPCS customer service, the first time, we couldn't get the ESN, because the MEID HEX isn't behind the battery, so that worker did us no good. Then we rebooted the phone and it actually came up past the "Click the Droid to activate" screen and we're actually at a home screen now, but with no service and etc. We talked to another worker and we got disconnected. The third worker supposedly set up our account and gave us a phone number but couldn't program because the model number wouldn't work. IDK.
All I want is the programming menu code, so they can fully activate the phone. I'm sorry if this is confusing, it was very confusing to us too!
Sorry this is so long, I thought maybe more details is better than too little details. Thanks for whoever replies.
Sara
EDIT:: Since we have been able to get to the homescreen somehow, I guess we could try doing ##PROGRAM on the normal dial pad, but my boyfriend has the phone so I will wait for him to come over. I also have seen that on some Droid X's the ##PROGRAM doesn't work and just dials the number because of some ROM. Will I have that problem since the phone is flashed over to Metro?

Droid X
I had same issue, if the phone is waiting for network program and you can't do anything but press a green droid then you can't enter ##program.. Once the phone is one with metro you can then enter the ##program and 000000 .. I just did that here.
Phone has to be activated before you can enter.. Is what I found.
hope I helped
wholesale - florida .com
Mark
MikeB89 said:
I have searched and searched for how to get to the programming menu for the DROID X.
We bought this phone from a guy that flashed it to Metro PCS and it worked perfect.
We want to use it for Metro as well. But for some reason the workers say they need a programming code for it because it's not one of their own phones. We tried telling the worker the model number because I guess sometimes you can get the code from the M#, but it didn't work. I have searched online that you can do ##PROGRAM and then send, then 000000, but the only screen we had was the "Touch the Droid to activate" and it has Emergency call and Change language at the bottom. We tried typing ##PROGRAM 000000 in the E. Call but it just tells us it's not an emergency number.
Since we've called the MetroPCS customer service, the first time, we couldn't get the ESN, because the MEID HEX isn't behind the battery, so that worker did us no good. Then we rebooted the phone and it actually came up past the "Click the Droid to activate" screen and we're actually at a home screen now, but with no service and etc. We talked to another worker and we got disconnected. The third worker supposedly set up our account and gave us a phone number but couldn't program because the model number wouldn't work. IDK.
All I want is the programming menu code, so they can fully activate the phone. I'm sorry if this is confusing, it was very confusing to us too!
Sorry this is so long, I thought maybe more details is better than too little details. Thanks for whoever replies.
Sara
EDIT:: Since we have been able to get to the homescreen somehow, I guess we could try doing ##PROGRAM on the normal dial pad, but my boyfriend has the phone so I will wait for him to come over. I also have seen that on some Droid X's the ##PROGRAM doesn't work and just dials the number because of some ROM. Will I have that problem since the phone is flashed over to Metro?
Click to expand...
Click to collapse

Related

Need help with apache phone number update

I have an apache witch I recently updated to wm6.1, after this I rang up to get it signed up to the telecom network. All went well until the next day I still hadn't been singed up. I rang up and they said I had to add my phone number into the device and they told me to type this into the dialer "##482243" then press the green phone key to get a type of popup. When I did it though nothing happened all it did was try to dial the code I had put in, could this be because I have updated my phone to wm6.1? Is there another code I could enter to get the same effect as the one telecom gave me?
Thanks a lot,
Aaron

[Q] Can send MMS but not SMS?

Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
SMS seems good on my end :/ maybe just an issue in your area?
slowz3r said:
SMS seems good on my end :/ maybe just an issue in your area?
Click to expand...
Click to collapse
Possibly, thanks for checking. I wish there was a way to manually enter a SMS service number in messaging settings like in previous android versions. I was thinking maybe for some reason my SIM card is too old, and suddenly decided to not be recognized properly. Looks like I'll be going to t-mobile tomorrow,
May wanna give them a call. going into a store they wont be able to help you
I've found that the primary merit to taking my phone to T-Mobile when it's messed up is so the guy behind the counter has to go through the list of things you already tried that the phone support agent is required to tell you to try again instead of having to do it myself. At least I can check out some cool phones and accessories while I wait. >.>
slowz3r said:
May wanna give them a call. going into a store they wont be able to help you
Click to expand...
Click to collapse
I spoke to a lovely Tmobile rep. She lead me through troubleshooting, except it was for Froyo, not gingerbread. When I brought this to her attention, and reminded her this was a nexus s, she connected me to samsung , and the call never went through.
Could a 5 year old SIM card magically stop working properly for SMS?
mprziv said:
I spoke to a lovely Tmobile rep. She lead me through troubleshooting, except it was for Froyo, not gingerbread. When I brought this to her attention, and reminded her this was a nexus s, she connected me to samsung , and the call never went through.
Could a 5 year old SIM card magically stop working properly for SMS?
Click to expand...
Click to collapse
honestly tell them you have an extremely old SIM and they will give u a free new one...if it deosnt help. then hell you got a free sim
Yeah. Unfortunately, since the Nexus S isn't supported by T-Mobile, giving you a new SIM card is about all they'll probably do, unless you're lucky and get a rep who's actually tech savvy.
zorak950 said:
Yeah. Unfortunately, since the Nexus S isn't supported by T-Mobile, giving you a new SIM card is about all they'll probably do, unless you're lucky and get a rep who's actually tech savvy.
Click to expand...
Click to collapse
The @Tmobile twitter is way handy and the reps who run that, are actual engineers so send them a tweet
This could be many things... does the Nexus S not have the ability to do the *#*#4636#*#*?
That is the code on every Android phone (save a very few POS) to get into the "engineering" menu. Select "phone" from that menu, then scroll to the bottom and bingo, SMS service center number entry... first hit refresh to see what is shows, if not correct delete, enter in the correct one, then update.
If the phone doesn't have the *#*#4636#*#* menu, not sure... perhaps your SIM doesn't have the SMS service center # saved to it anymore? New SIM would correct that, or putting your sim in an basic phone, then changing the service center # on that phone would put it back on the SIM.
Also, have you tried texting yourself to make sure it isn't a cross carrier issue? I know Verizon, for example, doesn't play very nicely with other carriers (actually all carriers prioritize in network traffic over cross carrier traffic, but Verizon seems to be especially bad in my experiences).
(FYI, I was looking through as I am thinking about getting a Nexus S and saw this thread, and couldn't help but toss in a word or two given I sell cell phones and have to deal with things like this all day).
mprziv said:
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
Click to expand...
Click to collapse
I have the exact same issue.Stock phone with Mobilicity. I don't know what their service number is.
Went in to T-mobile store today, got a new sim...everything is working properly now.
mprziv said:
Went in to T-mobile store today, got a new sim...everything is working properly now.
Click to expand...
Click to collapse
did you pay for it or was it free?
slowz3r said:
did you pay for it or was it free?
Click to expand...
Click to collapse
Since when has anyone ever charged for SIM cards?
zorak950 said:
Since when has anyone ever charged for SIM cards?
Click to expand...
Click to collapse
Last i checked its like 30 bucks to replace a SIM from tmo.
slowz3r said:
Last i checked its like 30 bucks to replace a SIM from tmo.
Click to expand...
Click to collapse
Huh. I've never known T-Mobile to charge to replace a SIM card that needed replacing, whether due to its being outdated or simply worn out. Maybe I just got lucky.
zorak950 said:
Huh. I've never known T-Mobile to charge to replace a SIM card that needed replacing, whether due to its being outdated or simply worn out. Maybe I just got lucky.
Click to expand...
Click to collapse
last i went was because i needed a replacement sim cuz my phone wouldnt pick up 3g and called a rep and said he put a note on my account so i can run into a store and get a free sim
SMSC Update Error - Solved
I had the same problem - but found a way to solve it without replacing sim.
What you need to do is to insert the sim into an older phone and update message central number from there.
I fixed it using a nokia 3210 - after having tried using an n95 with no success.
While trying to figure out what was wrong i tested with another sim also - and when reading out the SMSC from the *#*#info#*#*-menu i found that the number is stored in some strangely obfuscated way.
Here is how it stores number for two of norways major operators:
Netcom: +4792001000 - shows as 06917429000100
Telenor: +4790002100 - shows as 06917409001200
What the first 4 digits are for, i'm not sure, perhaps a code for '+' but whats interesting is the last 10 digits - they are basically swapped around in pairs of two.
I tried inputting the digits for the other central in this manner, and sure enough - it saved ok!
Hope this help someone
grab another phone and put your SIM card in it
then try to send a SMS
see if that works properly or not.
if that works, then it might be a SNS setting issues
if the SIM card does not send SMS on another phone, then you'll need to swap your SIM card with a new one.
I had the exact same problem just few weeks ago
mprziv said:
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
Click to expand...
Click to collapse
a one-phone solution from www google com tw/support/forum/p/Google+Mobile/thread?tid=078232a74455bbf0&hl=en
Code:
OK, I managed to fix this. I'll post the answer because this was buried deep and is a pain.
Answer is here:
http://forum.xda-developers.com/archive/index.php/t-926771.html
The relevant text is below. One thing I'd say is that the link is a bit vague on how to do the conversion. You need to put your SMSC number in the page, clear the rest of the info and press convert. You then need to ignore the numbers after 11.
For example, my vodafone +447785016005 goes to 0791447758100650110000910000AA00, which shortens to 079144775810065011. Go to the *#*#4636#*#* menu and put that in SMSC and hit update. Messages now send!!!. Hopefully I can save someone else the grief I've had all day...
"
to update the SMSC in android,
the number first need to be encoded
please use below url to encode the SMSC
http://www.twit88.com/home/utility/sms-pdu-encode-decode
for example, if your SMSC is number is +4531300000,
after encode, it is 0691541303000011
put this in the info page, and it will work.
"

[Q] Google Voice - Problems

Hello, This is my first post, I've done a lot of searching on here and google and am at my wits end with my google voice account and my new phone (Droid Charge).
It was working fine with my previous phone...and still does if i swap it to foward to it (Sprint - Blackberry Style).
I'm running PBJT kernel, and GummyCharged 1.7.5 - and did a wipe and cleared all of the options available to clear when flashing my rom.
Here is the problem: When I add my verizon droid charge's phone number into my google voice account it wants me to verify the phone. I hit call to verify but I never get the call. The only issue I could find on google voice help was people having problem entering the two digit code after the call comes through. That's not my problem. My call never comes through.
If I set it to another number, a different cell phone or land line...it rings and I can enter the 2 digit code, and it's working perfectly.
If I try to use the "add this phone" through google voice on my droid charge. It looks like it verifies because on the google.com/voice in the phones section it no longer says I need to verify. However, still having an issue because if you call the google voice number, it will not ring my verizon number (droid charge). It's worth noting that If I text it works. Just not the calls. Also if I leave a voicemail it will notify me on my phone as it should. The application works fine, etc. Just have never gotten it to ring my phone.
I'm about ready to have Verizon try and change my phone number, but wanted to ask here if anyone had any ideas to try. I honestly cannot remember if I tried to do it before rooting this phone, but my gut tells me I tried and it still didnt work. And yes, the checkbox to "forward calls to phone" is checked.
I've also tried from a friends google voice account seperate from mine. Tried to have them add my number, then when they need to do the verification step that calls the phone....of course...I never get the call.
Frustrating!
Thank you for any insight...
Is your GV number your primary number? If not you could also port your number over as an alternitave: google.com/support/voice/bin/answer.py?hl=en&answer=1065667
I know that there is an error saying my carrier is not supported when I try to setup my voicemail with the Charge, so I think it is either the phone or LTE. I had no problems setting it up when I used my Moto Droid, so I know Verizon works.
Since I'm already setup, I just ignore the error. That might not help you much, but like the suggestion porting your number will be your best bet. I hear switching back to a 3g phone temporarily will disable your sim card, and you'll have another headache on your hands.
Thanks for the replies. My sister actually has the same phone but stock etc etc. Going to have it forward to hers and see if that is a fix. I dont really want to have my google voice be my only number but I may do that porting if worse comes to worse.
Sent from my SCH-I510 using XDA App

[Q] Persistent Voicemail icon in Notification...

Hello all Xda'ers,
First of all, I am deaf and I was put on a special data plan that is customized for the hard of hearing and deaf subscribers. When I first got my NS4G, I got that voicemail icon as soon as I walked out of Sprint store. I should have went back to talk to the rep but I was late for work.
With that said, since May 8th, I still have that icon and I have been looking for solutions to remove it. I have searched this site as well as other sites for any remedies but with no avail. I do have Google Voice and have had GV set to use my current phone number so the voicemail can be ported over then I disabled GV after 20 minutes and the voicemail icon is STILL THERE!!!
I even tried Youmail and my heart jumped when it said I had one voicemail message and I was like YES! but then it was the youmail voicemail, probably greeting and congratulating me for installing youmail on my phone, because I saw what the message was and deleted it, but nope, VM icon is still there...
I have read somewhere, where you power down the phone, take the battery out for 30 seconds then put it back and power back on and it should be gone. Well, I did that and even waited 5 minutes and as soon as my homescreen came up, bam! voicemail icon appears. I told my Sprint rep that I can't remove it and he said something that struck me as odd. He said the NS4G has a visual voicemail and I should be able to remove it with no problem. I searched everywhere on the phone and couldn't find it. He said he got the same phone, even bought it right after selling me and my wife the phones. I emailed back and haven't heard from him since so...
I really don't want to put a ROM on this phone, probably because I have been putting it off since but other than putting a ROM on my phone, is there a solution to finally get that VM icon off?
Oh, to add, I have had my hearing friend call my voicemail for me, but he said that the automated response was something like, "This is no longer in service, the number you are trying to dial does not exist" or something like that, but he was NOT able to access my voicemail at all.
Sorry if this has been resolved elsewhere, but I had searched everywhere on this forum as well as all over the Internet as you can tell, it took me since May 8th to finally give up and post this on Xda, but why? You all are awesome!
I'm having this problem too ever since we got my wife the mytouch 4g slide. The CSR told me that I needed a new sim card. We put it in my NS and there is the icon.
I'm currently trying to put it back on T-Mobile voicemail service and calling my line from my work cell. It went to my GVoice so far so I guess I need to leave it for longer.
Pyro,
Since you are on Sprint I may have a solution. I also have this happen once in a while. After spending much time on the phone with Sprint here is their solution. Go to a land line phone and call your cell. Let it go to voice mail, give it a couple of minutes. Now on your cell go to your voice mail. You should have the message you left yourself. Listen to it all the way through and only press "7" to delete the message after the system prompts you to. After deleting the message hang up. The voice mail notification should disappear. This is a known Sprint problem, according to Sprint. If this doesn't work, take your phone to a Sprint repair center.
Good luck.
I just re-read your post. If your problem is the same as mine, you may have to have a hearing friend do this. I am not sure what Sprint may have installed on your phone to make it more usable for you.

[Q] HTC 8X caller ID issue

Hi,
I bought a T-Mobile HTC 8X in the US, unlocked it and brought it back with me to Israel. Now, when Israeli contacts call me, their numbers appear as (for example) 050 555 5555. When they text me, the number shows up as +97250 555 5555. For some reason the phone isn't able to tell that those two are the same number. I couldn't find anything while looking through the settings. I tried playing around with regions and all and came up with nothing. My old AT&T Focus had no issues and my dad's British 8S is working fine as well.
If I remember correctly, In WP7 deivces there's a registry setting which allows to control how many digits from the right identify the number as unique. However, I couldn't find a registry editor for the 8X (is there any?) so that information won't help me right now.
So now, my caller ID function sucks and the only way to actually ID contacts is to save 2 numbers for each one... really frustrating.
Does anyone know how to fix this?
Thanks!
Eyal
HTC support emailed back
And after sending them my IMEI they said that unfortunately there's nothing they can do and T-Mobile phones show that symptom in places like Israel and Europe.
So, it's either selling it on ebay or waiting for a registry editor or flashing it with a new ROM somehow. Option #1 seems like the most realistic one at the moment. This really sux.
Eyal
eyal453 said:
Hi,
I bought a T-Mobile HTC 8X in the US, unlocked it and brought it back with me to Israel. Now, when Israeli contacts call me, their numbers appear as (for example) 050 555 5555. When they text me, the number shows up as +97250 555 5555. For some reason the phone isn't able to tell that those two are the same number. I couldn't find anything while looking through the settings. I tried playing around with regions and all and came up with nothing. My old AT&T Focus had no issues and my dad's British 8S is working fine as well.
If I remember correctly, In WP7 deivces there's a registry setting which allows to control how many digits from the right identify the number as unique. However, I couldn't find a registry editor for the 8X (is there any?) so that information won't help me right now.
So now, my caller ID function sucks and the only way to actually ID contacts is to save 2 numbers for each one... really frustrating.
Does anyone know how to fix this?
Thanks!
Eyal
Click to expand...
Click to collapse
Actually, if I remember correctly from my previous experience with unlocked phones, most true Caller-ID (where the phone can identify who is calling even if they AREN'T in your Contacts list) requires XML code embedded in the phone (somewhere, don't ask me where) by the provider. Some providers use the same frameworks, so it's possible to get it working from network to network, but in most cases no.
I've never seen a situation tho, where it couldn't pick up the name from the Contacts list, based on the number coming in. I seem to remember you can turn on a feature called "International Dialing Help" that might bring them both together. OR put the entire phone number in your contacts. (As it is displayed when it comes in on Text).
drtolson said:
Actually, if I remember correctly from my previous experience with unlocked phones, most true Caller-ID (where the phone can identify who is calling even if they AREN'T in your Contacts list) requires XML code embedded in the phone (somewhere, don't ask me where) by the provider. Some providers use the same frameworks, so it's possible to get it working from network to network, but in most cases no.
I've never seen a situation tho, where it couldn't pick up the name from the Contacts list, based on the number coming in. I seem to remember you can turn on a feature called "International Dialing Help" that might bring them both together. OR put the entire phone number in your contacts. (As it is displayed when it comes in on Text).
Click to expand...
Click to collapse
I tried saving the entire number, but because local Israeli numbers get an extra "0" the phone is not able to ID them. Local call comes in as 050-5555555. SMS, like an intl. call, comes in as +97250-5555555. The "International Dialing Help" really helps when you're dialing. I thought it would fix the caller-id issue but it doesn't.
I spoke with HTC and with WP8 support on twitter. It's a known issue for T-mo phones and according to WP8 support, it has been forwarded to the appropriate team which probably means it'll be fixed in months to come. Until then, the only option is to get the phone flashed by one of the Israeli carriers with the Israeli version of the OS.

Categories

Resources