Alright, I rooted my EVO using the unrEVOked 3.3 method. I also NAND unlocked it. But when I flash any rom/kernel/radio. I lose MMS. Now I can root the stock sprint setup and I can receive MMS, but ANY other rom I lose the ability to get incoming pics. I have tried 2.2 roms, 2.3.3 and 2.3.4 roms with the same result every time.
Any ideas?
Any ideas?
Well I'm not sure which roms you're running, but in the latest CM7 nightlies, its a known bug with the MMS issue; you can send them, but they won't receive; its getting worked on.
I suppose a work around for now would be to stay on that stock rom you were on, or notify the people that are sending them, and have mms [pic, song, ect] sent to an email account, in which you can download it from.
Thanks, I have tried 15 different roms in the past 2 days. Even ones that say MMS works. I'm just gonna stick on stock for now until I know for sure I can get a good running rom with at least MMS working.
Thank you
Hopefully it does get fixed, but no problem.
You could always revert to stock Ruu and see if that fixes anything. Also, try wiping everything before you flash, including boot and system.
You could try as someone above said, do a full wipe. In Amon RA do a full wipe: data: factory reset, data, cache, dalvik cache. Then use Caulkin's Format All (search for it you'll find it somewhere on here). Flash into a sense ROM, Kings UNleashed R5 is good. Then update profile and PRL & see if that works. I had a similar problem and did these steps and it worked again. Similarly, if you want to try an AOSP rom like CM7 or MIUI, do this in a sense rom before hand and then just wipe cache, dalvik cache, then flash new ROM and the profile and PRL will still be in tact.
Hope that helps.
Related
I am running Myn warm 2.2 rls 3. I will be going to rls 4 shortly. I have yet to establish a procedure for updating/switching ROMs that works. I have gone from one release of a rom to another and only wiped cache and dalvik. Sometimes this works and other times not. I have had best results wiping data, cache, and dalvik, but then I have to get my phone back up-to-date. I use Titanium Backup (paid) and it restores pretty well. Again best procedure that works consistently for me is to restore only user apps and data, but then I have to resetup homescreen settings, ringtones, speed dial, bluetooth pairings, wifi keys, etc. I have run into problems when restoring system data with TB. Any ideas for a procedure that works consistently?
To go from RLS3 to RLS4 you should only have to wipe dalvik and cache.
To go from one version of CyanogenMod to a newer one, you only need to flash the update.
To go from two completely different ROMs, you have to wipe data and cache. You can restore WiFi, Bluetooth, and Phone settings via TitaniumBackup, in addition to all your apps.
Doing a search on here for five seconds would have gotten you all of these answers.
drmacinyasha said:
To go from RLS3 to RLS4 you should only have to wipe dalvik and cache.
To go from one version of CyanogenMod to a newer one, you only need to flash the update.
To go from two completely different ROMs, you have to wipe data and cache. You can restore WiFi, Bluetooth, and Phone settings via TitaniumBackup, in addition to all your apps.
Doing a search on here for five seconds would have gotten you all of these answers.
Click to expand...
Click to collapse
I have not gone to a newer release of Myn yet. The recommendation is to do a full wipe. I will try cache and dalvik, but in the past with other roms this has caused problems.
Not interested in CM, but thanks for the info.
I have not yet been able to determine what to restore for bluetooth or phone settings that was why I was asking.
BTW, I did search (took me much more than 5 mins) and found nothing helpful to my situation.
When i went from rls3 to rls4 i only wiped the cache and dalvik and i got force closes. I then wiped everything and reflashed and i havent gotten any problems. So the best thing is to wipe all at least for me. I dont really know about the other stuff, i only back up apps
Sent from my PC36100 using Tapatalk
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
danootz said:
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
Click to expand...
Click to collapse
No sometimes recovery doesn't wipe everything correctly... downlload caulks format all and then flash sense rom. Should fix your problem!!
Sent from my PC36100 using XDA App
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
danootz said:
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
Click to expand...
Click to collapse
radios have nothing to do with it. they base roms off new ota so that you can get the benefits of the changes not the radios. You can flash the original radio that came with the evo and it would not affect the rom. The radio controls your signal strength and wimax strength. which is why there is a thread with all the different radios because each phone reacts different to each radio.....
I recently decided to update the look on my Evo and went with the MikFroyo v4.5 Rom. I was running Netarchy's Burnt Rom, and had the toastmod kernel. After updating the radios, as they suggested, I proceeded with flashing with the MikFroyo rom. The MikFroyo Rom comes with stock HTC #15 Kernel, which I just left alone until my wifi stopped working.
I read on a few threads that some people were flashing a different kernel and were able to fix wifi, so I tried a couple of different ones. I've listed the kernels I used below. Additionally, I updated profile in system updates, and it still didn't fix anything.
[KERNEL]
Stock HTC #15 Kernel (came with MikFroyo v4.5)
4.3.1 netarchy-toastmod-cfs-nohavs-nosbc-universal
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS) - This kernel is currently on my phone.
I'm just grasping at straws at this point, and I have no idea what else to do. I love the Rom, but I need the wifi to work.
Does anyone know a kernel that is supposed to resolve the wifi issue?
Are there perhaps some file location changes that were made when the new Rom was installed?
You stated that you kept the HTC 15 until wifi stopped working. This infers that wifi was working with MikFroyo and then something happened. What mods did you make to your phone just before wifi stopped working?
Hi, thanks for the reply. I meant to say I didn't start trying new kernels until I noticed the wifi wasnt working. The MikFroyo rom suggested updating the radios before flashing it, so I did.
The wifi problem surfaced after updating the radios to the current ones. I reverted the ROM back to Netarchy Burnt Droid 1.4.2 to see if it was the ROM that was causing the issue, but the wifi still can't scan for networks. I also always wipe the dalvik and cache before flashing.
Which radio did you flash.
I would suggest doing a full wipe, and then re-flashing the rom.
Khilbron said:
Which radio did you flash.
Click to expand...
Click to collapse
I did the combo and the boot update found here. I don't know which piece effects the wifi though.
teh roxxorz said:
I would suggest doing a full wipe, and then re-flashing the rom.
Click to expand...
Click to collapse
I also always wipe the dalvik and cache before flashing anything. Are you saying I need to wipe something else?
aerobic1 said:
I also always wipe the dalvik and cache before flashing anything. Are you saying I need to wipe something else?
Click to expand...
Click to collapse
I'm saying backup your rom and apps. Then do a full wipe, factory/data, cache, and your dalvik, then re-flash your rom. That should clear up your issues.
teh roxxorz said:
I'm saying backup your rom and apps. Then do a full wipe, factory/data, cache, and your dalvik, then re-flash your rom. That should clear up your issues.
Click to expand...
Click to collapse
Wooohooooo!!!! I wiped everything, and it's working PERRRRRRRFECTLY!!
Thanks a bunch teh roxxorz
Anytime man.
So i just flashed cm7 the stable version, first thing i do is turn on my wifi, but when it obtains the ip adress etc, it keeps rebooting and turning off rebooting, and just keeps doing that over and over again. any suggestions?? anyone?
Have you tried reflashing it on a clean install? You also flashed gapps with it?
yes, i even wiped alll that thing like dalvik and all that good stuff and flashed gapps right after. this started happening to me with rc3 rc4 and now stable cm7, works fine with cm2
Did you flash a kernel with it?
whats that?
cocoes4o8 said:
whats that?
Click to expand...
Click to collapse
Well that's a no then. And the kernel is basically the heart of the phone operation. Different kernels do different things, but we can worry about that later.
Now I'd like you to backup your apps, then re-flash the rom completely, along with gapps.
If it is turning on Wifi only that causes the issue, it may be something with what is remembered in your wifi access points.
Delete your access point. Turn on Wifi and re-attach.
should i wipe dalvik cache also?
cocoes4o8 said:
should i wipe dalvik cache also?
Click to expand...
Click to collapse
Yes; you need to wipe factory/data, cache, and dalvik cache. The flash the rom, wipe cache and dalvik, then flash gapps, then reboot.
just finished doing all that
Any improvement?
WIFI Sleep policy set to NEVER?
thanks!! it works!!! ok i have one more problem, this has been happening to me since i flashed cm7 any cm7, i use email alot but it doesnt give the right time date etc, each and every email date is 12/31/1969
cocoes4o8 said:
thanks!! it works!!! ok i have one more problem, this has been happening to me since i flashed cm7 any cm7, i use email alot but it doesnt give the right time date etc, each and every email date is 12/31/1969
Click to expand...
Click to collapse
Have you tried updatinng / reinstalling the app?
yes even downloaded a different email program.
the email thing
might be a problem from your email server what service do you use is it a public or a private service such as work email or a simple yahoo gmail hotmail? type pop 3 that could explain it more in depth
teh roxxorz said:
Yes; you need to wipe factory/data, cache, and dalvik cache. The flash the rom, wipe cache and dalvik, then flash gapps, then reboot.
Click to expand...
Click to collapse
ok when i flashed cm7 final my market was jus loading forever so i did those steps n now it works but ive been haven an issue wit the facebook app...when i go to my messages it jus forcloses same goes for when i checkin...any ideas
weztcoazt said:
ok when i flashed cm7 final my market was jus loading forever so i did those steps n now it works but ive been haven an issue wit the facebook app...when i go to my messages it jus forcloses same goes for when i checkin...any ideas
Click to expand...
Click to collapse
When you flashed, did you flash the gapps?
And facebook app has been giving people problems...I think the word was to go back to 1.52 [the previous version before latest update] and you should be good.
I don't have a facebook, so no help with that app, sorry.
teh roxxorz said:
When you flashed, did you flash the gapps?
And facebook app has been giving people problems...I think the word was to go back to 1.52 [the previous version before latest update] and you should be good.
I don't have a facebook, so no help with that app, sorry.
Click to expand...
Click to collapse
yeah i flashed it right after the rom....but ok no worries no biggie jus tryin to see if it could b fixed...also when i run the car home app n select "navigate" it tells me "no activity found"...whats wrong
You should always do a factory like reset before flashing a rom.
When I went to CM7 I did this.
Ran a Nandroid backup of Stock rom
Ran the GPS Fix for CM7 before going to CM7
Cleared Dalvik cache
Cleared Cache
Cleared Data
Flashed CM7
Flashed GApps
ReBooted
If you used TB to backup everything on your old rom then ONLY install the Apps NOT the data. Also I have noticed that a lot of people are just running a Restore everything from TB that may have something to do with it. I only installed third party apps like barcode scanner, Game Fly, PicSay, Directv. Do not restore anything that was a system app from your other rom.
And so far everything has been great.
Hello everyone. I'm running CM7 Nightly #134 with Aeroevan's .7 BFS Kernel. It appears I'm unable to recieve MMS messages. I'm using handcent, and I do have the option on to "automatically retrieve messages" under the MMS category. Is there any fix/patch that I could apply to my phone? I'd rather not reflash another ROM onto it as I like how it is right now. Thanks!
You could look into on of the cm7.2 kangs builds I'm pretty sure you can flash them over whatever cm rom you're running just wipe dalvik. You'll need to flash the kernel again and be sure to make a back up
Okay so dalvik-cache is the only thing I need to wipe, correct? Once I wipe the dalvik cache (assuming this is the only thing I need to do), I will flash one of the kangs. What exactly will I need to re-do? I've pretty much flashed/applied the following:
G-Apps
Aeroevan's 0.7 BFS Kernel
crypted's AGPS Patch
The kernel will need to be re-flashed for sure because it will revert to the stock CM kernel in the new kangs, and probably the AGPS patch as well. But dalvik-cache has nothing to do with applications right? I was reading online about it and it seems a bit confusing to me. Also, will I have to reconfigure all of my misc. settings again? IE: My overclock, preferences, launcher, etc?
ma70ent said:
Okay so dalvik-cache is the only thing I need to wipe, correct? Once I wipe the dalvik cache (assuming this is the only thing I need to do), I will flash one of the kangs. What exactly will I need to re-do? I've pretty much flashed/applied the following:
G-Apps
Aeroevan's 0.7 BFS Kernel
crypted's AGPS Patch
The kernel will need to be re-flashed for sure because it will revert to the stock CM kernel in the new kangs, and probably the AGPS patch as well. But dalvik-cache has nothing to do with applications right? I was reading online about it and it seems a bit confusing to me. Also, will I have to reconfigure all of my misc. settings again? IE: My overclock, preferences, launcher, etc?
Click to expand...
Click to collapse
Correct... You'll need to reflash kernel, agps patch and gapps. Unless you're flashing my kang in which case you won't need to flash gapps. I have them included in the ROM. I would always suggest a dalvik wipe as well as cache but a full wipe "might not" be needed.
Just do a back up before flashing in case you have any issues.
Sent from my ADR6350 using xda premium
What's the difference between dalvik cache and normal cache? Also, is the MMS issue fixed in kangs/newer source builds? I'm hoping that flashing the newer stuff will not be in vain
ma70ent said:
Okay so dalvik-cache is the only thing I need to wipe, correct? Once I wipe the dalvik cache (assuming this is the only thing I need to do), I will flash one of the kangs. What exactly will I need to re-do? I've pretty much flashed/applied the following:
G-Apps
Aeroevan's 0.7 BFS Kernel
crypted's AGPS Patch
The kernel will need to be re-flashed for sure because it will revert to the stock CM kernel in the new kangs, and probably the AGPS patch as well. But dalvik-cache has nothing to do with applications right? I was reading online about it and it seems a bit confusing to me. Also, will I have to reconfigure all of my misc. settings again? IE: My overclock, preferences, launcher, etc?
Click to expand...
Click to collapse
Hey did you get your mms working on your phone? I'm having the same issue with cm7 and BFS Kernel on HTC aria. Can neither send nor receive.
Thanks!
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application. Think of dalvik cache as Windows prefetch.
As far as mms.... It's working fine on my CM7 kang and I would assume the others as well. Once thing you can try though that worked on Eris when people had mms issues for one reason or another is:
1. Install Verizon Messages from the market and use that to send and receive a couple mms messages.
2. Once you confirm mms is working again you can uninstall it and go as normal.
Another option that takes a little more work is:
1. Make a nandroid backup of current ROM.
2. Install a stock based ROM.
3. Send and receive a few mms messages to verify everything is in working
order.
4. Install APN backup/restore from the market.
5. Open APN backup/restore and backup your APN's.
6. Restore backup you previously made.
7. Install and open APN backup/restore.
8. Restore APN's with the ones you backed up from stock.
@christophlend
Nope, haven't gotten it working yet.
@CondemnedSoul
Just wondering, why would installing Verizon Messages, then uninstalling it fix the problem? Is there something that gets activated/left over during this process that may / may not allow me to send MMS messages?
Also, I would definitely flash to your kang if I knew that all of my current settings/apps wouldn't be wiped out. If I could retain all of my current apps, and some of the more important settings, then I'd probably go for it.
ma70ent said:
@christophlend
Nope, haven't gotten it working yet.
@CondemnedSoul
Just wondering, why would installing Verizon Messages, then uninstalling it fix the problem? Is there something that gets activated/left over during this process that may / may not allow me to send MMS messages?
Also, I would definitely flash to your kang if I knew that all of my current settings/apps wouldn't be wiped out. If I could retain all of my current apps, and some of the more important settings, then I'd probably go for it.
Click to expand...
Click to collapse
The only thing I can figure the Verizon app does is reset your apns automatically vs restoring them from a stock ROM. We never quite figured out why it worked but 99% of the time it was successful when a few people had mms issues with a build. As far as your apps and settings going to my build... I can't promise a flash over will work. If you're on cm7.1 is suggest a full wipe of everything going to 7.2. You can always back up user apps and data with titanium backup and restore those however system settings would need to be reset manually. Restoring system data with ti backup is not recommended.
Sent from my ADR6350 using xda premium
Alright I'm gonna try installing the Verizon app. If that fails, I'll be doing a full wipe (I'm guessing wipe cache + wipe dalvik cache then flash is what you mean, yes) and use TiBu to reinstall the apps I had.
Thanks for all the help.
ma70ent said:
Alright I'm gonna try installing the Verizon app. If that fails, I'll be doing a full wipe (I'm guessing wipe cache + wipe dalvik cache then flash is what you mean, yes) and use TiBu to reinstall the apps I had.
Thanks for all the help.
Click to expand...
Click to collapse
Full wipe meaning data/factory reset, cache wipe then advanced-wipe dalvik.. yes.
CondemnedSoul said:
Full wipe meaning data/factory reset, cache wipe then advanced-wipe dalvik.. yes.
Click to expand...
Click to collapse
I've been meaning to ask this, what does the data/factory reset function do in CWM? And well, now that I know what wiping dalvik does, what does just wiping the "cache" do? What is stored in there?
Ok so I got MMS to send and recieve using Nightly #134. First I installed Verizon Messaging, then I read something on here about using GoSMS and configuring it manually....so now it works and its awesome. Just search for a CM 7.2 kang thread and GoSMS
CondemnedSoul said:
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application. Think of dalvik cache as Windows prefetch.
As far as mms.... It's working fine on my CM7 kang and I would assume the others as well. Once thing you can try though that worked on Eris when people had mms issues for one reason or another is:
1. Install Verizon Messages from the market and use that to send and receive a couple mms messages.
2. Once you confirm mms is working again you can uninstall it and go as normal.
Another option that takes a little more work is:
1. Make a nandroid backup of current ROM.
2. Install a stock based ROM.
3. Send and receive a few mms messages to verify everything is in working
order.
4. Install APN backup/restore from the market.
5. Open APN backup/restore and backup your APN's.
6. Restore backup you previously made.
7. Install and open APN backup/restore.
8. Restore APN's with the ones you backed up from stock.
Click to expand...
Click to collapse
Dude, you're a genius!! This fixed my wife's inc running CCM7 v15. I'm out of thanks, but I'll get ya tomorrow.
NOTE: When I uninstalled the VZW app, MMS stopped working again. So I reinstalled it and turned off all its notifications.