Sorry for the noob question, but i have looked everywhere and could not find an answer.
So yesterday I install nueSPL 2.47, on my Verizon XV6800 and then flashed to Radio 3.42.50 and then flashed to DCD Rom 3.2.6. I had some problems with authentication, so I called Verizon and they couldn't fix the problem at night because the system was down but they were able to fix things the next morning. Not sure what they did because they didn't give me a new A-Key over the phone.
So after that I was able to place calls out. I then downloaded the Verizon cab and was able to connect to the internet. I am also able to send and receive txt messages, but I can not receive phone calls. Now strangely after ending a call, I did receive one phone call but that was it. The rest of the time anyone calls it only rings on their end and then goes to voice mail. Then a few seconds later I will get a notification that I have a voicemail.
So since all this happened I have reflashed the dcd rom and reloaded the carrier cab. and called both *228 -1 and *228 -2. I still can call out, use gps, internet, and txt, but not get any calls. Any one have any ideas? Any help is greatly appreciated.
Thanks in advance.
that very interesting... I recently upgraded my father in law's phone and also experianed the same thing.
Also interesting, when I did the upgrade to my phone a few months ago I had to get an a key.. I also had to get one once after a hard reset. Perhaps they fixed something for this.
Keep calling VZW not all techs know what there talking about, eventuality you will run into one that know exactly how to fix your problem.
Related
Okay, so I've never posted here before.. I've only lurked enough to figure out how to install a WM6 ROM on my phone.
I've been having a lot of problems with my Hermes lately (can't make/receive calls, sim missing, text messages not sending or receiving)... I have not figured out if it's from dropping it too much or if it's because I'd been running a WM6 rom on it. So I decided on Saturday to switch to another version of the WM6 ROM's available around here...
I installed 3DES.3 and so far I've been having more and more issues as far as making and receiving phone calls.
So the issue is that with the slider closed I'd go to the phone screen and then t9 in a user's name and then call them. The call would not connect... I kept trying and normally wouldn't notice the number it's trying to dial, but the phone is trying to dial a 107140 in front of every call made through the t9 dial menu.
Is anyone else experiencing this? Is the ROM trying to make long distance calls on our behalf? Should it be taken off the website?
Thanks guys,
Mitchel
mitcheloc said:
Okay, so I've never posted here before.. I've only lurked enough to figure out how to install a WM6 ROM on my phone.
I've been having a lot of problems with my Hermes lately (can't make/receive calls, sim missing, text messages not sending or receiving)... I have not figured out if it's from dropping it too much or if it's because I'd been running a WM6 rom on it. So I decided on Saturday to switch to another version of the WM6 ROM's available around here...
I installed 3DES.3 and so far I've been having more and more issues as far as making and receiving phone calls.
So the issue is that with the slider closed I'd go to the phone screen and then t9 in a user's name and then call them. The call would not connect... I kept trying and normally wouldn't notice the number it's trying to dial, but the phone is trying to dial a 107140 in front of every call made through the t9 dial menu.
Is anyone else experiencing this? Is the ROM trying to make long distance calls on our behalf? Should it be taken off the website?
Thanks guys,
Mitchel
Click to expand...
Click to collapse
the ROM you are talking about isnt exploited to my knowledge... but it is old and i think 3DES has stopped supporting it...
you are also in the wrong Forum... you should have posted in Hermes Windows Mobile 6... download this ROM and try it...
Thanks for the fast reply. I'll switch over to that ROM. Something is definitely up with this ROM though.
Thanks again,
Mitchel
First of all, let me tell you that I DID install the verizon cab
And second thing I should say is I am getting an internet connection, and from the message I am getting when I try to make a call, I would say something is not allowing verizon to authenticate my phone.
I have dialed *228, option 1 to program my phone and it said it is doing that, and then it does a soft reset, but i still can't make a call. Do i need to call verizon or something? ....I appologize for the post but i searched and i feel like i'm missing something simple. Thanks in advance!
Did you run the "Carrier .CAB"?
Never Mind
Found this thread which explained basically i did need to call VZW...
http://forum.xda-developers.com/showthread.php?t=376142&highlight=make+calls
Is it just me or is anyone experiencing a "Forbidden" error when sending/receiving MMS after updating to AT&T's new ROM with 1.14.25.35 Radio?
I've reflashed the updated AT&T ROM and then flashed NRG's latest 6.5 ROM with the correct Rilphone.dll and still have the Error. I even tried sending from the new stock ROM and got the error. I did this multiple times to make sure it wasn't a bad flash and still have the "Forbidden" error. Did I do something wrong when I flashed the new ROM and Radio? The settings in MMS are correct and I didn't load anything else prior to testing MMS.
At first I thought it was AT&T and wasted over 30 minutes with a rep that knew next to nothing. Then it dawned on me that this all started after I updated to the new ROM/Radio release for AT&T on HTC's website. So, I reverted back to the original shipped ROM with 1.02.25.32 Radio, flashed NRG's latest 6.5 ROM and can now send/receive MMS.
I had the same forbidden error and had to talk to tech support from att.. apparently it's because i had placed my sim into an iphone and we all know iphones can't send mms so it registered into their system that i was using an iphone thereby causing the iphones imei to register to my number hence why it's forbidden to send/receive a mms. did you perhaps do something similar?
ATT0001 file can't open it
Hey Guys... sorry than I can't help to solve your problem.. But i have a problem too with the MMS... what happens is that every time I send or receive a mms to a windows mobile phone comes as ATT0001 file and I can not open .. I need help with this thanks
Loner2DEnd: I did but only to unlock one. I've done this before and have never had that problem up. I only noticed that I wasn't able to send/receive MMS after I had the official update from HTC for the FUZE. I was on the phone with the tech and they told me that using my SIM in an iPhone wouldn't have updated my account. You can log onto your online account with AT&T and see what phone/IMEI is registered with your account. Mine still has my FUZE and correct IMEI. Everything is working now that I reflashed the original shipped ROM with the 1.02.25.32 Radio.
I downloaded another copy of the ROM update from HTC for the FUZE and ran the same tests to see if maybe it was a corrupted file/bad flash and I still had the same issues with MMS. My internet still worked but I got the same Forbidden Error. For now, I'm going to just stay with my current (original shipped) Radio since everything's working.
Dannyedilber: I'm not familiar with that Error. Sorry man. I don't know much about MMS and had to do some homework and some trial and error to finally find this solution. Maybe one of the seniors can answer your question.
I've had this problem a few times but usually fixes itself after a reset or a quick disconnect/reconnect of the radio.
I find that if I leave my data on for an extended period of time, it seems to happen. Almost like AT&T is seeing the high traffic and cutting me off.
Also check to make sure you guys don't have Data disabled in your accounts.
@Dannyedilber: I don't even know what an "ATT0001" file is?
@Loner2DEnd: My wife just returned her iPhone because she said it sucks compared to Windows Mobile (smart girl eh?) and went back to her old Samsung Blackjack. We did this yesterday, after her having the iPhone for a little under 30 days. I just sent her a picture and she got it.
From AT&T
The data network works for all of our devices and the Windows Mobile devices are the only ones that seem to have had some issues with the way the data network is configured. Rather than trying to re-configure and potentially break the network for other users, we have been working on a fix for the Windows Mobile issue. We have a fix that will be implemented by the end of this quarter and we should have the problem resolved at that time.
Click to expand...
Click to collapse
From AT&T
Just wanted to let you know that I did get an update. The project to "fix" the 403 error is moving forward. Right now we plan to have the implementation complete in June with Project closure in Early July. I will follow up again in about a month to see the status and provide closure information.
Just for clarification: This project hasn't slipped a month, we keep the project open during a "soak" period to ensure that everything is going as expected. Also, as we apply the fix to the elements in the network the fix will be applied to certain markets and complaints should drop for that market dramatically. I haven't seen this issue in a while here so I believe that the patch has been applied for the Minneapolis market.
Click to expand...
Click to collapse
An easy temporary fix is to put your phone into flight mode and then take it out. A new data connection almost always works. Worst case scenario soft reset the phone.
so its by market then?
I flashed the new rom about last week, had no issues receiving and sending MMS on it and on NATF's 4.7 rom.
Still No MMS
nmbr6 said:
...An easy temporary fix is to put your phone into flight mode and then take it out. A new data connection almost always works. Worst case scenario soft reset the phone.
Click to expand...
Click to collapse
My MMS is not working incoming or outgoing. I have tried it from TF3D2, Titanium, after reset, after airplane mode and reset with no success. I put my SIM card in my backup phone and MMS send and receive worked flawlessly. I do not get the forbidden error message some of you have gotten; it just does not work. I have reset the RegEdit keys several times and they are currently set at 1.2mb. I know that 6oo K is at&t max, but the two test MMS messages are 77K and 317k. Thanks - David.
Black C5 said:
My MMS is not working incoming or outgoing. I have tried it from TF3D2, Titanium, after reset, after airplane mode and reset with no success. I put my SIM card in my backup phone and MMS send and receive worked flawlessly. I do not get the forbidden error message some of you have gotten; it just does not work. I have reset the RegEdit keys several times and they are currently set at 1.2mb. I know that 6oo K is at&t max, but the two test MMS messages are 77K and 317k. Thanks - David.
Click to expand...
Click to collapse
It sounds like you have a different issue altogether. My posts were answers from AT&T strictly for the 403 forbidden issue.
Player911 sorry that I was not very specific...whats happening is when I send a ATT MMS to someone who have a HTC touch pro to her hotmail account.. she can't open it because the picture come as ATT0001.. even when I send att MMS to myself at my email account I receive as a ATT0001
Need help with this guys.. please
Sorry my english
Hi All:
First off thank you for the info in resolving this issue. Since swithing back to the original shipped ROM with radio 1.02.25.32 then flashing EnergyROM 3.0 Phoenix 6/12, I've had no problems with MMS Forbidden Error. It's been a week now and I've had no data/network issues either. I'll try again with the new Radio/ROM this weekend when I have some free time and will report back. Thanks everyone!
Tru using a registry editor and go in and change the registry in Arcsoft under HKLM>Software>Arcsoft>Arcsoft MMS UA>Config>MM1>MMSCSetting>SampleMMSC>Wap1SendDefault and Wap2SendDefault and change to a desired number. For instance, I have 102400 set to send up to 1MB.
See if that allows you to send.
try enabling ATT's proxy. This always works for me.
1. Enable the proxy
2. Kill the data connection
3. Reconnect data
4. Try sending or receiving.
This has worked countless times for me.
I usually find solutions to my own problems while lurking, but this one is stumping me.
Starting last night at some point I stopped being able to receive both calls and texts. I was quite confused because I was in the middle of a text conversation with someone and they just stopped responding.
Data still works and I can make calls and send texts, but when I send myself a text from another phone nothing happens and calls just go to voicemail.
The phone was on the Eugene 2E JK2 Froyo ROM. I re-flashed it, then flashed it back to stock and nothing helps. When data is off it still doesn't work.
Any ideas? I tried searching but couldn't find anything. My GoogleFu may be lacking
Weird, have you contacted t-mobile support? Many years ago on ATT, with an old school flip phone, I had a similar problem. One night, my phone just suddenly stopped being able to receive or make calls. It could only text. The only solution was to get a replacement--it was not software related.
I've got a new phone on the way because I've been experiencing a similar thing, off and on for the last few days. I called T-mo and went through all the troubleshooting but they can't find any reason for the phone to be behaving this way...gonna send me a new one as warranty replacement.
I followed Bentenrai's guide to S-Off, Rooting, and Recovery. Internet (both Wi-Fi and 3G/4G data) works, but I am unable to make/receive phone calls or send/receive text messages.
The phone call error occurs after about 2 rings, which says "Error 16 (then in Spanish) Switch 694".
The sms error is: "sms error radio interface resource shortage" with details "cause code:64, error class: 2".
I tried everything from the "Phone does not work after S-Off" thread and was on the phone with 2 Sprint operators for over an hour. The first operator had me update profile and PRL, then had me turn off/pull battery while she did stuff twice to no avail. The second operator (who was mean and treated me like a moron) had me turn mobile networks off and on again, update profile and PRL, and pull battery (yes, she actually wanted me to pull the battery while the device was on; I powered it off first).
Is anyone else experiencing this or has anyone found a solution?
Thank you very much!
Yup, I found the fix. It's really easy! Tell the person to do a "CHLS Refresh", and then restart your phone.
http://forum.xda-developers.com/showthread.php?t=1194460
Thanks! I also just saw the thread in the General section about all the lucky people who achieved S-Off without the error.
I'll call them back tomorrow and report back.
i had the same error after rooting my phone, just try to call any number, and after listen to the message, it will connect you to a sprint rep. they will confirm some information with you and they will tell you that they will reset from their side and ask to turn off the phone for 30 sec and boom, it's a go.
After some thought, I realized both Sprint reps only had me pull the battery for a few seconds. I decided to leave the battery out for about 5 minutes and when I powered back on, I was able to connect to voicemail. I let it stay connected for a bit and then was able to make phone calls and texts. Suddenly, I began receiving Error 67 messages, so I updated profile and PRL. Since then, (knock on wood) everything has been ok. Phew!
Forgot to mention this tidbit of wisdom from the 2nd Sprint rep: She told me my problems with making calls was because there's an outage in my area. I told her that wasn't likely because I was using another Sprint phone to talk to her. She still persisted in saying it was an outage. Yay!
That's it? no other responses to this. My sons phone is a paper weight at the moment. He can't even dial Sprint and nothing else has worked. Anyone have another idea?