Will there be a MIUI 1.3.25 MetroPCS build?? - EVO 4G Q&A, Help & Troubleshooting

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

Related

Yet another ics mms post

I am running 'mimicry v1.5.0 and it has been the best rom I have run on any device. The one issue I have, and it seems to be a common one for ics, is mms just doesn't like me. I have went through the apn settings and have tried everyone I can find for tmobile but no luck. Now for the point of the post... can someone tell me what roms running gb have mms abilities? Another ics rom would be great but something tells me that it won't happen and unfortunately I have to use mms for work.
Thanks for the help
Sent from my G2 running Mimicry 1.5.0
I've always found that I can't retrieve MMS' on any signal apart from plain old GPRS.
If i have Wifi, Edge, 3G or 3.5 I can't download them, it just times out.
I can't seem to send or receive no matter what band is in use. Which rom are you using?
Sent from my G2 running Mimicry 1.5.0
alarmdude9 said:
I can't seem to send or receive no matter what band is in use. Which rom are you using?
Sent from my G2 running Mimicry 1.5.0
Click to expand...
Click to collapse
I was using Elitemod, but am intalling Mimicry as we speak. I'll test an MMS later today and let you know.
This was also the case for me on Virtuous roms too. And the stock ROM if i remember rightly.
I am using o2 in the UK, this might be just be a network setting rather than ROM setting though.
Thanks for giving it a shot. Let me know what you find. Most of what I have read says its an apn setting but I have tried all the ones I can find for tmobile.
Sent from my G2 running Mimicry 1.5.0
I just had this problem and restoring the stock messaging app fixed it...still looking for a permanent solution...
I still have the same set up. Won't retrieve on anything other than G still on Mimicry.
Thanks for the info. As far as I am aware I am on the stock mms app I think. And now to find a way to force my phone to use gprs.......
Sent from my G2 running Mimicry 1.5.0
Does anyone actually know why some people have the mms "bug" in ics roms when others don't even when the apn numbers are the same ones from a gb rom? Possibly carrier specific?
Sent from my G2 running a random rom.
I have the same bug on blackout 3.0 and made a lot apn settings but there it still won't send mms. Need a solution.
Is Blackout an ics rom or a gb rom? As far as I have read it is something that effects all ics roms but not gb roms for certain people.
alarmdude9 said:
Is Blackout an ics rom or a gb rom? As far as I have read it is something that effects all ics roms but not gb roms for certain people.
Click to expand...
Click to collapse
I am having all of these issues and more...very frustrating... Im on the nightly flinny jb build and need to post on there but running the noob ladder.
I have mimicry 1.5 and i use GO SMS Pro.. it works fine for me.
Yeah I tried gosms and no love there. Seems like there is a lot of factors that effect it. I moved back to a gb based rom and keep trying as I see new things for ics and try them but still no love for me.
Sent from my G2 running the random rom of the day.
I may have found something that effects the mms issue. Decided to goof around and flash a mess of roms tonight and see what they were like. I have the .15 radio and all the gb roms work perfect for mms. ICS and JB no luck. After doing a mess of reading I have a feeling it could have to do with the radio version installed possibly. Is anyone having the problems with mms on a .19 radio?
I'm running. 19 radio with edkeys rils and have never had any mms issues.
Sent from my HTC Vision using xda app-developers app
That's what I was thinking. I get the radio thing but I'm still trying to wrap my head around the edkeys thing.
Sent from my G2 running the random rom of the day.
Just flash the files in his post
Sent from my HTC Vision using xda app-developers app
Learned a long time ago never flash what you don't understand. Had to buy my first android phone 3 times (i'm a slow learner).
Warbuff said:
Just flash the files in his post
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
alarmdude9 said:
Learned a long time ago never flash what you don't understand. Had to buy my first android phone 3 times (i'm a slow learner).
Click to expand...
Click to collapse
Alrighty bro let me help.
First download the .19 radio with RC data from this link https://www.dropbox.com/s/0qsobli3v07qbxw/VISION_RADIO_RCDATA_12.62.60.27_26.13.04.19.zip
Rename file to PC10IMG.zip
Put file into root of SD card
Reboot into bootloader and it should see the file. Use volume up to press yes
After its done you should be on the new radio. Make sure to remove the Zip from your sd card now.
now to flash the RILs download Edkey's RILs from here https://www.dropbox.com/s/5m94hm0fv..._26.13.04.19radio_ril_gps_so_updater_v3.1.zip
Reboot to Recovery. Make a backup.
Flash the previously download zip.
Wipe Cache and Dalvik Cache. And also wipe EFS partition with this http://dl.dropbox.com/u/17578272/vision_wipe_efs-signed.zip
Reboot and you should be set.
Keep in mind that if you already have the radio with the RC data you can also flash the RILs during the setup process for Mimicry.
Let Me know if you have any questions.

[Q] Cyanogenmod 10.0 Texting error 34

