Develop Bugs

X-VzW-MDN

Is there any reason that the reg. When sending a message does not see the correct number is in place?Or is there away to make the reg point that it is there?Thank You

My phone acts like the X-VzW-MDN is not even entered.I have been fighting this for days now.Reflashing roms and hard rest,following any tut I can find.I dunno what the deal is.I have even tried installing other Acrosoft builds.All my settings under WspHeader are correct.Have my mms options all correct.I am lost even if I flash a factory VZ rom still same error.I called them got new A-Key made sure my phone account was right talked to 3 techs or what VZ calls techs.This Originator Address error is pissing me off lol.I even went as far as to clear the NV ram and restore it from a old one I had,That I know mms worked on.Something seems werid.Any ideas would be nice I posted a thread on it here.
http://forum.xda-developers.com/showthread.php?t=541438
I was going to flash back to V12 but lost the rom boooo.LOL thanks for any help.BTW everything else works but mms.I dunno about gps I never use it anyway.
I have a sprint 6900 running V13 with radio 3.37 on Verizon
Sorry if people think this is a double post but I thought it might need its own thread.

I'm assuming you're trying to make your MMS's work? Assuming you are I have followed these instructions with success on the last several ROM flashes including NFSFAN Win6.5 V13. I have attached the Arcsoft cab that I used after having some problems with the one posted in the NFSFAN 6.5 thread. It could have been user error when I tried NFSFAN's Arcsoft cab, but I figure another option couldn't hurt.
MMS
1. Go to connection settings and select "Manage existing connections"
2. edit the only connection there
3. Name it whatever you want ie "vzw"
4. hit next and enter #777 as the number
5. hit next and put "[email protected]"
and "vzw" as the password
6. hit finish
7. install the attached arcsoft cab
8. do a soft reset.
9. open phmregedit in the start menu
10. navigate to HKLM\Software\Arcsoft\ArcsoftMMS UA\Config\mm1\WspHeader\X-VzW-MDN
and put your 10 digit phone number for the value
11. wait a min or two and do a soft reset
12. go into messaging select menu and then mms options
13. select the server tab
14. select verizon wireless and change connect via to "the internet",
the other settings should be correct.
15. wait a few min and perform a soft reset once more
16. now mms should work!!!
Every time I've done this procedure my phone number has already been in the X-VzW-MDN spot, but I have always reentered it just because. Also remember to wait a couple minutes before soft resetting after that step.
Edit: I just read your post in the 6.5 thread, this is the solution to your problem. Make sure you uninstall any previous Arcsoft cabs first, then soft reset and THEN follow these directions to the "T".

I have tried that over and over not tring to be rude.LOL I do not think its something I am doing but a stuck reg or something I dunno.Thank you tho I will try it again

OK so I bought a sprint 6900 off a friend switched a vaild esn to it.I have VZW service mms has worked until I flash V13 to it.I called VZW to make sure my account was provisioned right.and get a new A-Key after fighting this error for a few days.I have flashed I dunno how many roms and tried I dunno how many fixes and tuts.I have tried every cab for Acrsoft you can name.I know all info on the phone is correct due to the fact I have entered it in my sleep lol.I erased my NV ram and reinstalled it from a date I know my mms was working.My X-VzW-MDN is correct and connection setting is correct.I wondering if VZW has done something on there end to stop mms on there end after the fact which I dought.When my phone goes to send a mms the icon pops up and flashes a few times and then I get the error.I dunno what else to try being that I have reflashed a factory rom and cleared the NV ram a few time now.My latest setting are V13 on VZW with GC arsoft and followed the Cody bear tut to a T.Still nothing same ol error.My net works just fine and my settings for mms are right and my X-VzW-MDN are there.I am wondering if my phone is not picking u that it has the right phone number in the area.I have no clue as to what to try now.I thank everyone for the help.I am thinking about switching to a toucj pro so if anyone can pm me the full exe for cdma 3.0 or higher that would be great.

these phones suck, my mms will not work for the life of me, switching phones is your best bet these phones are headaches and they really are garbage

