I was wondering if anyone else has seen this behavior.
The phones appeared to have the original VZW roms on them but I admit I didn't look as closely as I should have and write down the numbers.
I've two warranty replaced phones that work this way.
1. Flash olipro&latest radio & latest (4.1) DCD rom
2. *228 (succesfully)
(Thinking back, the first time I did this I *228ed before applying the carrier rom)
3. After that calls cannot be made EVERY call even *228 results in a roaming "call lost"
I can flash back the original signed VZW rom that was posted here a while back and restore phone operations.
The *228 update then worked but could not check messages. The switch to non-broadband phone and back to the titan got me able to check voicemail successfully. I've redone the cycle but after applying the DCD rom, it doesn't take me back to a phone needs initial programming state. I'm gonna try to go full circle a third time now and see if I missed anything when it was 2am.
*ADDITIONAL: I just realized that when power is hit or the phone battery saves to power off, it locks up. Even though the lights still blink.
Do you have any thoughts? Have you seen this before?
I'm tempted to install the latest from HTC, but I don't want to give up on GPS - or has it the recovery from that been proven now?
Status update!
I had also noticed that there was a 2mo newer carrier cab from DCD. That didn't help.
At this point I've up/down/crossgraded to MR2 successfully.
This resolved the lockup problem.
I am in the process of following this thread to resolve the GPS issues. Hopefully the new roms will work with this radio http://forum.xda-developers.com/showthread.php?t=481750
A work around
Ok I went through that whole process to no avail.
However, I found a solution that I REALLY dislike and you will too once I tell you what it is.
It seemed pretty obvious that vzw somehow flagged the phone during the upgrade process to disable it. This was perhaps because I hadn't loaded the carrier cab when I updated, though I've done that before on earlier without any lasting effect.
**** NOTE *****
I strongly discourage you from taking the steps I have done below. Done incorrectly, you are committing a prosecutable crime with jail time involved.
**** NOTE *****
Knowing calls were blocked and that I would have a chance to hit hangup before the call was actually placed (that's why it beeps) I dialed 911 hit send and hit hangup. Obviously the call did not even start because the phone was in lock down mode (I haven't mentioned this before but the phone always booted to the extended network.) when the call was attempted. However, Verizon is also obligated to process all 911 calls. So, it switched from extended, to roaming, to Verizon. The call had been canceled even before it got to roaming, so there was no contact with emergency services. The upside is that the phone is now on the Verizon Network with the new radio and new ROM. I can do everything except a *228. This includes checking voicemail, #768, rebooting etc. I've not tried a hard reset, nor do I think I will.
I REALLY don't like the method, but I have my phone back.
I'm traveling to TX next week for SxSW again. I may see if I can do a *228 from there and get a better result.
Related
It left all kinds of Sprint stuff in the EPST, not sure how to clean that up, or if I'm screwed.
Anyone know of a way to get it all restored back to Verizon acceptable?
I have the 2.4 SPD, Radio 3.27, and DCD 2.2.6 and expect for no phone service, love it.
I've called Verizon, they have not been helpful, I did check my a-key both before and after and it was blank both times.
Help?
Fred Rat said:
It left all kinds of Sprint stuff in the EPST, not sure how to clean that up, or if I'm screwed.
Anyone know of a way to get it all restored back to Verizon acceptable?
I have the 2.4 SPD, Radio 3.27, and DCD 2.2.6 and expect for no phone service, love it.
I've called Verizon, they have not been helpful, I did check my a-key both before and after and it was blank both times.
Help?
Click to expand...
Click to collapse
I don't know if it will work, but try going into the phone app and dialing ##786 Talk
This is supposed to completely reset the device, including the EPST settings, to factory clean. You will need to restore the MSID and MDN, so make sure you know what they are. I do not know if you will need to obtain an a-key from VZW. After that you will probably need to do the *228 setup.
If that does not work, maybe reflashing the radio and Verizon ROM will help.
I've got it fixed
Thanks for the tip; while I was waiting for that I tried a number of things, one of which worked.
What I did was to reflash the stock verizon rom from
http://forum.xda-developers.com/showthread.php?t=359659&page=2
Using the complete version.
This put back the original radio and rom.
When I rebooted after that, it ran some cabs on first boot. One of them was called something like ResetRadio. Anyway after that I was able to call *228 and could do both options 1 and 2. Which I could not do successfully before.
I was still getting unauthenticated messages when I tried to call anyone, and could not take incoming calls.
I then called VZW and got a new A-Key, that fixed the phone so I could call in/out, but internet access was still broken.
They had me take my battery out, while they did something on their end; after that we redid the *228 and internet access is now working. We did a test text message and that worked as well.
I think the key in all of this, is to NOT flash the Sprint ROM into a Verizon phone, but if you do, you can reflash the Verizon version to put things back in order from the link I mentioned above.
I am using a DCD rom 2.2.6, and while I am a noob on some of this, I seem to recall him mentioning that he no longer includes the extended ROM; if that includes the part that resets the radio on a hard reset, I think it's actually required for people to keep their sanity.
Hope this helps, and for those that are worried that they will screw up their phones and have no way back from the far side of disaster, I can say that I've been there and made my way back.
Best of luck to you all.
DCD 2.2.6, GPS, and yes I can even make phone calls!
I am helping my mom with her VX6800 for verizon. I first flashed the RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4 350H_SPCS_AM_Ship ROM, just to get the radio from it (If anyone knows where to get the entire Ship ROM with 3.42.30 please tell me, can't find it). I then flashed DCD 3.2.2 and then installed the Verizon carrier cab.
The phone was working right away to make calls, although it still showed Sprint on it, as opposed to Verizon. When i try to access the internet it gives me an error saying "Dialed #777, Cannot connect for unknown reason." I had flashed a verizon phone for a friend before and had to call verizon to get a new code, doesn't seem like the issue here but not sure why i'm not getting internet service and if it has anything to do with the sprint logo showing on the screen..
TIA!!
Sounds like maybe you let the sprint ROM reboot (reset) after you flashed it to get the radio? Check the Titan WIKI on XDA and it'll tell you everything you need to know to fix it.
worthingtonmedic38 said:
Sounds like maybe you let the sprint ROM reboot (reset) after you flashed it to get the radio? Check the Titan WIKI on XDA and it'll tell you everything you need to know to fix it.
Click to expand...
Click to collapse
I have read through the Wiki a few times and it doesn't say anything in there about the ROM rebooting or resetting
"To flash, enter bootloader mode by pressing the power, camera button and then the reset button. The screen should be at a three colored (red, Blue and Green) screen, check to make sure you have the appropriate bootloader. Then plug the device and computer into the USB cable. Start the RUU.exe upgrade program on the PC that usually is provided with the ROM."
I did all this, except not sure if i am using a RUU utility, i just double click on the ROM icon,which i think has the RUU built in. It then flashes the SPrint ROM. if i am supposed to do something after it has finished flashing to prevent it from rebooting or resetting i couldn't find it in the wiki, so if u can just tell me that would help me out a lot...thanks heaps
you let the customizations run... end of discussion...
i think at this point, it'd be easiest for you to flash back to Verizon STOCK and then follow my guide to upgrade it (see signature)..
To flash back to stock, see the info from: http://forum.xda-developers.com/showthread.php?t=376873
You need to reset before the carrier customizations kick in. If you didn't then that is why you have the Sprint info on your phone.
There are a bunch of threads here about this problem. Let me see if I can find a link to one.
Here is some more info from the wiki:
do NOT boot into the OS after flashing to any of these ROMs.. After screen calibration the carrier customisations will run and alter your EPST settings to that operator's settings.
OOPS! You just let the customisations run but are with a different carrier than the ROM you just flashed to!
Choose A or B
A.follow above EPST instructions in step I to edit back to the settings that you recorded
B.Goto to the Titan Stock Page to restore your device back your carrier's default settings, boot into the OS and permit the cusomisations to run, and then return back here to start over again.
Click to expand...
Click to collapse
you dont need to reset at all. ugh. follow these steps:
1) flash sprint rom
2) at 'tap screen to set up device' flash your rom of choice
3) install carrier cab
4) soft reset
literally, its that simple. if you need a step by step, i guess here you go:
1) flash sprint rom
no need to enter bootloader unless your installing from SD​2) after rom installs, it will automatically reset
3) at 'tap screen to set up device', unplug and plug your phone back in
4)run (assuming you are using DCD) the kitchen or the RUU.
phone will reset after done installing​5) calibrate the screen and let customizations run
6) install carrier cab
7) soft reset
done
Dillsnik said:
I am helping my mom with her VX6800 for verizon. I first flashed the RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4 350H_SPCS_AM_Ship ROM, just to get the radio from it (If anyone knows where to get the entire Ship ROM with 3.42.30 please tell me, can't find it). I then flashed DCD 3.2.2 and then installed the Verizon carrier cab.
The phone was working right away to make calls, although it still showed Sprint on it, as opposed to Verizon. When i try to access the internet it gives me an error saying "Dialed #777, Cannot connect for unknown reason." I had flashed a verizon phone for a friend before and had to call verizon to get a new code, doesn't seem like the issue here but not sure why i'm not getting internet service and if it has anything to do with the sprint logo showing on the screen..
TIA!!
Click to expand...
Click to collapse
Hi there,
The 3.42.30 Radio was pulled from a Vogue and was modified to work with there Titan, therefore there is no ship ROM for it. Your best bet is to format an SD card with the FAT32 filesystem and copy the TITAIMG.NBH onto it and load up in bootloader mode. There are thorough instructions in the Titan wiki. Best of luck!
Hate to break it to you all, but if he let customizations run...then he's screwed unless he can get Verizon to issue him a DMU reset. If not, the phone needs to be replaced. End of story.
damn....I had to get a new phone after my first time flashing too...
gc14 said:
Hate to break it to you all, but if he let customizations run...then he's screwed unless he can get Verizon to issue him a DMU reset. If not, the phone needs to be replaced. End of story.
Click to expand...
Click to collapse
Are you serious?? oh no
How would you go about asking vzw for a DMU reset? i'm not sure what that is....and would vzw do a phone replacement??? they won't say it was voided?
Thanks all for all your help...i haven't had a chance to reflash anything yet, but gonna give it a go later today and pray it works!
Dillsnik said:
Are you serious?? oh no
How would you go about asking vzw for a DMU reset? i'm not sure what that is....and would vzw do a phone replacement??? they won't say it was voided?
Thanks all for all your help...i haven't had a chance to reflash anything yet, but gonna give it a go later today and pray it works!
Click to expand...
Click to collapse
if you call verizon, youre gunna have to make it sound like you know WAY more than they do about the issue. if you google 'DMU reset', im sure youll find some information about this. if you have another phone, switch your service to the other ESN, then switch it back. then call verizon and say that your MIP settings are not receiving a static IP from verizon. tell them you just switched your service back to this phone, and youve had this issue before. Tell them you need the data features removed and re-added to the account, and you need your DMU keys reset.
if you cant switch ESNs to and back, youll have to say you had a serious software issue on your phone, which required a hard reset and now your data connection is taking way longer than normal to connect, and you would like your DMU keys reset.
i recommend researching as much as you can about this before calling. depending on the TSR you get, they could ask you alot of questions. most of the time, if you answer all their questions before they ask them, theyll do what you say
EDIT:
when you do talk to them, before they can tell you any steps, make sure you tell them that you've:
soft reset
hard reset
clear storage
*288 1
*228 2
*22899
those are all the general things theyre gunna tell you to do before they reset anything for you. you just need to make it sound like youve already done everything possible, so the last possible step is resetting your keys for you
VZW has....well, an interesting way of doing things
So, I spoke to a VZW rep tonight after flashing back to a stock VZW ROM and, as expected, not getting a data connection (or able to make calls).
The rep was pretty helpful and knowledgeable. Mind you, i am on AT&T and this is my mom's phone i am helping her with (or at least trying to ). ATT base reps suck and for any minor network thing i would always need to speak to a data support tech (who these days tend to also suck pretty bad as well!) This VZW rep was no dummy and, to my surprise, understood all the things i threw at her. She was overly diligent which gets annoying, retrying lots of the same things, but i understand these people need to be, and she was making progress (bc after flashing the stock ROM my voice calling wasn't working initially either).
When I mentioned doing a DMU reset she explained that she can't do that and in order to have that done she needs to submit a request to her network team. I thought she would have them call me to troubleshoot the problem or something, but that isn't how it works . The network team doesn't speak to customers; she would be calling me back to tell me that the problem should be fixed and they did what they needed to do. I found it odd that they wouldn't need to speak to me to find out if it is working or not....Apparently, she said, they can tell if my phone is working/not working for the data connection.
For now i am kind of impressed with VZW's whole approach on how to solve this kind of thing (although it'd been nice if i coulda spoke NOW to a rep that can actually fix my problem), but i am a bit skeptical that it is actually gonna happen. We'll see what they come back with and hopefully i don't get run around in circles and they can indeed get my data working by resetting the DMU or whatever they need to do.
So, I spoke to a VZW rep tonight after flashing back to a stock VZW ROM and, as expected, not getting a data connection (or able to make calls).
The rep was pretty helpful and knowledgeable. Mind you, i am on AT&T and this is my mom's phone i am helping her with (or at least trying to ). ATT base reps suck and for any minor network thing i would always need to speak to a data support tech (who these days tend to also suck pretty bad as well!) This VZW rep was no dummy and, to my surprise, understood all the things i threw at her. She was overly diligent which gets annoying, retrying lots of the same things, but i understand these people need to be, and she was making progress (bc after flashing the stock ROM my voice calling wasn't working initially either).
When I mentioned doing a DMU reset she explained that she can't do that and in order to have that done she needs to submit a request to her network team. I thought she would have them call me to troubleshoot the problem or something, but that isn't how it works . The network team doesn't speak to customers; she would be calling me back to tell me that the problem should be fixed and they did what they needed to do. I found it odd that they wouldn't need to speak to me to find out if it is working or not....Apparently, she said, they can tell if my phone is working/not working for the data connection.
For now i am kind of impressed with VZW's whole approach on how to solve this kind of thing (although it'd been nice if i coulda spoke NOW to a rep that can actually fix my problem), but i am a bit skeptical that it is actually gonna happen. We'll see what they come back with and hopefully i don't get run around in circles and they can indeed get my data working by resetting the DMU or whatever they need to do.
Click to expand...
Click to collapse
She could have performed the DMU reset without bringing in the network team. She just didn't know how.
oh. well, for what it's worth, your support reps (even the bad ones apparantly) for the most part seem way better than the ones @ ATT! still not planning on switching any time soon though
Thank you!
I just want to deeply thank everyone that contributed to helping me get my problem fixed. The phone is now up and running and I am most appreciative to all of you that took the time to help me!!!
You really have a great community here!
FWIW, Verizon data tech fixed my problem but when i asked what he did he would not tell me....he basically said he "checked some things out and madde sure everything was set up right" while he had me take out my battery and wait. I asked what specifically he did, for research purposes and he said he couldn't tell me
Lol..he performed a DMU reset. I swear some of those techs are so dumb.
Well, he actually denied that he did a DMU reset cause i asked if that was specifically what he did and he said, no...i just checked some things out...and wouldn't tell me what he did.
i am sure you're right, he did the reset, but they must be instructed not to tell customers what they do...i guess maybe to try to prevent us from telling them what to do?
Hey all I was given an Eris by a friend so I rooted it easy enough at 1.5 last August. Since then I have had a few different custom roms loaded and everyone of them that I tried to activate the phone on didn't work. This phone was not activated when I rooted it, and I have to take it to my local verizon shop to have them try to activate it after they deactivate my moto droid 1. I' ve been digging for awhile now trying to figure out if it's the baseband version or what. Can someone please help if at all possible.
Current phone info:
Firmware: 2.1
Baseband: 2.42.01.04.27
Kernel: 2.6.29,
Build: 2.36.605.1 case release-keys
Software 2.36.605.1
Browser WebKit 3.1
PRI: 2.11_002
PRL: 58003
ERI: 5
When the phone boots it shows the verizon logo which doesn't completely mean the radio is flashed for versions network, but I have no idea how to tell otherwise.
Thanks.
If you activate the phone with a stock, or near-stock ROM (let's say Ivanmmj's "Official 1.0"), then thereafter, nothing you do to the phone with dev ROMs from this site will change the phone's activation data (stored in the phone) afterward - not flashing a different radio, nor performing a "wipe/factory reset" (in Amon_RA), nor installing a different ROM will change that.
When it comes to deactivating the phone - or more precisely, clearing the activation state of the phone, the only thing that seems to accomplish that is one of the factory recoveries - Amon_RA does not touch it. This happens if you perform a "factory reset" in the regular OS, which actually causes a boot to the recovery, which does all the "dirty work". You can also manually boot the stock recovery, and use the wipe menu to achieve the same result.
You can see that this makes de-activation inconvenient for rooters - but most of them don't need to do that.
So I'm reluctant to conclude that the radio firmware is affecting your result.
What happens when you try dialing *228 option 1? The call goes through, but you get an error voice announcement after some delay?
I was under the impression that people that flip back and forth between two phones on the same service don't ever bother to de-activate the phone in use: they just make sure that current phone is turned off before they attempt to activate the next phone.
I suppose you could restore the phone back to complete stock (including the stock recovery) before activating it, and then re-root it and reload a nandroid backup... but that's sort of a pain in the neck if this is something you plan on doing regularly.
bftb0
PS I could swear I have activated my phone (*228 option 1) with a dev ROM on the phone, but don't remember the specific details.
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
RnkG said:
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
Click to expand...
Click to collapse
I just re-read your initial post and actually can't tell if the phone has ever been successfully activated since you received it. You mentioned taking it in to the Verizon store, but you didn't say what the outcome was - was the Verizon store unable to activate it?
Normally when you dial *228 it just sounds like a normal voice call - you hear audio, the recorded lady's voice provides a menu, etc. Since that needs to happen in order to activate the phone, it is fairly obvious that the cellular radio must be working completely for that to happen - so the fact that you don't hear any audio seems to indicate something is wrong.
Why don't you try and reflash the phone back to stock using the download from this thread which also flashes the radio:
[ROM][10/20/2010]FlashBack21 v1 -Return to Factory Stock - UPDATED
And see if that gets you any different result. That would eliminate any effect of "dev" software, and also reflashes the radio with the July 2010 version - the last one officially shipped by VZW/HTC for the Eris. If you can't get audio (and you are sure from playing music that there isn't a speaker problem), that would point to a hardware problem.
BTW - even if the phone is working completely, VZW needs to already be aware that it's ESN/MEID is associated to your account, and I think that your other phone needs to be turned off at the time you attempt activation.
cheers
Thanks again. I'll work through that and then post back here.
Thanks again!
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
RnkG said:
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
If they activated it I don't know how they could be blocking it. I would've checked to see if it was working before I left the store, and when it wasn't, would've brought this issue up with them.
Are you just going by their word that they activated it, or is there some other way you can tell that it's activated, even though you're not getting any service? What I mean is, if you're not getting any service, how can you be sure they activated it successfully?
RnkG said:
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
Other than bad hardware, the only thing which would cause this problem would be a "blacklisted ESN" - that would usually be a stolen phone, or a phone that was on a Verizon account that was abandoned by the subscriber with an unpaid balance. (Verizon doesn't want customers who cheat them to continue to cheat them by habitually opening new accounts under assumed identities, so they just blacklist the ESNs of phones that were used on abandoned accounts with unpaid balances)
Verizon won't activate phones with blacklisted ESNs - but if you walked in the phone store and asked them to activate it for you, I would presume that they would have told you straight up "We can't/won't activate this phone".
The radio does not use a separate technology for 911 calls, so, yeah - there is something odd going on here. Perhaps you had a "green" VZW customer assistant that isn't familiar with what happens when someone wants to activate a blacklisted phone, and simply didn't take notice when "something unusual" popped up on the computer they used to enter in your activation request.
You've got stock software on the phone now, so I wouldn't hesitate to pick their brains about it. Telling a VZW tech about the 911 call might convince them a little better - but just remember that you are admitting to a criminal activity (calling 911 without due cause).
Also - bear in mind that by law (in the US) every cell phone has an aGPS unit in it, precisely for the purpose of emergency services locating a cellular handset when the user is incapacitated. ( There is a small risk that if you make a 911 call, cops will end up at your door even if you hang up.)
I just got done SBF'ing my phone (DX2) from the Atrix ROM because I didn't know about A-Key's and thought I lost something major. Anyway, I still plan on running a custom ROM but does anyone know if Verizon could detect that by chance when I call to get my phone re-authenticated? I don't want to call them twice in a matter of an hour or so.
AFAIK VZW cannot tell the difference. Furthermore, I don't think they care how many times you *228, as I've done it multiple times over the past week or so, and I know my friends done it a couple of times in an hour when he was first starting out with his DX. VZWs primary concern is that your MEID matches what they have on record, and isn't reported as stolen. They only really care if you have a custom rom on your phone if you take it in for repairs.
Ok, thanks. Just to clarify I'm not doing the *228 activation. It's activated and I can text, browse, etc. but I cannot place calls because my A-Key was wiped somewhere along the line. I have to dial #8899 and actually speak with someone. That's where I'm concerned about whether or not they will be able to detect the ROM and in turn void my warranty.
I don't believe they'll be able to detect the ROM, but have you tried *228? I just don't understand why you would have texting/data but not voice.
Yes I have done *228 twice. The problem is that the A-key (authentication key) was lost during one of the hard resets. I'm not sure why it happens but it does. I'm also not sure how you retain texting/data but lose voice. Here the thread I found that has a little more detail and the solution to the authentication problem:
http://forum.xda-developers.com/showthread.php?t=363967
Reading through that thread it doesn't seem like getting the A-Key would create any complications. Those people were in the same situation as you, and if they wanna know why you had a problem, then you had to hard reset, after installing some wonky programs cuz you're a dev.
So I installed CM7 following the wiki on there site, using Revolutionary.io Everything worked fine, got s-off, installed the CWM recovery and then installed CM7. Well when I boot to CM7 the phone is telling me that it is no longer activated. It worked perfectly before. Ive rooted several EVOs on Sprint in the past and have no issues, didnt know if anyone had has some similar problems before and what they did to fix it.
This is a common Revolutionary bug.
You can try to take the battery out for a full minute and then go to settings, update, update profile. Then update the PRL. This did not work for me.
If that fails you need to try to send text messages and record the error codes when they fail. Call sprint from a different phone and give them those codes (dont tell them you rooted or s-off'ed) Hopefully you get someone with half a brain and they ask you for the IMEL code (behind the battery) and reset your phone. It took me 3 calls (and resets) to Sprint over a week but finally it stuck. On a friends phone it only took 1 reset by Sprint to get it to work. If you have any call or text failures after Sprint resets it you need to call them again.
I personally believe this is caused by a failure in the hands-free activation mechanism preformed after running Revolutionary.
Is it possible that you flashed a GSM rom aka the wrong radios? I'm assuming you mean it has no network connections by "not activated", some more detail might help you get a solution quicker.
Good luck!
Well after some reading, people were saying that I should go back to stock and then reactivate. So I did that and when back to CM7 and and nothing. Others were saying to play with the MSL buy dialing ##3282 or 228 but I didn't have the code for it so I just went back to CM7 and it turns out it works now. Not sure why but who the hell cares. Sucks that Revolutionary has those issues. Its worked great for me so far.
I had this happen too right after I rooted a week ago using Revolutionary.
It's no big deal and you don't need to waste your time switching roms or jumping through hoops just call Sprint and tell the your phone just stopped receiving calls.
In my case my 3g data worked but not texts or calls. I called Sprint and just said my phone wasn't making or receiving texts or calls and I wasn't sure why.
They just reset something on their end or whatever they do and I was good to go. No need to do anything else.
Sent from my PG86100 using xda premium