I recently upgraded to Cyanogenmod from the vanilla android of my Sprint S3. I've had no issues with it since I've gotten it running until suddenly today it refuses to send text messages. It receives them just fine but for some reason refuses to send? I found another thread on this but it just confused me more and seemed to be talking about non CDMA phone (an Italian Evo 3d) and it doesn't make sense for my issue... yet it seems to be the same.(Reference)
Synopsis:
1. I could send and receive fine for an entire week til today.
2. I can still receive texts but cannot send them.
3. Sometimes it will send a single text through? That could just be a fluke.
4. Turning it off and back on didn't help.
5. It says Error Message 34
Thanks!
Try fixing permissions in CMW
Sent from my SPH-L710 using xda premium
crowbahr said:
I recently upgraded to Cyanogenmod from the vanilla android of my Sprint S3. I've had no issues with it since I've gotten it running until suddenly today it refuses to send text messages. It receives them just fine but for some reason refuses to send? I found another thread on this but it just confused me more and seemed to be talking about non CDMA phone (an Italian Evo 3d) and it doesn't make sense for my issue... yet it seems to be the same.(Reference)
Synopsis:
1. I could send and receive fine for an entire week til today.
2. I can still receive texts but cannot send them.
3. Sometimes it will send a single text through? That could just be a fluke.
4. Turning it off and back on didn't help.
5. It says Error Message 34
Thanks!
Click to expand...
Click to collapse
You could try fixing permissions, or backing up your current ROM, flash a touchwiz stock one (rooted of course), and updating your profile/prl. If that doesn't work use the ##7282# or something like that (look it up please, I can't remember the code right now) in the touchwiz ROM. Those may fix it.
Don't forget to backup!
------------------------
Sprint Galaxy S3 :trooper:
Whiplashh said:
You could try fixing permissions, or backing up your current ROM, flash a touchwiz stock one (rooted of course), and updating your profile/prl. If that doesn't work use the ##7282# or something like that (look it up please, I can't remember the code right now) in the touchwiz ROM. Those may fix it.
Don't forget to backup!
------------------------
Sprint Galaxy S3 :trooper:
Click to expand...
Click to collapse
K, well I backed up and fixed permissions. Same issues... So I'm gonna try the touchwiz. I'll keep you posted. Thanks!
Whiplashh said:
You could try fixing permissions, or backing up your current ROM, flash a touchwiz stock one (rooted of course), and updating your profile/prl. If that doesn't work use the ##7282# or something like that (look it up please, I can't remember the code right now) in the touchwiz ROM. Those may fix it.
Don't forget to backup!
------------------------
Sprint Galaxy S3 :trooper:
Click to expand...
Click to collapse
Well shoot. I did everything, backed up and all. On the stock rom I got everything working normally. I then went into CWM recovery and installed Cyanogenmod 10.0 again. And lo and behold, I can only send messages if they're 1 page. Anything more than that and it gets an Error 34: Network not responding. I don't know what to do? Could it be Cyanogenmod? Because that seems oddly specific...
Thoughts?
Since you can send single-page texts, it's probably a setting in the messaging app. In my messing app, there's an option to spilt messages, maybe try that.
Sent from my SPH-L710 using xda app-developers app
No setting for that in my messaging system :\ I'm using the stock Cyanogenmod 10 one, should I consider a different system?
Well, I just installed a more recent Nightly from CM and everything is working. Irony at its finest: The "Stable" mod has problems and the nightly is flawless.
Thanks for everything! (I hit that Thumbs Up for you!)

[Q] AOSP keyboard failed to launch?

So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS

[Q] Q & A BrokenPop [5.0.2][official] Dialer not working ?

Merry Christmas to all!
JLM, have posted similar on your other site.
Having a problem with the BrokenPop 5.0.2 on my L900 (Sprint Note2)
I can't seem to dial out with this rom. I get popup saying 'Unfortunately, Dialer has stop"
Are others seeing this problem? Is this an rom issue or a setup issue on my end?
I don't expect a daily driver from an early alpha of this rom and do expect issues but I would hope that I can at least make phone calls, after all, the Note 2's primary function is a phone
What I have done so far.
DL and installed rom twice. Both DL check via MD5 OK
Using Philz 6.07.9 recovery
1. Backup internal sdcard to pc
2. Factory reset / Install new rom option
3. Wipe/format internal sdcard
4. Reboot recovery (selected yes to restore root notification)
5. Install rom
6. Boot rom
7. Boot into recovery
8. Flash Gapps
9. Did minor setup of things like Wifi, Google Login, Play Store, DL ES File Manager.
10. Try to make phone call using dialer (phone icon) and get 'Unfortunately, Dialer has stop"
11. DL another free dialer from Play Store.. same error message.
I'm open to suggestions on how to get this to work.
I do like what I see from my little tour around this rom, but not being able to make calls is a major issue for me even for an alpha release. For now I have fallen back to my trusty Community Rom 4.4.2 which has been rock solid for me.
Thanks
bump.... a few people have viewed this posting .. anyone else having this problem? I have since try to install once again.. had some limited success with dialer, but then problem returns. even made a nandroid of when it was working.. still my favorite early lollypop rom for the l900
I installed Broken5.0.2, ran it for 24, and found it seemed to be one of the least reliable functioning loli roms for L900. I personally am preferring the LiquidSmooth 12-23 nightly. The LS rom has overcome the wifi/screen off hotboot bug, the keyboard bug, but still needs the manual GPS fix. Right now it offers hands down the most functioning options at this particular time and the phone is semi reliable??? Lol its doesnt FC but its buggy.
My two cents ... Cheers!
I've tried LiquidSmooth 12-23 nightly also.. one thing I had issues with was I have a OTG usb drive and did not find a way to unmount it. Did you find that function anywhere in LS?.. Other issue I have is no XPOSE support right now.. and I'm not a fan of the AOSP messaging pgms. Lots of things I don't like about TW .. but they make a nice messaging pgm
I did see a semi-workaround where you click on the carrier setting and it kinda resets the capability to make calls.. kinda hokey.. but it seems to work.. Lolllypop is still very early.. and I guess these are the growing pains for being alpha testers. Hopefully over time it will get more mature. Back on 4.4.2 for now.. everything works.. the thing is huge.. over 2gb nandroids using high compression.. but hey, everything works.. Thanks for responding.

[Q] No MMS Liquidsmooth v4.0 (Virgin Mobile)

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

Categories

Resources