i have a incredible 2 with Verizon and i went into ROM manager and did a backup for cyanogen 7 and then downloaded miui straight onto the phone and flashed it. when the phone rebooted itself and started using miui it got to the lock screen and when i unlocked it it started giving me messages that various applications are crashing. an example of one of the messages is " the process android.process.media has stopped working unexpectedly. Please try again." so can someone please tell me what is going on and how to fix the problem ?
The rom you got could have bugs. Have you tried overclocking your device? MIUI roms use a lot of resources which could also cause the problem. If you still have problems, then try flashing a new rom.
Sounds to me like you didn't wipe Data when you flashed miui.
I'm not having any issues at all.
Go into recovery and wipe cache, dalvik, and data. Then reflash MIUI. If you don't wipe properly you'll get force closes.
I suggest flashing through recovery instead of through ROM Manager. I don't trust it to do what it's supposed to do, and it's easy to do it manually.
Sent from my Evo + MIUI using Tapatalk!
Related
The ROM runs pretty smoothly until I try to change a ringtone using the android system and then I get the error android.media isn't working and it forces me to close it until I either reinstall the ROM or change to a different one. Has anybody else had issues that can help with this?
Also, there is no Oxygen settings menu on this version so I was wondering if any of the themes could be changed another way.
HurtMeSole said:
The ROM runs pretty smoothly until I try to change a ringtone using the android system and then I get the error android.media isn't working and it forces me to close it until I either reinstall the ROM or change to a different one. Has anybody else had issues that can help with this?
Also, there is no Oxygen settings menu on this version so I was wondering if any of the themes could be changed another way.
Click to expand...
Click to collapse
i run this same ROM and i have not had the problem that you are having. what i would try is to go into recovery and wipe data/ factory reset, and then wipe cache partition, and lastly, go to the advanced part of recovery and wipe davlik cache as well just to make sure.
then install the ROM again, everything should turn out ok. good luck.
I tried that several times. It runs incredibly smooth until an attempt to access some kind of media and then I get the android.media.secure error I believe it is. I love how smooth and quickly it runs but the error literally pops up every 5 seconds until I install another ROM or re-install.
@ hurt: wow, i don't even know what to add to that, especially since you've tried to wipe everything several times. i would hope that perhaps someone would assist you in getting this working as this ROM truly rocks. good luck in getting this resolved.
redownload it?
Hey everyone, I just updated my Nexus S from version 1.1 of the ROM here to 2.1
http://forum.xda-developers.com/showthread.php?t=1399035
Since I was already on CM9 I followed the instruction that says I don't need to do a full wipe. I did however wipe both caches and the boot just to be safe. I installed through ROM manager, booted into the ROM successfully, but GApps wasn't restored like it said it would be. After that tried installing GApps v11 like the directions say to. However, market just closes every time I open it now and none of my gmail stuff can sync because of it. I've tried reinstalling GApps. Anything I can do without having to wipe the whole ROM and recover it?
Another thing, every time I boot into this ROM I get the optimizing apps dialog, no matter how many times I reboot. I read a good bit of the thread and no one else seems to have that problem either, any ideas there?
Thanks in advance
Hello Sensation users
Recently i was trying to install and try out one of the MIUI ROMS.
So far I have tried the blackwing (CM9 based) version and sense based versions from bsAndroid and directly from http://en.miui.com/
However i got problems with all of them. Could you please advise if i am doing something wrong or is this the ROM problem.
None of the verions lets me restore anything using Titanium backup. Sometimes, i am getting an error saying Installer packager has stopped, other times the restoring process is ok, but when i reboot the phone thereafter I am getting loop of these messages:
Unfortunately the process com.android.phone has stopped
Is Titanium backup incompatible with the MIUI Roms? or am i doing something wrong?
The applications I am restoring are not problematic and very common - like Angry Birds or Wi-Fi and APN settings.
I am using 4ext Recovery and 3.32 firmware. And of course i Factory Reste and wipe the cashe before installing a new ROM
Please advise
I wanted to post this in the BAKED thread in the developer section but I don't have enough poststo do it there, so hopefully someone here can help.
I just flashed crespo BlackBean 7 (BAKED) ROM (on my Nexus S) and inverted gapps. It seems to have installed properly but whenever I reboot I get a message that several processes have stopped such as YouTube and GMail, and when I go in to system settings -> storage I get a message saying "Unfortunately, Settings has stopped". I get that message every time consistently. I've tried re-flashing the ROM but to no avail. When I installed the ROM I wiped "Dalvik cache", wiped "Battery Stats" and wiped "Cache partition".
It appears I've not done something or done something wrong, so if anyone here can help I'd appreciate it.
Did you full wipe before installing the rom? That means factory reset/data wipe.
polobunny said:
Did you full wipe before installing the rom? That means factory reset/data wipe.
Click to expand...
Click to collapse
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
volan1 said:
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
Click to expand...
Click to collapse
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
volan1 said:
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
Click to expand...
Click to collapse
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
anshumandash said:
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
Click to expand...
Click to collapse
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
volan1 said:
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
Click to expand...
Click to collapse
There isn't any boot issue with the ROM. If you decide to try this ROM again, try to do a clean install.
Boot into recovery, do a factory wipe, go to advanced & wipe dalvik cache, go to mounts & format /systems. Flash ROM & gapps, reboot.
Sent from my Nexus S using xda app-developers app
Hi Everyone,
I've been having some trouble getting custom ROMs to fully boot on my girlfriend's Galaxy Tab 2 (p3113). I was able to gain root access (I used this method: http://forum.xda-developers.com/showthread.php?t=2510669) and managed to install the latest CM rom, SlimRom, or OmniRom (with their respective Gapps).
However, I always run into the same problem: whenever I reboot from recovery (regardless of which rom was installed), android begins "optimizing" apps (presumably because I've cleared caches, including dalvik) and at the end, reports 2-3 process that have unexpectedly stopped, and reboots. I've done clean wipes with each install, and even tried re-downloading the roms, but nothing seems to work. Also, it doesn't seem like the stopped processes are consistent between roms. For example, the CM rom would report calendar and keyboard processes that have stopped, whereas Omnirom would report mediastorage and google search processes that have stopped.
Anyone have any ideas of what I can do to fix this?
It sounds like you are not doing a full wipe, I dont think it should be optimizing on a fresh clean install. Try factory reset, wipe cache/dalvik. And possibly system.(usually recomended)
Sent from my SGH-T889 using XDA Premium 4 mobile app
Thanks - that what I suspected as well, although I thought I was doing a full wipe (including /system) in TWRP, but maybe not?
Anyway, I somehow got it working last night after formatting /data and then flashing the last CM stable release (CM-10.1.3, p3110). Got the tablet to boot and setup and everything. Maybe there was something conflicting in the data folder, or that there was no more space on the internal SD. Guess I won't know now..
But I decided to flash the latest Omnirom instead, to get a 4.4 rom. Seems to be working fine now. Thanks for the reply!