The process android.process.media has stopped unexpectedly!!!!

[Guest ValiantSaint]

Hi (again!) on all of the last four ROMs I have installed, I keep getting the same error message a different times: "The process android.process.media has stopped unexpectedly" What causes this? I've had it on CM7 Green, CM7 N131, Ginger Stir Fry and now SS. I have booted into recovery and done a full wipe of everything, and I'm still getting this error. Is my phone bricked? Cheers : )

[Guest k0zmic]

No, it's not a brick unless it's dead as in there's no sign of life and not even a light comes on.

Have you done full wipes when you changed ROM's?

[Guest ValiantSaint]

No, it's not a brick unless it's dead as in there's no sign of life and not even a light comes on.

Have you done full wipes when you changed ROM's?

OK, so maybe "bricked" was a bit too strong. Is FUBAR'd better? LOL

Back on topic, what's the best way to do a full wipe? I have been cleaning the cache and doing a data wipe. Is this enough? Cheers : )

[Guest k0zmic]

OK, so maybe "bricked" was a bit too strong. Is FUBAR'd better? LOL

Back on topic, what's the best way to do a full wipe? I have been cleaning the cache and doing a data wipe. Is this enough? Cheers : )

In recovery mode do data/factory reset then go into mounts and storage and select format system.

[Guest ValiantSaint]

In recovery mode do data/factory reset then go into mounts and storage and select format system.

I'll give it a go, thanks : )

[Guest t0mm13b]

Uhhhh....

Something is wrong here....

People are posting questions like the above, and did not bother to read the important message when it comes to installing ROMs and it has been oft-repeated over and over again, kinda like telling you to listen until we're blue in the face.... NO WIPE NO WHINE! <_<

Simple really, just do a darn wipe data/cache prior to installing ROMs... :rolleyes:

[Guest ValiantSaint]

Uhhhh....

Something is wrong here....

People are posting questions like the above, and did not bother to read the important message when it comes to installing ROMs and it has been oft-repeated over and over again, kinda like telling you to listen until we're blue in the face.... NO WIPE NO WHINE! <_<

Simple really, just do a darn wipe data/cache prior to installing ROMs... :rolleyes:

I did do a "darn wipe data/cache" as I always do. I have never had to do a system format, though. (TBF, I normally use ROM Manager to swap between ROMs, so the option maybe slightly different in that program)

[Guest ValiantSaint]

Sorry to double post, but the phone has started displaying the message again after I rebooted the phone (It was fine for the first re-boot after installing Ginger SF b13) I have however, reinstalling most of my programs. Does that mean that one of them could be damaged? How could I find out which one?

[Guest t0mm13b]

Sorry to double post, but the phone has started displaying the message again after I rebooted the phone (It was fine for the first re-boot after installing Ginger SF b13) I have however, reinstalling most of my programs. Does that mean that one of them could be damaged? How could I find out which one?

Can you pastebin the entire log from start? Plug in the cable into handset and issue this command 'adb logcat -c && adb logcat > handset_issue.txt', then restart as normal, let the errors crop up, after a period of time after you get the error message, kill the logging by Ctrl+C, the file will be saved.

Open up the file handset_issue.txt and paste it into the linky above and submit it, you will get back a URL, reply back with the URL and I'll take a look at it :)

Edited July 15, 2011 by t0mm13b

[Guest Mushroom_Lord]

No, it's not a brick unless it's dead as in there's no sign of life and not even a light comes on.

O.o mine just start doing this like 5 mins ago and I can't get it to wake :L

I shoved it in the airing cupboard as it seems a bit damp, and I was getting bootloops before. If this doesn't help i'll just tpt it back :P

[Guest ValiantSaint]

I have managed to get round this problem, in the end. I think it was something i was doing when re-installing all of my apps from a Titanium backup. So I installed the "Ginger Stir Fry" ROM, then reinstalled everything again manually, then made a new backup. Job done : )