Almost every text I send fails.. I have full bars, go to send a text and then after a while the text fails to send..(they still end up receiving it anyway,but its a huge issue because the phone constantly alerts that my text failed). I can make calls just fine. Is anyone else having this problem with this ROM? IS there a fix? I'm 99% sure its installed just fine and my hardware is impeccable.
I had this before on ee odin then reflash to bonsai it should fix it. Btw i dont have this on bonsai
Sent from my SPH-D700 using XDA App
If you're using gingerbread theme, try this.
If not, do what the post says above and it should fix the problem. If you're wanting to try something easier first, simply try reflashing the ROM. But I think it does occur to many people that have a problem during switching Modems in Odin.
The same thing is happening to me, but Im not using a custom rom. I'm using stock D118
I had an issue with bonsai where my messages would stick on "sending". I rebooted the phone and the problem hasnt come back until i flashed v2.0 of bonsai..i rebooted again and all is well. for safety measures i reflashed the dk28 modem...i replied to your post in the bonsai thread and said that you can also odin the DI18 modem which some people have said works better than DK28 and the internet speeds are much better..
hmm darn, well i just restored to the point before i flashed bonsai and flashed nebula 1.0.7 instead and its working perfectly
Having the same radio problems with this one as Midnight v 3.1, I've tested both and can hardly send a text to save my life. I go to send it times out and fails then i get the error message did not send, yet they still recieve it. Its frustrating because I really wanted to run either of those two. Not sure why but these two must be similar causing the same problem. (in midnight theres a huge thanks to bonsai dev's so just assuming its a similar Rom)
coke32 said:
Having the same radio problems with this one as Midnight v 3.1, I've tested both and can hardly send a text to save my life. I go to send it times out and fails then i get the error message did not send, yet they still recieve it. Its frustrating because I really wanted to run either of those two. Not sure why but these two must be similar causing the same problem. (in midnight theres a huge thanks to bonsai dev's so just assuming its a similar Rom)
Click to expand...
Click to collapse
I've been restoring to the point of when i just flashed stock dk28 and reflashing both these roms and still every other text fails to send. should i try to odin back to stock dk28 and reroot? does that do a more effective wipe then restoring back to stock dk28 with root? (because i made a backup right after i did the oneclickrootcw3)
well i odin'd back to stock and rerooted and reflashed midnight and im still failing every other text Im a heavy texter and like to go fast and often when im going.. when every other message is failing it becomes impossible to talk to someone. calls work fine.
Related
hi all, been following the Epic forums for sometime, finally decided to start getting involved
Im experiencing an issue with EB13. when it first came out I Odined EB13, everything worked great. Since then I have ran into the same issue every time I switch ROMS. I will flash the new rom, about half the time it works great. The other half I get no connectivity at all, and the UI is sluggish. Going into about phone, I see that my baseband is unknown, and my hardware version is unknown.
I can usually get it to connect after re-flashing and re-flashing the rom a few times.
Also, noticed that once I get it to actually connect and I get "bars", I will of course then do a fresh Nandroid, after a full nand backup the issue reappears.
Anyone know what this could be? weird thing is just that its so random. I can get it to work most of the time, just have trouble when switching roms.
Set up:
CWM3.0.0.6/EXT4
Just flashed SyndicateROM today.
EB13 (sometimes)
FIXED
FIXED. all the computers in my home are Macs so odining the modem again is not a quick fix option.
Booted into CWM3 and Fixed Permissions.
Booted up and connected.
Interesting stuff
I've been experiencing the exact same problem as the OP, but for me, running fix permissions in CWM (2.5.1.0) doesn't (always) solve the issue.
It seems to happen anytime I flash a zip from CWM, and goes away randomly (usually after sever flash attempts and modem restores with Odin).
Really hoping someone has an idea what's causing this issue, because it makes flashing things very tedious knowing half the time I'm gonna be stuck with a useless phone until I can get the modem working again.
I'm wondering if it's somehow a hardware issue, since it doesn't seem to affect everybody.
If it helps, I have the stock deodexed EB13 ROM with the Genocide 0.3a kernel.
I'm definately thinking its a cwm issue.. ill even just do a nandroid backup for kicks, reboot and it will do it sometimes.. eventually I might odin back to eb13 and reflash cwm and custom rom and see if I can get it to go away
Sent from my SPH-D700 using XDA App
DrKaotica said:
I'm definately thinking its a cwm issue.. ill even just do a nandroid backup for kicks, reboot and it will do it sometimes.. eventually I might odin back to eb13 and reflash cwm and custom rom and see if I can get it to go away
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Let me know if that works for you, because it happens to me all the time, and it's really annoying.
There also doesn't seem to be a simple way of fixing it.
Seems to just randomly go away as suddenly as it comes on.
Okay, so I just odined back to stock EB13 and I still have modem issues.
Currently going all the way back to DI18 to see if that fixes things, but is it safe to assume it's a hardware issue if even Odin doesn't fix it?
Okay, so the unknown baseband issue is back for me, and I seem to have made some headway on what causes it.
I had just tried to initiate a ROM backup in ROM Manager, but it hung while rebooting into CWM (on the Samsung Boot Logo).
I think I might have been doing something with ROM Manager last time it happened as well.
Can anyone who knows more about this stuff than I do think of a reason it'd happen when using ROM Manager?
I'd very much like to nip this issue for good, because it's making it hard to justify using CWM/root if I'm gonna keep losing the phone part of my phone.
Can I bump this? My battery died, and when I turned it back on, I have the unknown baseband, unknown hardware problem. I've been googling all night, and haven't found a solution.
I have been running ERA Legendary v3 on the EI22 Modem for a few weeks with ACS Recovery that I've had installed since it came out.
Any help would be awesome.
---------- Post added at 07:28 AM ---------- Previous post was at 07:17 AM ----------
And I've tried flashing modems/roms and odining modems/roms. Even Heimdalling modems/roms. No luck. I've mainly tried ec05 and up. I will try older ones right now, if I can find them.
so i just downloaded the update from my phone, and i'm not 100% sure what went wrong. i downloaded a zip update to the ec05 modem and updated from the eb13 one. then i just flashed the 1.1 update like i did with the rest. except now my phone is super slow and keeps freezing. also, opening the browser and facebook and essentially any other apps keep crashing my phone. i've tried different settings with setcpu, but that didn't do any good. now i can't even send or receive text messages. i've tried reinstalling and that didn't work either. any ideas?
Happened to me to. I odin back to stock, then did the legit update to ec05 throught google, did the one click cwm 3, and flashed the rom. Works fine now.
You may be one of the few people with a freak phone that doesn't like EC05 too. There seems to be no harm in sticking with EB13, try flashing back to it.
K0nane has posted several times that the stock kernel (twilight) sometimes freaks the phone out. He suggested flashing a different kernel and that has fixed several peoples problems similar to this.
Atlienzz said:
K0nane has posted several times that the stock kernel (twilight) sometimes freaks the phone out. He suggested flashing a different kernel and that has fixed several peoples problems similar to this.
Click to expand...
Click to collapse
This is right. If you are having issues flash to Vision kernel.
EDIT: Problem Solved
Downloaded Stock Sense 2.2 from here, flashed into that, Reset Data Connection in EPST (Like Here), rebooted and flashed back to CM7. Simple as that!
I realize this may be a bit of repeat thread, But I haven't really got an answer yet.
For reference: I'm running Cm7
Sometime during the day last Thursday, I lost the ability to receive texts. I can send texts, as well as make/receive calls, and data works fine as well. I just can't send them.
Things I've tried include:
Flashing to Stock Sense 2.3
Updating PRL/Profile
Manually installing Radio/PRL/Profile updates
Flashing to a fresh CM7 Install
I also feel like I should add that I tried to open EPST to reset data, but when I enter the code(##3282#) in Phone I get nothing.
Any help would be appreciated, and I'll be on until late tonight as to not keep responders waiting. Thanks.
Go to stock rooted 2.2 or MikG or a custom ROM with the old EPST, the new EPST features less. I just do it on stock 2.2 to avoid any problems when doing the restore. My radios are working, did you flash them individually?
Sent from my PC36100 using XDA Premium App
Okay
Downloading MikG right now, going to give that a try.
And I think that may be part of my problem, I just can't get the radio to update. I've attempted to install them as a combo, and separately in both ClockworkMod and Amon_RA several times. I never get any error messages, it just installs, and tells me to reboot, but nothing ever changes.
That's why I'm going to try to Reset Data in EPST. I had heard elsewhere that my MSL doesn't match what Sprint has on file, or something like that, and that resetting data should fix this.
Anyway, Thanks a lot, I'll be back in 10-15 minutes with results!
Partial Success
As soon as Stock 2.2 booted up and got to setup, the texts started pouring in. Not sure what caused this, but it seems at this point like a Gingerbread issue. For good measure I opened EPST and did a data reset and updated PRL/Profile. I'm about to flash back to CM7 and see if the changes carried over.
It worked! It was that simple all along! Thank you! Just sent myself a text via email that I received on CM7!
foxtrotftw said:
Downloading MikG right now, going to give that a try.
And I think that may be part of my problem, I just can't get the radio to update. I've attempted to install them as a combo, and separately in both ClockworkMod and Amon_RA several times. I never get any error messages, it just installs, and tells me to reboot, but nothing ever changes.
That's why I'm going to try to Reset Data in EPST. I had heard elsewhere that my MSL doesn't match what Sprint has on file, or something like that, and that resetting data should fix this.
Anyway, Thanks a lot, I'll be back in 10-15 minutes with results!
Click to expand...
Click to collapse
If you rebooted in between installing each one, the radios should've updated. You might not notice any difference, but it should work. Glad to hear that your problem is solved!
I've searched, so please forgive me if there's something similar. I've found nothing that solves my issue. I have freshly installed cm9 a couple days ago, and then shortly after upgraded to 10. That is where my woes began. Friends and fam started telling me that my phone would ring onced and straight to vm. I get texts in huge batches, a lot of repeats, and very unreliably. I've installed a few other different roms and kernels to no avail. And yes I've wiped everything, every time. My 3g/4g/wifi are fine.. just texts and calls messed up. What's happeninggg =[[[[. Is my radio corrupted or something? How can I fix this?
First: This is a support question and should have been posted in the Q/A forum.
Second: You should probably not install the RC of CM9, since CM9 is now stable and has an official release. http://get.cm/?device=epicmtd&type=stable
Third: Before flashing CM, use Odin to go back to stock and test out SMS, MMS and calls. If all works well, then you can Odin flash CWM, pull the battery, 3-finger boot to CWM and then flash CM9 stable.
If testing SMS, MMS and calls do not work properly on stock, then you need to go to a Sprint store and get them to fix it. Just leave it on the stock rom to bring it in.
Moved
Sent from my SPH-L710 using xda premium
Hi all,
I recently rooted my SPH-l710 that was updated to 4.3 using this method: http://honai-android.blogspot.com/2013/11/how-to-root-galaxy-s3-sprint-sph-l710.html
Everything worked well and then I flashed the CM11 ROM (snapshot) and again, everything was working well, I could make calls, send and receive text messages and had mobile data. This afternoon, I found out that I had not been receiving text messages, I could send them and people received them, but when they replied, they never came) through on my end. I rebooted, nothing changed, then I did a factory data reset, again, same issue. Then I flashed this stock ROM (deodexed): http://forum.xda-developers.com/showthread.php?t=2541900 and still had the issue. After installing the stock ROM, I updated the PRL profile and I'm still having the issue. At this point, I have no idea what else I can do the fix this issue and I'm hoping someone here can help me.
Thanks in advance.
Did u try reflashing the modem? If that doesn't work its something on sprints end.
Sent from my SPH-L710 using Tapatalk
I'm shocked that root method even worked for you...did you update your profile as well and then reboot the phone when on stock rom? might wanna get back on the stock rom and try...other things you may wanna try when all else fails, reflash back to completely stock 4.3 which you can do by using my guide in my sig for bricked phones, which you're gonna need to do if you have to go to sprint for it, they won't touch it rooted
I did not try flashing modem, I was under the impression that the modem deals with data and since I had no problems there I didn't bother with it. I did try rebooting after going back to stock rom, but that didn't help. When I first installed cm11 I was having problems with getting Google Voice to work, but I restored the back up a CM 11 when I first installed it and tried google voice again. This time it works and I'm able to send and receive text messages and access voicemail through the app so as long as I don't come across any more issues I'm happy with how it is now. I appreciate all the pointers and if I ever have to go back to stock, I'll refer to this post, thanks.