When Install non Sense roms I'm not able receive or make calls everything else works fine. I'm US T-Mobile unlock running 2.41.617.3 fireware. I'm putting it hear as other have the problem some solved some not. Others reported running RUU then flash Rom works, not me I feel it something about data format before install.
No one has a take on this
Maybe you forgot to set Google dialer as your default phone app.
Related
I've recently switched to MIUI 1.3.25 GB build, and love it. Best ROM in my opinion. But MMS doesn't work for whatever reason (mind you my EVO is on MetroPCS). Before it was working fine on the Sense Rom, but the Sense Rom is garbage compared to MIUI GB.
Anyways so I found this MIUI 1.29 MetroPCS Edition build by "Bloody". I installed it and MMS works fine, but I honestly would like to keep the latest MIUI build. So does anyone know if there will be a MIUI 1.3.25 MetroPCS build?
EDIT: I got a reply from bloody, I guess apparently you should be able to install his mms script he built to a working MIUI Rom and it should work. (which I tried but didn't work, so I'm guessing I did something wrong. But I'll keep messing with it til I figure it out). Will keep this thread up-to-date so if anyone else has the same problem.
Ok so I tried this agian and made some progress. I restored my bkup of MIUI 1.3.25 GB Rom, I guess if you wanted you can just do a fresh install.
Second, flash "MetroPCS_Web_MMS_Evo_AOSP_v4.zip" file. Now once you reboot after flashing, you'll notice that the MMS app is gone and probably wondering what the heck happened. Well the new MMS app is installed but you just don't see it.
Deleted the previous MMS app which at this point should look like a missing app cause the os can't find it. Using Root Explorer (you can use any other app that can do the same thing) I went to system/app/mms.apk and intalled it. Its gona ask if you want to overwrite the current mms app, just hit ok. Now reboot and you should now see the MMS app appear back on the screen. Click on it, and you'll notice its not as nice as the original MMS app that comes with MIUI 1.3.25.
This is as far as I've gotten I tried sending my self a pic msg but never received it. So I'm redoing the entire process to see if it works then.
Ok here it is, I have everything working. Remember this is for EVO's on MetroPCS, if you're still on sprint, they you should be fine with just flashing the latest MIUI on your phone.
This only works if your phone is already provisioned and already on MetroPCS.
1. Install latest MIUI using their steps that they've provided
2. Once your phone is booted, mount the SDcard and copy the MetroPCS Evo AOSP MMS & Web Script v4 to the root of the SDcard.
3. Flash the zip file, you should see it deleting and installing some files.
4. Once you've rebooted, you'll notice the original MMS app gone. Just reboot your phone again.
5. When booted up for the final time, the MMS app should appear again. When you click on it, you'll notice its a different app from the original. The original is cool but, this one still works great.
Also you'll notice at the top where it usually would say SprintPCS, now it says MetroPCS.
This is for EVO's with MIUI on MetroPCS that do not have mms working. This should fix it. Hope this helps.
Thanks to Bloodykiller86
Hi,
I have a big problem with AOSP 4.0.3. When I flash a ROM with this build, my data connection always get lost/cut, when I switch the screen off. In this time it is not possible to call me or to send me a massage. When wifi is activated, internet data works, but of course calls and massages not!
I really tried all RADIOs. I flashed them via fastboot and CWM. I also tries different bootloaders, don´t no really why.
I completely set my phone back with a stock google img and locked my bootloader and repeated the whole process. But when I flash a ROM with 4.0.3 base, the same problem appears.
When using AOSP 4.0.2 based ROMs everything works fine!
I have no idea what goes wrong, or what to do to fix it. I think the only option is to wait until Google releases an official update.
Has anyone the same problem her? Or does anyone have an explanation?
Thanks.
So I have the interesting problem with Google services. When I am on wifi I have no issues what so ever. When I am just on cell data Google search doesn't work, Gmail doesn't, ingress doesn't, contacts don't sync, play store won't open etc. All other internet works perfectly fine though. I am currently usinuslatest viper Rom. And am on the latest firmware and on AT&T. I have tried a couple other roms and same problem...except MIUI. Everything on MIUI worked perfectly fine no issues what so ever...Does anyone have any ideas on what the issue could be.
malac0da13 said:
So I have the interesting problem with Google services. When I am on wifi I have no issues what so ever. When I am just on cell data Google search doesn't work, Gmail doesn't, ingress doesn't, contacts don't sync, play store won't open etc. All other internet works perfectly fine though. I am currently usinuslatest viper Rom. And am on the latest firmware and on AT&T. I have tried a couple other roms and same problem...except MIUI. Everything on MIUI worked perfectly fine no issues what so ever...Does anyone have any ideas on what the issue could be.
Click to expand...
Click to collapse
Have you tried GPE roms? Did you make sure you did a full wipe when you hop around sense roms? What about AOSP roms, do they have the same issue? I never faced this issue on my M8 though
I have TWRP on my phone. I think it's the latest. I do a factory reset and then wipe the system partition then flash. I tried an aosp Rom and had the same problem not sure about GPE based Rom though. I think MIUI is GPE based though. I will try a GPE Rom though and see.
malac0da13 said:
I have TWRP on my phone. I think it's the latest. I do a factory reset and then wipe the system partition then flash. I tried an aosp Rom and had the same problem not sure about GPE based Rom though. I think MIUI is GPE based though. I will try a GPE Rom though and see.
Click to expand...
Click to collapse
All you need to do is a factory reset.No need for a system partition wipe.
malac0da13 said:
So I have the interesting problem with Google services. When I am on wifi I have no issues what so ever. When I am just on cell data Google search doesn't work, Gmail doesn't, ingress doesn't, contacts don't sync, play store won't open etc. All other internet works perfectly fine though. I am currently usinuslatest viper Rom. And am on the latest firmware and on AT&T. I have tried a couple other roms and same problem...except MIUI. Everything on MIUI worked perfectly fine no issues what so ever...Does anyone have any ideas on what the issue could be.
Click to expand...
Click to collapse
Known issue if you try to run some custom ROMs on AT&T. Something about build.prop on Euro ROMs breaks Google services on AT&T LTE.
Flashing the US Dev Edition firmware (3.28.1540) and the 4.4.4 Sense ROM by Wonders_Never_Cease should fix it:
http://forum.xda-developers.com/att-htc-one-m8/help/lte-connection-issues-3-28-401-7-t2913168
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
OK I flashed the firmware from that link you posted. I now have a problem. I had relocked my phone to flash firmware before and I am not sure how to unlock it again. I was able to reflash a recovery because the rom that was installed on it booted far enough for me to adb shell into it. I may not get so lucky next time though. I am not sure where my oem_unlock.bin file is though. Can I get another from HTC?
NVM I got it squared away. Just dedid the stuff for the htcdev site and got it sent again.
Hello all,
I used to have CM11 M12 on my SPH-L710. when I first installed it, I didn't have MMS or LTE. However, I fixed it using this fix from MopedRyder: http://androidforums.com/threads/mod-universal-lte-virgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/ and I fixed the MMS with the fix from moonknightus on that page. However, when I flashed liquidsmooth v4.0 to my phone, whenever I flashed the MMS fix, the phone would not boot. Does anyone know how to fix this? It says it should work with all AOSP ROMs. The LTE fix works, but not MMS.
This problem persists on Android Ice Cold Project v8.0. Using Hangouts as the default messaging app allows MMS to work, but stock messaging doesn't seem to want to work with Lollipop. Anyone know of a fix?
Powered_By_Linux said:
This problem persists on Android Ice Cold Project v8.0. Using Hangouts as the default messaging app allows MMS to work, but stock messaging doesn't seem to want to work with Lollipop. Anyone know of a fix?
Click to expand...
Click to collapse
You shouldn't need the MMS fix on lollipop, I didn't. Everytime I try to apply the MMS fix mine would not boot either, but just applying the APN fix allowed me to send MMS's in the default text messaging app. I'm on Boost Mobile. Have you tried flashing a TouchWiz ROM on there updating PRL and profile and then flashing the lollipop ROM? If you try this make sure you wipe internal SD each time.
Yes, I have tried it without the fix. However, the message wouldn't download. I cleaned up the phone before a new flash using the feature in PhilZ touch home recovery. I haven't tried flashing a touchwiz ROM to update anything. I'm pretty happy with using hangouts as the default messaging app, but is there any other advantage for updating PRL and profile? I've configured my ROM the way I like it. Will making a Nandroid backup, flashing the touchwiz ROM, and restoring the backup allow me to have the updated PRL and profile?
Powered_By_Linux said:
Yes, I have tried it without the fix. However, the message wouldn't download. I cleaned up the phone before a new flash using the feature in PhilZ touch home recovery. I haven't tried flashing a touchwiz ROM to update anything. I'm pretty happy with using hangouts as the default messaging app, but is there any other advantage for updating PRL and profile? I've configured my ROM the way I like it. Will making a Nandroid backup, flashing the touchwiz ROM, and restoring the backup allow me to have the updated PRL and profile?
Click to expand...
Click to collapse
Updating the prl and profile will just make sure everything is up to snuff and communicating with towers and provider, in Philz make a nandroid, wipe cache, wipe internalSD, wipe to install new ROM. Flash TouchWiz ROM, update prl and profile, go back into Philz, wipe everything including internalSD, restore nandroid.
Thanks! Do you know where to get a good touchwiz ROM?
Wicked S5 is the best TouchWiz ROM I've run:
http://forum.xda-developers.com/showthread.php?p=57728620
Make sure you can send and receive MMS on there before you go back to Liquid. That way if there is something you need to do per carrier instructions if it doesn't work, you'll have access to dialer codes.
Thanks. I'll get around to checking it, but I'm a little hesitant to because everytime I would recieve an OTA (before I rooted/installed custom ROMs), my phone's coverage would stop working, and I'd have to contact Virgin Mobile and reactivate my phone. Now that I've burned those bridges installing ROMs, I'm a bit hesitant to do something like that. Do you think this will happen again, or is that a stock only problem? Getting stock MMS to work now isn't a high priority (I'm fine using Hangouts), but I figure I'll have to update my modem, PRL, profile, or something else sooner or later, and I'd like to figure this out.
Powered_By_Linux said:
Thanks. I'll get around to checking it, but I'm a little hesitant to because everytime I would recieve an OTA (before I rooted/installed custom ROMs), my phone's coverage would stop working, and I'd have to contact Virgin Mobile and reactivate my phone. Now that I've burned those bridges installing ROMs, I'm a bit hesitant to do something like that. Do you think this will happen again, or is that a stock only problem? Getting stock MMS to work now isn't a high priority (I'm fine using Hangouts), but I figure I'll have to update my modem, PRL, profile, or something else sooner or later, and I'd like to figure this out.
Click to expand...
Click to collapse
Burned what bridge? They don't care, it's your phone, you bought it. If you have ANY TouchWiz ROM and you call to trouble shoot a problem you can use dialer codes if need be.
I was under the assumption that once you rooted or installed a custom ROM you were on your own. In that case, I'll install a touchwiz ROM with no worries!
Powered_By_Linux said:
I was under the assumption that once you rooted or installed a custom ROM you were on your own. In that case, I'll install a touchwiz ROM with no worries!
Click to expand...
Click to collapse
You're really on your own with AOSP ROMs, keep in mind if you go the route with WickedS5 AND need to call VirginMobile, don't use the S5 settings, use the normal one, if you read the thread you'll see what I'm talking about
I've just rooted and installed Viper ROM on my ATT HTC m9 and everything works great except I can't receive phone calls. The phone never even rings. I've also flashed ICE and ARHD with no success receiving phone calls. If I restore to a TWRP backup of stock the phone works perfectly so it's obviously something to do with the ROM.
I've checked the other posts on here and none of the fixes have worked, yet. I wanted to try to RUU but whenever I run the RUU application (windows 8.1) the progress bar to initialize the setup completes and the program closes. It never does a flash. I've tried running as admin, disabling services, and running in Win7 compatibility mode to no success.
Do any of you have any ideas on either of these?
mdomino said:
I've just rooted and installed Viper ROM on my ATT HTC m9 and everything works great except I can't receive phone calls. The phone never even rings. I've also flashed ICE and ARHD with no success receiving phone calls. If I restore to a TWRP backup of stock the phone works perfectly so it's obviously something to do with the ROM.
I've checked the other posts on here and none of the fixes have worked, yet. I wanted to try to RUU but whenever I run the RUU application (windows 8.1) the progress bar to initialize the setup completes and the program closes. It never does a flash. I've tried running as admin, disabling services, and running in Win7 compatibility mode to no success.
Do any of you have any ideas on either of these?
Click to expand...
Click to collapse
I had this happen too and it's still kind of a mystery as to what causes it. Did you see this thread? My posts in there are everything I did to fix this, but I can't say exactly what step fixed it. http://forum.xda-developers.com/one-m9/help/unable-to-receive-phone-calls-t3137209
I haven't had the issue in about three weeks now, so whatever it was is apparently fixed. I'm on ICE 3.0.1 with no issue. A definite short-term fix is to do steps 2 or 3 of post #3 in the above link. I suspect it has something to do with either the radio not reading the default.xml file properly or the default.xml file not containing the correct voLte settings.
jollywhitefoot said:
I had this happen too and it's still kind of a mystery as to what causes it. Did you see this thread? My posts in there are everything I did to fix this, but I can't say exactly what step fixed it. http://forum.xda-developers.com/one-m9/help/unable-to-receive-phone-calls-t3137209
I haven't had the issue in about three weeks now, so whatever it was is apparently fixed. I'm on ICE 3.0.1 with no issue. A definite short-term fix is to do steps 2 or 3 of post #3 in the above link. I suspect it has something to do with either the radio not reading the default.xml file properly or the default.xml file not containing the correct voLte settings.
Click to expand...
Click to collapse
Thanks! I followed your steps and got it working. It seems from what you and Venom support said that the problem is with going directly from the ATT RUU (5.0.2) to a custom 5.1 ROM. Once I flashed the developer edition RUU and edited the default.xml I was able to flash ViperROM and have calls working without any further tinkering.
Thanks a ton!
mdomino said:
Thanks! I followed your steps and got it working. It seems from what you and Venom support said that the problem is with going directly from the ATT RUU (5.0.2) to a custom 5.1 ROM. Once I flashed the developer edition RUU and edited the default.xml I was able to flash ViperROM and have calls working without any further tinkering.
Thanks a ton!
Click to expand...
Click to collapse
Thanks for the feedback. That's weird though because I couldn't even receive calls on the developer edition.
I couldn't make calls until editing the default.XML in developer edition. I'm still not sure how it works but I'm happy either way!
Sent from my HTC One M9 using XDA Free mobile app