Gotroot said:
OK so I bought a sprint 6900 off a friend switched a vaild esn to it.I have VZW service mms has worked until I flash V13 to it.I called VZW to make sure my account was provisioned right.and get a new A-Key after fighting this error for a few days.I have flashed I dunno how many roms and tried I dunno how many fixes and tuts.I have tried every cab for Acrsoft you can name.I know all info on the phone is correct due to the fact I have entered it in my sleep lol.I erased my NV ram and reinstalled it from a date I know my mms was working.My X-VzW-MDN is correct and connection setting is correct.I wondering if VZW has done something on there end to stop mms on there end after the fact which I dought.When my phone goes to send a mms the icon pops up and flashes a few times and then I get the error.I dunno what else to try being that I have reflashed a factory rom and cleared the NV ram a few time now.My latest setting are V13 on VZW with GC arsoft and followed the Cody bear tut to a T.Still nothing same ol error.My net works just fine and my settings for mms are right and my X-VzW-MDN are there.I am wondering if my phone is not picking u that it has the right phone number in the area.I have no clue as to what to try now.I thank everyone for the help.I am thinking about switching to a toucj pro so if anyone can pm me the full exe for cdma 3.0 or higher that would be great.
Click to expand...
Click to collapse
That happen to me too, i could the not X-Vzw-MDN but what i found out that one of the arcsoft cabs has it and one does not so i switch from one cab to the other and the other and walla! i found it.Try getting a diff arcsoft cab.

I've also had to reinstall the same GC arcsoft twice to get the X-VZW-MDN to even show up.

it will not show up unless you wait a couple mins after installing and soft reset

i've never had a problem using the directions provided above. always sets MMS up properly.

is the White different then the Black?

I have a black Epic 4G Touch rooted and running EuroSkank just fine. I actually haven't experienced any issues besides video camera with effects causes FC. But I have a friend who has the white Epic 4G Touch and we rooted it, got a custom recovery and all went smooth. The second we put on the ROM on his phone he now is unable to make/Receive Calls and send/receive text/mms messages. Is there a color specific ROM? I tried flashing all sorts of ROMs to the device to fix it, but to no avail can I get it to work.

i have a white one and it works well with all kinds of custom roms. i believe they are the same.

