• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Not Receiving Texts

izander

Member
For the past 2 weeks, I thought it was just chance that no one had texted me back, but I think something with my Rooted/S-OFF Evo V 4G has gone awry. I'm currently on the SonySan CyanogenMod 9 (Android 4.0.4) with (H-Boot Eng 1.04) and I think my SnapChat is a little messed up as well, the FFC's preview is a very distorted image, but after the picture taken, nothing is distorted, but I haven't received many pictures in return when people say they respond. I have no problem sending texts, calling, or receiving calls, but texts are never received. I've flashed new ROMs with clean installs and factory wipes, but nothing has worked. I tried ##VIRGIN# and ##MSL# but they don't work on my ROM. Any ideas?
 
Well keep in mind, I'm using a phone that is basically an Evo 3D (even more so with the downgraded H-Boot and an Evo 3D CDMA ROM which is using VM's service) so I'm not sure how much help they'll be, but I will be sure to trudge through the customer service when I wake up later today. Thank you again for your advice!
 
No Problem Izander

A good rep can be a hard thing to get a hold of. If you get a seasoned rep in the tech department they should be able to do what they need to do in less than 15 minutes.

Just don
 
I'm having the same problem running sprint Roms, and VM told me there were no outages in my area.

Any Sprint rom either needs a port specifically for Virgin or have a separate mms fix otherwise it won't work because of the screwy way that Virgin handles mms. This is one of the primary reasons why people flash Sprint phones to Boost and not Virgin even though they're both owned by Sprint and run on the same network. :rolleyes:
OB
Edit: moved to ATR
 
Any Sprint rom either needs a port specifically for Virgin or have a separate mms fix otherwise it won't work because of the screwy way that Virgin handles mms. This is one of the primary reasons why people flash Sprint phones to Boost and not Virgin even though they're both owned by Sprint and run on the same network. :rolleyes:
OB
Edit: moved to ATR

I'm not taking about mms, I know virgin mobile mms is screwy
 
VM Customer Service couldn't help at all, or their expert service either. I didn't have the heart to tell them I had S-OFF, Rooted, Downgraded H-Boot, Updated PRL, and a new Radio, etc, or they might of got mad haha.
 
My mistake, I thought you were talking about mms problems. I have used this rom without any problems although I used the jbear 1.50.5050 Hboot as that's what was recommended. I don't think that would have any effect on your problem though.
OB
 
I originally started off with the JBear method, but used the thread of basically turning my phone into an Evo 3D which told me to downgrade my H-Boot to make it more compatible, and it's worked on every one I've used
 
i had the same issue.... i had to return to pretty much bone stock by this i mean original hboot recovery and rom then call vm or try ##25327# after re-stock u have to b stock for the provider codes to work if this doesnt work then u may need a new phone and a fresh start good luck!!
 
Really? Changing the hboot fixed your SMS issues?

That's good to know! Thanks for the information, sellers. I never suspected that could work.
 
I know this is late, but have you tried the "update profile" through a stock (or stock-based) ROM? Sometimes that works. Other than that, the new radio (released March 13th) delivered an old message to me immediately upon booting up with it and updating my profile.
 
Just a bump, I fixed this by changing to the 1.04 hboot.

Seriously?!?! I don't understand this? Bootloader has nothing to do with your data signal... Are you sure that you didn't change a radio along with the bootloader? Can you post a link to the file that you updated with? I'm not trying to say this isn't true, but I'm just curious if you changed more than your hboot because the hboot should not make a difference to a problem like that :)
 
I'm am 100% sure that all I did was flash the ENG hboot. No different radio, no different ROM, no nothing. Just the hboot. And I started having the issue when I flashed a different hboot. I dont think that's a coincident.

Edit: I know it sounds weird and its hard to believe, but try it yourself. That's the only way to see if it really works.
 
I'm am 100% sure that all I did was flash the ENG hboot. No different radio, no different ROM, no nothing. Just the hboot. And I started having the issue when I flashed a different hboot. I dont think that's a coincident.

Edit: I know it sounds weird and its hard to believe, but try it yourself. That's the only way to see if it really works.

Ok thanks I will flash the eng. Hboot 1.04 and reply back thanks and nice to see you on this thread
:D
 
I'm am 100% sure that all I did was flash the ENG hboot. No different radio, no different ROM, no nothing. Just the hboot. And I started having the issue when I flashed a different hboot. I dont think that's a coincident.

Edit: I know it sounds weird and its hard to believe, but try it yourself. That's the only way to see if it really works.
We've been round and round on this over at XDA and no one has ever explained how the bootloader can have any effect on anything after Android is booted. For Android itself the bootloader is out of the picture once the kernel is booted.

Perhaps formatting cache and dalvik after changing the hboot helped resolve your issue.

ramjet73
 
We've been round and round on this over at XDA and no one has ever explained how the bootloader can have any effect on anything after Android is booted. For Android itself the bootloader is out of the picture once the kernel is booted.

Perhaps formatting cache and dalvik after changing the hboot helped resolve your issue.

ramjet73

I didn't format anything. That wouldn't make a difference as I tried a clean flash of 3 different ROMs with no change. All I did was changed the hboot. Doesn't make sense to me either.
 
Back
Top Bottom