Related
so like a kid in a candy store i got ahold of ROM manager and ODIN and started flashing cool looking roms..next thing i know, the t-mobile logo is popping up and i am a not-so-proud owner of a modded T-Mobile Captivate, no longer an ATT Galaxy S!
of course the t-mobile network uses different frequencies and the like, so the phone part of my phone stopped working...bummer! i grumbled as i flashed back to a ROM that worked with the ATT network (FUSION it is called) but apparently that ROM does not mess with the internal network settings thats why it worked so well initially it didnt change the stock cell internals...
so now i have a hybrid phone, half-tomobile half-att half Fusion, and it only picks us signals from the Edge network!!! i barely get any reception so it pretty useless...
so i need some help...i can i get this beast back into a condition where is will work as an ATT galaxy?? also, for whatever reason i cannot mount or download market apps to the phone tho it does pickup wifi connections...
any help/ideas appreciated...advTHANKSance!
- mark
Flash back to stock with odin 1 click. Or try just flashing a new modem with cwm.
Sent from Serenpitidy x.x
ok...i finally fixed the mess i made by using this process...
manually set the modem/APK using this guide...may or may not have been needed in the end...
http://www.wireless.att.com/answer-center/solutionDisplay.jsp?solutionId=KB110934
reset the phone to factory using this thread...
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
note..i used the old I897UCJH2 Firmware but the plan is to upgrade to JH6 tonight...
did a factory reset on the phone and BINGO...full working baseline phone. thanks for the help guys what a great site u run
I just tried to flash the Telstra (Australia) SBF. No info comes up in file properties and it gives an instant 'failed flash' message.
I am a bit stuck- i can only flash the China Froyo and the GB Froyo, the only 'Fixed' SBF I can ever flash is the 2.2GB_NoCG_31_39.sbf -(Higgsy fix). The China rom is the first and only Froyo rom I flashed with the above fix.
1a. :I want to know why I cannot flash 'fixed SBF's' that come with JBoogie, ADXLmod, barebones etc roms.
1b :Why do I still have to use the 'Higgsy fix' 2.2GB_NoCG_31_39.sbf? It appears that I am somehow locked to it.
1c :Is it because of the Telstra rom I am on- with all rom flashing instructions, it is mentioned eg 'if you are on 2,21 or 2.34 fw etc- no reference is ever made to the 2.26 fw.
2: I want to know how flashing a rom without the corresponding SBF actually affects the operating of the rom- eg: I get random reboots, black screens, freezups=- is this likely an issue with the rom or because I cannot flash the fixed SBF.
3. Will restoring a Telstra nanodroid on top of the China Froyo SBF that I am running, then applying the fixed Telstra SBF that racca graciously provided make my Defy exactly like stock- or will there still be remnants of the China Froyo etc rattling around under the hood and potentially affecting stability and continuing to affect my ability to flash fixed SBF's as per Q 1 & 2.
4. Does anyone have a FullTelstra SBF that works unlike the one already posted on XDA.
I have tried renamimg and moving sbf to root folder as per a suggestion for 64 bit windows, though i am only on 32bit, it didn't work for me- 'start' is still greyed out in RSDLite..
I have also tried different rsdlite versions.
I welcome any other suggestions or questions.. At least I would like to know what is going on and how it affects my phone as I have spent hours and hours searching these and other forums and am none the wiser..
Cheers
Gavin
Accidental 2nd post-ignore.
what exactly are you trying to do?
i can't make much out of your long and pointless statements.
be specific about what you need, then maybe we can help.
all i can understand is that you might want the fixed sbf, so here it is.
http://mir.cr/6MJBVDCN
Thanks for that, pointless is a bit harsh though, long maybe- i was trying to give some background to prevent 'have you tried that, just do this- when it is clearly not applicable to my situation.
I will try to put it in point form.
I hope that is a bit clearer, but it is a complicated situation- there are alot of threads dancing around similar themes, but I cannot find specific answers to these questions- i can't see how I could provide less information without having 5 pages of people directing me to posts that I have already looked at but aren't applicable, so yes it is a bit long, but by doing this much misdirected effort is saved by myself and those helping.
Thanks again
Looking at my original post again, it was hard to see what I was asking, thanks racca.
I just restored the Telstra factory reset nanodroid- the start button was greyed out with the Telstra SBF , so i can't use it. Had to use the 'Higgsy fix' to get it to boot. Weird, i just don't understand it.
To be honest, with all the eventual issues with any rom i use, i would prefer to go back to stock (i will have to put up with the grey status bar, short battery life and no flash). I am tired of getting crashes at the most inopportune times.
Can't wait until the bootloader is fully cracked- I have put Gingervillain (CM7 base) on her Desire, which is much more stable than any rom when i was using it.
Update- it just won't boot now, have to reflash the China Froyo SBF, looks like I am stuck with daily @ 3x daily reboots, bluetooth that works 60% of the time, dropped calls etc....
Change SBF file name
Hey there,
I kinda have the same issues as you do, I think...
The RDS lite gave me an instant ROM-flash error when trying various SBF's. I simply renamed the file name to an SBF file name that was working, yes it got a little confusing... first I renamed the original working SBF to *.old.
Suddenly the flash process was working, I've renamed SBF-files on 4 different occasions in order to get it to work.
I'm not quite sure whether you have this issue or you have something different going on, but feel free to try it.
//Dave
Sounds like a plan, I will give it a go. Thanks.
Thanks Dave69 and Racca, i just renamed the TElstra fixed sbf to the higgsy fix; restored the stock nanodroid and flashed it and it worked. It at least gives me the confidence to flash others now, but will sit on this for a bit- don't have time for more tinkering this weekend.
Titanium wouldn't work with the Telstra rom- said it had restored apps, but wouldn't restore evn one.
Thankfully I got Barebones running, SBF and all. Looks great. Thanks guys.
I would still like to know what's going on though, I haven't tried the TElstra full SBF with the rename yet- it had a different issue than others- just failed. May try again later.
Sounds like you have the same problem as me, was on the telstra on. Not being careful enough I flashed a non downgradable 3.4.2_155-002 sbf. So now I can't downgrade back to the stock Telstra one. I have tried both nandroid backups and flashing the stock telstra sbf and neither work. so am stuck on this rom running JBoogie GingerBlur
Not compaining, for a blur rom it is quite fast, only thing is I can't downgrade back to telstra if the phone needs to be returned for anything.
Hope this helps.
Cheers.
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
superfastmonkey said:
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
Click to expand...
Click to collapse
ok, now where do i begin. i'll just say what i can think of instead of answering every single question.
sbf's contains various code groups as you may noticed while flashing it slipts into smaller pieces.
out of those, cg31&39 are non-downgradable and the pair of them must match. all other partitions on the phone are either not flashed by the sbf (e.g. bootloader/mbmloader, pds), useless (cdrom) or downgradable (kernel, recovery, lbl, devtree).
there are no hardware incompatibilities except the chinese ones, but if you don't update cg31(cdt) to match your /system(cg39) you might have some minor issues (i singles these out because they are not downgradable, of course you'll have issues if you don't match all other things).
you might have a chance fooling tel$tra by flashing the sbf i provided (stock 2.26.0) and restore the nandroid. it should be almost identical except you'll get busted when they try to do flash their service sbf.
the bottom line is,
1. if you flashed any sbf larger than 50MB it must have cg39 in it, and you can't downgrade.
2. you must use matching kernel/devtree with the system: the chinese ones will not be compatible with any other roms, you can't mix match froyo with eclair.
Thanks racca, it makes things a bit clearer. I didn't think I had flashed the GB rom, but I must have-it was 3 or 4 mths ago- it explains why I used the Higgsy fix...i think the China one came out very shortly after..
I should probably try flashing a 2.1 rom b4 restoring the telstra nano if I want stock-( with Telstra, we will have to wait until 3 mths + after the rest of the world gets Froyo for them to fill it to the brim with bloat ware..)..
It looks like the Higgsy fix didn't work for our devices anyway-i suspect my phone believes it is a 3.42 fw now.
In any case, I am relieved to have a way to flash the fixed sbf's now.. Barebones is very impressive, no hint of an issue, but need to run it for a week to really see.
Thanks.
I have a Telstra phone too and after a week of owning it back in January, I had already installed a 2.2 De-blurred ROM. I did have radio issues at first and also remember a non-stop reboot issue. I think it was the USB debugging somehow but I could be wrong.
Now I install new ROMs with ease when the need strikes me.
Are you able to flash the fixed sbfs for roms you install?
I've just put the CM7 rom on mine, best rom I've used. Also flashed a fixed rom with it.
Next thing i tried was restoring a nandroid backup of the default telstra rom, then flashed a fixed stock telstra sbf, this worked and was able to at least make the phone look like it was stock. Whether or not that would be enough if i had to send the phone in for repairs. Can only try if it needs to go in.
CM7 is by far the fastest rom I've tried. Only used for a day so far and no problems yet. Highly recommend this one.
Cheers
Sent from my MB525 using XDA App
I flashed the fixed sbf by renaming after restoring the telstra nano and it worked, but didn't run properly, I did it a couple of months ago with just the nano after having jboogies blurless ginger and it passed for warranty. Haven't tried renaming the full telstra sbf yet. I might over the long weekend.
Sent from my MB525 using XDA Premium App
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
samorgs said:
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
You'll be fine.
On a side note, it's ridiculous that Optus have official froyo already, Telstra due in July.
Sent from my MB525 using XDA Premium App
I am sending my phone back into samsung for repair, and I want to bring it back to its stock condition. I have unlocked the bootloader, flashed CW recovery, and installed superuser with no problems, however cannot seem to figure how to go into reverse. I understand how to re-lock the bootloader. I have read on the forums through the countless amounts of people asking this. I am however trying to use the ROM for the GTJ61 build found from this thread http://forum.xda-developers.com/showthread.php?p=13478981 When I try to use Clockwork Recovery, and go to restore, it states there is a MD5 mismatch. Am I suppose to install from zip or update from SD with CWR, or should I try to flash everything back onto there? I do not know what to do. Am I even trying to use the right ROM? The GTJ61 build is the original build that came on my phone, but would another one work?
follow this thread http://forum.xda-developers.com/showthread.php?t=1033269
all you have to do is clear your data, flash the stock rom and stock recovery, and then lock the bootloader
Thank you very much. I figured it out. All I have to do now is destroy the evidence on my sd and seen my NS away.
I realize superuser is still alive and well after I did everything. How I would I get rid of it?
I just uninstalled it. it might have gotten restored when you logged in with your gmail account. did you wipe data and the cache with cwm before you flashed the rom?
edit: did the ots update to 2.3.4 install fine for you?
I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.
SleepyFox said:
I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.
Click to expand...
Click to collapse
I did mean ota lol. my bad. where'd you get a 2.3.4 rom from?
edit: if you used the 2.3.4 rom from the thread you posted, just be aware that it isn't official. i'm not sure if the link I posted has the official rom, but you can download OTA updates with it so I would assume that it's pretty damn official lol
I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?
SleepyFox said:
I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?
Click to expand...
Click to collapse
I don't know much about it either, but I would assume that you should put it on a stock rom if you're sending it back into samsung. I could be totally wrong though
I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.
SleepyFox said:
I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.
Click to expand...
Click to collapse
I would guess that superuser would be one of the first things they check for to see if you broke warranty. you could just uninstall it and wipe everything through cwm again to make sure it's gone
I managed to fix everything. I just was searching through the system folder of the 2.3.4 rom and to my surprise there was little old superuser. So I deleted the .apk and bin files. After that I restored the ROM. Fixed everything. The stress of sending in a phone with superuser is gone and I am back to being stocked
Two questions for you OP:
1. How do you have a warranty on a I9020A? Is it the subsidized version from Best Buy (i.e. "AT&T's sanctioned model")
2. Why do you need warranty repair? What broke?
Yes I got my phone from best buy. I just registered the imei with samsung and I am under the 1 year warranty. I have a problem with my battery draining 80% in 6 hours little to no use with all radios besides 2g turned off. I know that the NS has not so stellar battery life, but there is genuinely a problem with mine. It cannot even survive for half a day.
Hmm, I had that very issue with three past i9020a's (two from Amazon, one white one from Newegg). They were all the Rogers model, which is said to be identical to the one Best Buy is selling as a subsidized model.
I just bought another i9020a on eBay (no, I never learn) and hope to try some fancy methods to save on battery life (ROMs, etc). I also experienced VERY slow 3G with the i9020a on AT&T's 3G network here in the US. Like 300kbs download slow. I read that if you flash the radio to KB3 it gets very fast, like HSPA 3G should be.
I don't care about rooting and flashing because my phone will not have a warranty. I do, however, suspect that there is nothing wrong with your phone, rather the battery life is just random. One of the i9020a models I had drained a fresh charge in like 3 hrs of sitting idle w/full bars. The phone was burning hot. I restarted it, charged it up, and it lasted over 16 hrs the next time. Very erratic and strange, but that seems to be par for the course with the NS.
I would first see if the phones you bought were registered yet. You never know when you would need samsung to take care of something for you. The correct radio for the US ATT is UCKE1. You should be getting data speeds of about 3.3 megabits. My battery has been consistently low.
SleepyFox said:
The correct radio for the US ATT is UCKE1.
Click to expand...
Click to collapse
So that may explain what's different between the international (i.e. Canadian) I9020A and the "Best Buy" AT&T sanctioned I9020A...a different radio?
Is it possible to flash the KB1 radio of the Canadian I9020A to the AT&T friendly UCKE1 radio?
I am running the stock version of Gingerbread on my phone and just noticed today that the WIFI tethering option is not working. I don't live in the US and my phone is SIM unlocked.
When I select the WIFI tethering option I get a message to contact AT&T to purchase a tethering plan, I guess they did this to prevent people in the US from doing it since it was possible to do it with the Froyo version by deleting the APN settings.
I downloaded a widget that let me do the tethering once but not anymore.
Has anyone found a workaround for this?
Yes. Quit using the att stock rom.
Sent from my Inspire 4G using XDA Premium App
apn
follow this and use the guide to get free wifi teather on your phone.
http://www.unigizmo.com/1696/steps-by-steps-guide-–-to-enable-data-tethering-on-htc-inspire-4g
That will only work for Froyo but not Gingerbread . The new ROM won't even let you use those APN settings
I guess I will have to go back to stock Froyo. I did rooted once and instaled Coredroid but had to many annoying issues. Oh well hopefully someone will find a fix that doesn't involved rooting and whatnot. But thanks anyways
I have the GB too and I can confirm the old workaround doesn't work around and more.
I'm hoping for a new way .... Does anyone know of a fix or a 3rd party app that will provide the same functionality?
I've never "rooted" a phone before. I have the HTC Inspire and I was hoping to.
Can I root the GB version that is already installed? There is a Wireless Tethering app that won't work and asks .... Is your device rooted?
Hi everyone,
So far I haven't found any fix for the WIFI tethering or an app available in the Android market that will bypass that. So I just went back to Stock Froyo using the official RUU from HTC
About rooting, yeah sounds a bit complicated but if you follow all the steps then you'll be fine. I was kinda scared when I attempted to root my phone. I used the hack kit or whatever was called and I worked, make a search and you will find the guide. Then I installed CoreDroid V7 but it had some annoying issues, no random reboots or force closes though. Then after a week of using that ROM I read about the GB official updated and I downloaded the RUU. I gotta say the phone got a bit faster but today I discovered the WIFI tethering thing and it is something I use, maybe not all the time but is a great tool when there is no WIFI available to connect your computer to the Internet.
I shall update to GB when someone finds a fix for that. Good luck you all
Something you can try. I don't know if it will still work but if you turn airplane mode on and all at&t signal is off then turn on your wifi and go to the market and search for wifi tether apps.
Sent from my Desire HD using XDA App
I did try that. What I did was to put the phone in AP mode and it would let me activate the tethering option but as soon as I enabled the mobile connection I would get the same message that I need to call bla bla.
But Froyo will do alright for me right now. I didn't see any noticeable changes in the GUI in comparison with GB but GB does manage the resources better and improves the battery life. Next time I'll get a phone that is not carrier branded LOL
Bobbypty, I am having the exact same problem and want to do what you did when you say "So I just went back to Stock Froyo using the official RUU from HTC."
Can you please point me in the right direction as to how to obtain Stock Froyo from HTC? I have been to their site and can't find it, and I've searched the forums here and elsewhere on the web and can't find anything specific to this. I would really appreciate your help since it sounds like you have done EXACTLY what I want to do!
What's up?
Here is the direct download for the RUU and this will install the stock 2.2 for the phone. You will need to install the HTC sync in order to run it. Just double clicked on the exe file and you shouldn't have any problems. Make sure your phone has 30%+ of battery.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
Or go here and the download link is there
http://forum.xda-developers.com/showthread.php?t=957692
bobbypty said:
What's up?
Here is the direct download for the RUU and this will install the stock 2.2 for the phone. You will need to install the HTC sync in order to run it. Just double clicked on the exe file and you shouldn't have any problems. Make sure your phone has 30%+ of battery.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
Or go here and the download link is there
http://forum.xda-developers.com/showthread.php?t=957692
Click to expand...
Click to collapse
Is that going to downgrade radio as well? Thanks in advance.
Yup.
Everything will go back to stock. Radio version 12.39.60.19H_26.06.04.06_M Android version 2.2.1
Hi everyone,
Seems that there is no fix for this right now since the ROM for this phone is branded by ATT unlike the Desire HD (Close sister to this phone) is a unbranded HTC ROM.
So pretty much the options we have is either to go back to stock Froyo or root the phone and then install a custom ROM that is based off the DHD Gingerbread ROM, I've been reading other forums and the custom ROMs based from the Inspire 4G will still have the WIFI tethering option blocked, so stay away from those. Make sure the ROM you are installing is based from the DHD. Try Coredroid, Cyanogenmod or whatever you like. Rooting this phone is not that complicated and I was able to do it with a little help.
Good luck with the rooting/flashing if you decide to go for that. Search for Ace Hack Kit for instructions.
I was able to get wireless tethering working on an AT&T gingerbread ROM, I modifed the apn xml before i flashed it, I modified APN Type to * for all of the AT&T / ATT/ medianet entries in the file (except for the mms apn that exists in there). I can upload my file when I get home or you can download my ROM from the rom thread (static nonsense) and grab it from /system/etc. Theres also an apn file in /system/framework/framework-res.apk inside the xml folder, Mine is more or less blank, so you may want to replace that file as well. Just a thought anyways
beerbaronstatic said:
I was able to get wireless tethering working on an AT&T gingerbread ROM, I modifed the apn xml before i flashed it, I modified APN Type to * for all of the AT&T / ATT/ medianet entries in the file (except for the mms apn that exists in there). I can upload my file when I get home or you can download my ROM from the rom thread (static nonsense) and grab it from /system/etc. Theres also an apn file in /system/framework/framework-res.apk inside the xml folder, Mine is more or less blank, so you may want to replace that file as well. Just a thought anyways
Click to expand...
Click to collapse
That's essentially what I did in InspirePhacopida and that works on my phone, but I was able to do it on my wife's stock phone by just adding an APN, so who knows?
Hi Gene and beerbaronstatic,
First of all thanks for the assistance.
I guess that for me to do that I'll have to flash the ROM via rooting and whatnot or did you modify a file within the RUU so I can just run that and flash it as if I was the regular ROM?
Regards
Robert
bobbypty said:
Hi Gene,
First of all thanks for the assistance.
I guess that for me to do that I'll have to flash the ROM via rooting and whatnot or did you modify a file within the RUU so I can just run that and flash it as if I was the regular ROM?
Regards
Robert
Click to expand...
Click to collapse
No. You can't modify an RUU zip. They are signed by HTC. If you modify one, or make an unsigned one from scratch, then you must have S-OFF so that the hboot loader ignores the signature (or lack thereof).
This is Gingerbread 2.3.3 on the Inspire NOT Froyo 2.2
Thanks anywho....
Yes. The WIFI tethering option WILL NOT work on the stock Gingerbread ROM of the HTC Inspire, this will only work with stock Froyo by manually setting the APN.
If you want to have the WIFI tethering option with GB, then you will have to root the phone to install a custom ROM based off the Desire HD which is the European version of the Inspire. Coredroid is the only one I've used so far but right now I went back to stock Froyo.
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.