feyerbrand said:
I have a black Epic 4G Touch rooted and running EuroSkank just fine. I actually haven't experienced any issues besides video camera with effects causes FC. But I have a friend who has the white Epic 4G Touch and we rooted it, got a custom recovery and all went smooth. The second we put on the ROM on his phone he now is unable to make/Receive Calls and send/receive text/mms messages. Is there a color specific ROM? I tried flashing all sorts of ROMs to the device to fix it, but to no avail can I get it to work.
Click to expand...
Click to collapse
White and black are essentiall the same phone.
Sounds like a network issue.
You could try a complete Stock+Root with an OTA build from sfhub http://forum.xda-developers.com/showthread.php?t=1721229 .
This should set everything right.
OR
You could try reseting the network settings. You'll need your MSL and a stock dialer.
Hands Free Activation/Network Reset:
Open dialer then ##72786# (factory reset on network settings)
Enter your MSL and hit OK
On the SCRTN screen select yes
Phone will auto reboot and take you to Hands Free Activation
If you have an SD card, media scanner will do its thing first.
Re-activation will initiate, let it run (DO NOT TOUCH THE SCREEN, no need to Press OK it will continue on its own)
Phone will then update Profile, then PRL, (you can select cancel when it searches for Firmware update if you want)
Phone will reboot again.
To get you MSL (if you're rooted)
1. Download "Terminal Emulator" from the app market.
2. Open Terminal Emulator.
3. type in getprop ril.MSL (make sure the .MSL is capitalized)
4. Press enter and poof, you have your MSL
Good luck

alright I found the problem. It wasn't the ROM at all, it wasn't the RIL, it wasn't anything to do with the custom ROM. It was actually his line that was having problems with the switch. We got it all figured out and the phone works great now. Thank you for your responses on getting it back up and working. We put a test line on the phone and it called just fine, so we found the issue was actually on his number. Phone fixed, and we are rocking the custom Jelly Bean again. Thank you everyone!

feyerbrand said:
alright I found the problem. It wasn't the ROM at all, it wasn't the RIL, it wasn't anything to do with the custom ROM. It was actually his line that was having problems with the switch. We got it all figured out and the phone works great now. Thank you for your responses on getting it back up and working. We put a test line on the phone and it called just fine, so we found the issue was actually on his number. Phone fixed, and we are rocking the custom Jelly Bean again. Thank you everyone!
Click to expand...
Click to collapse
Thanks for posting back the resolution. It always helps the community when we know what happened.

[Q] GT-N5110 Wifi not working after OTA upgrade to Kitkat 4.4.2

I have upgraded from Jelly Beans to Kitkat 4.4.2 via regular OTA upgrade provided by Samsung on my Samsung Note 8" GT-N5110. Since then I am unable to use Wifi on it. My device is NOT rooted and is running on original Samsung software upgraded via OTA.
I have tried to clear cache and then factory re-set as well and still can't get the WIFI button to sometime even select available WIFI networks. So issues I am facing are summarized below"
1. After factory re-set and clearing cache via Power+Vol Up option, when I tried to setup from scratch, WIFI would not turn on at all meaning device would not be able to scan for available WIFI network or would do so but after long time and if it does show available Networks and I select my home network with required security (WPA2) and password, it would show status as " Saved" rather than connecting to this network. The device would not connect to selected network even after multiple tries.
2. When trying to turn wifi on, device would not show "WIFI" button to Green but instead would stuck at "Grey" color for ever unless rebooted and re-tried many times. The grey would turn green when selecting advanced option or tabbing thro' back button but would not scan available networks then. If it would scan thro' Networks, it would just save selected network even with correct security option and password for it.
WIFI not turning on has made this device a piece of junk for any meaningful use. Any suggestions/ help would be highly appreciated. Again please note, my device is UNROOTED and running on original firmware provided by Samsung via OTA upgrade.

Hi XDA Gurus,
Any one can direct me to right section that has solution for this issue if it is a repost? or help me get an answer?
Thanks,
R

Anyone find an answer to this?
I ahve had no luck, same exact issue, anyone have any ideas? thanks

shahrit said:
I have upgraded from Jelly Beans to Kitkat 4.4.2 via regular OTA upgrade provided by Samsung on my Samsung Note 8" GT-N5110. Since then I am unable to use Wifi on it. My device is NOT rooted and is running on original Samsung software upgraded via OTA.
I have tried to clear cache and then factory re-set as well and still can't get the WIFI button to sometime even select available WIFI networks. So issues I am facing are summarized below"
1. After factory re-set and clearing cache via Power+Vol Up option, when I tried to setup from scratch, WIFI would not turn on at all meaning device would not be able to scan for available WIFI network or would do so but after long time and if it does show available Networks and I select my home network with required security (WPA2) and password, it would show status as " Saved" rather than connecting to this network. The device would not connect to selected network even after multiple tries.
2. When trying to turn wifi on, device would not show "WIFI" button to Green but instead would stuck at "Grey" color for ever unless rebooted and re-tried many times. The grey would turn green when selecting advanced option or tabbing thro' back button but would not scan available networks then. If it would scan thro' Networks, it would just save selected network even with correct security option and password for it.
WIFI not turning on has made this device a piece of junk for any meaningful use. Any suggestions/ help would be highly appreciated. Again please note, my device is UNROOTED and running on original firmware provided by Samsung via OTA upgrade.
Click to expand...
Click to collapse
If you don't mind... try odin 3.09, flash philz recovery, factory reset for wipe clean for fresh install option, and boot to downloader. Flash a firmware from sam mobile, or the get a usa version in the development section.
That should flash a clean install after a wipe

Cannot SEND SMS Tried Everything Please HELP :(

All of a sudden today I cannot send SMS.
I was on a really old build of Cyanogenmod12 (April 22nd I believe) as any time I tried to update to newer Nightly builds I lost all Sprint service could not make/receive calls or texts, etc.
I decided I was pretty fed up with CM12 so I decided to go ahead and migrate to AICP. I wiped everything TWICE in recovery, loaded up AICP and it works fine, I get LTE signal, etc. However I cannot SEND SMS, I can RECEIVE SMS I just cannot SEND. I had done some data restores with Titanium and I figured that somehow some way that might be messing with things. So I did another 100% fresh install after wiping everything.... I can send/receive calls, receive SMS but I cannot SEND SMS
I am really at a loss here guys, ANY help would be greatly appreciated

*#*#4636*#*# change it to CDMA wait 30 seconds send an SMS and do *#*#4636*#*# again change it back to late/CDMA n should be ok
Sent from my SM-N910P using XDA Premium HD app

pbedard said:
*#*#4636*#*# change it to CDMA wait 30 seconds send an SMS and do *#*#4636*#*# again change it back to late/CDMA n should be ok
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I stayed up all night last night working on this, let me update the thread with what I have done so far.
I was looking at some stockish ROMs and I noticed that there were warnings on some of them stating that you needed to have the Sprint OTA 5.0 update installed prior to flashing, which I actually never got. My phone came out of the box with Kit Kat and I never installed the 5.0 update, I went straight to CM12 5.0 instead. So I had a theory that there might possibly have been some sort of network data profile, etc or something out of that official 5.0 OTA that I never got that was somehow causing me problems. I decided to revert back to complete bone stock.
I wiped everything and flashed the N910PVPU1BOB7 file (MD5 = 7304e42cf0e241553d8db9e3c3eeed81) which was the official Sprint 5.0 OTA. Loaded it up, updated the PRL, Network Data Profile, etc, etc, etc.... everything works (relatively speaking...... TouchWiz sux balls of course). I have LTE signal, I can send/receive calls, I can send/receive SMS... all good.
So at this point I decided to re-wipe and flash AICP, with the emotion Kernel (latest builds on all). Load it up.... same problem as before. I have LTE signal (stronger than on the stock Sprint ROM), I can send/receive calls, I can receive SMS but I still CANNOT SEND SMS
I tried a few things at this point. I tried to manually reset the Sprint network connection on the phone by dialing ##72786#, this did not work, it returned an error "incorrect MIM code". I tried the *#*#4636*#*# that I have seen suggested in multiple places, this also did nothing, it returned an error "incorrect MIM code". I also noticed on the "mobile networks" tab, and this is true for BOTH CM12 and AICP, that it has the setting at "Global" by default and everything works with exception of sending SMS. Now when I click that tab it only has 3 options LTE, 3g, 2g.... for some reason "global" is not an option, neither is CDMA. Whenever I select LTE it automatically drops me from the Sprint network PERMANENTLY until the ROM is re-flashed there is no way to reverse this. I cannot even dial the manual programming codes "*#* etc" as it just simply says "no network service". If I try to automatically connect to the sprint network through the network operators tab it does in fact find Sprint as my provider, however if I click on Sprint to connect it processes for about 2-3 minutes and then simply returns an error of "cannot connect to the network at this time, please try again later". Again the only way to reverse this is to re-wipe and re-flash again which puts it into the unselectable "global" network setting by default where then I will have LTE signal, I can send/receive calls, and can receive SMS but not send SMS.
So that is where I am at, I stayed up all night last night wiping, flashing, and testing different things over and over. Nothing seems to work 100%, except the stock 5.0.1 OTA which is what I am on now. I really hate TouchWiz and for some reason I get a much weaker LTE signal on stock compared to either CM12 or AICP (I have no clue why this is). I am really at a loss here why everything works on the custom ROMs except for sending SMS..... willing to try almost anything to go back to a custom ROM.
Let me know if you guys have any other ideas.

Well great news I have finally resolved the SMS send issue
pbedard said:
*#*#4636*#*#
Click to expand...
Click to collapse
pbedard had tried to help me with the above post (which I appreciate, thank you), and I have seen the same advice in other threads. One slight problem though, he slightly mistyped the manual programming code it is actually *#*#4636#*#* not *#*#4636*#*# which I had tried entering ohhhhh I dont know 30 times? :silly: And it always returned an "invalid MMI code".
I had tried everything and after spending a full day on TouchWiz I was determined to fix the issue so I could go back to a custom ROM. I was even manually creating and deleting APNs, etc. Nothing would work. Right as I was about to finally give up (after literally 12hrs of researching the issue and testing fixes) I was reading the official CM 12 thread and came across the "fixes" post:
http://forum.xda-developers.com/showpost.php?p=57613217&postcount=3
Because I had tried entering the manual programming code so many times I happened to notice that the last 4 key strokes were not what I had been entering. I entered the correct programming code, boom the Phone Info menu pops right up I follow the directions and what do you know send SMS finally works .... wow what a relief, I am on the latest AICP release on the emotion Kernel and everything works like a charm.
Also by setting the phone to LTE/CDMA through the manual programming menu I have the strongest LTE signal by far, full 100% bars at all times (I live right next to a Sprint tower). I have never understood why I only got 1-2 bars on the stock ROM and 3-4bars on CM12/AICP through the default settings. Anyway thanks for help and I will list out exactly what I did to get it working.
- 100% Stock ROM
- CF Auto Root and TWRP install through Odin
- Reboot to recovery
- Wipe Dalvik cache, system , data, and cache
- Reboot to recovery
- Flash emotion kernel (optional)
- Flash latest AICP build (or custom ROM of your choice)
- Flash latest stock Gapps
- Reboot system
- Confirm Google Messenger is the default SMS app (it will already be if you flashed 5.1 stock Gapps)
- Dial *#*#4636#*#* ("Testing" menu screen will pop up, select "Phone Information")
- Scroll down to "Set preferred network type" click it and scroll up and set it to "CDMA auto (PRL)"
- Wait until 3G signal comes online (takes about 10 seconds)
- Change "preferred network type" to " LTE/CDMA auto (PRL)"
- It should take another 10 seconds for LTE signal to come online and you should be good to go to send and receive SMS ! :good:

Android 12 update causes the System UI to constantly reload - can't use phone

After applying the Android 12 OTA upgrade today, I can boot into the phone, however it looks like the System UI is constantly stuck instantly crashing upon launch, then reloading. the wallpaper is flickering on and off. I can take calls (and reboot the phone) just about, but I can't open any menu aside from the Power menu, or anything like that. Does anyone have any ideas how to resolve this? I'd try and enable adb mode or something like that but I can't beacuse I can't open any menu. I managed to boot into safe mode, but that had no effect and the problems are still happening.
Sometimes I can get it to briefly show the system icons, but it disappears too quickly for me to be able to do anything. If I was able to open the settings app, i'd be able to put it in USB file transfer mode to get my stuff of it, but I can't even do that.
Using the LG_UP tool, I can downgrade to the previous firmware, however I can't do anything as it then won't accept my encryption pin code. If flash the (broken) latest firmware back on, I can decrypt the phone, but I'm back where I was again where the system UI app just instantly crashes.
Right, so I think it's related to the lock screen. I was able to (somehow) manage to get it to the home screen from where I could open the settings app up and everything was fine, and was able to turn on USB file transfer mode. However as soon as the phone locked again, it stopped working. But it's very wierd.

You could try to do a factory reset. I think you have to start the device while holding one of the two power keys.

Ahkah said:
You could try to do a factory reset. I think you have to start the device while holding one of the two power keys.
Click to expand...
Click to collapse
I think that would work, but i'm trying to avoid doing that as there's still stuff i'd like to get off of it. Maybe a future firmware update may fix this bug.

Most probably there will be no further update. Do you have a chance to take a look at the system protocol via "adb logcat" during the crash? Typically the notorious "com.android.systemui" is the culprit.
PS: In fact it does not matter, but is your device some 820 (G8) or the downgraded version 810 (G8s)?

bergqvistjl said:
I think that would work, but i'm trying to avoid doing that as there's still stuff i'd like to get off of it. Maybe a future firmware update may fix this bug.
Click to expand...
Click to collapse
If you do decide to factory reset, please let us know if it resolved your issue.

idk which g8 you have but my g8 from xfinity just a few hours ago got the ao 12 v40a update and it did the saame thing the bottom screen buttons (home, back, etc ) flashed on n off crazily,
once i figured out the specific recovery mode combo and performed data wipe reset etc
it has seemed to of fixed it, phone calls and messaging are operational are what ive so far checked asa working phone out not recieved any incoming calls yet but messaging works
lmg820qm5
ao12 v40a
on metro pcs service

Ahkah said:
Most probably there will be no further update. Do you have a chance to take a look at the system protocol via "adb logcat" during the crash? Typically the notorious "com.android.systemui" is the culprit.
PS: In fact it does not matter, but is your device some 820 (G8) or the downgraded version 810 (G8s)?
Click to expand...
Click to collapse
It's the G8S. And I didn't have debug mode enabled, so adb doesn't work.

jtkc said:
idk which g8 you have but my g8 from xfinity just a few hours ago got the ao 12 v40a update and it did the saame thing the bottom screen buttons (home, back, etc ) flashed on n off crazily,
once i figured out the specific recovery mode combo and performed data wipe reset etc
it has seemed to of fixed it, phone calls and messaging are operational are what ive so far checked asa working phone out not recieved any incoming calls yet but messaging works
lmg820qm5
ao12 v40a
on metro pcs service
Click to expand...
Click to collapse
Yes, i'm pretty confident if I did a factory reset, it would work fine, but I really don't want to do that until i've got all my stuff off it.

i hear ya, understood, i just thought id fyi,
that the reset, as undesireable as it is. has appeared to fix the issue and phone, is as far as i can determine fully operational . the finger print reader, phone calls, and messaging all work
i just got the phone fixed less than an hour ago, after installing the 40a update a lil before noon or 2 hours ago lol