Database Info

android.process.media (delete this thread)

So all the sudden i have "android.process.media" force closing it happened like four times so i tried rebooting. Still happened after the reboot and i noticed i lost my ringtones. Finally my phone just rebooted now im stuck on the endless android screen! Any ideas what could have gone wrong.
Oh and by the way this just started today but i've been having android.process.core force closing alot ever since i got the phone.
UPDATE: So i have apps to sd maybe this could be part of the problem. I have booted into recovery and typed
su
cd /system/sd
it returns cant access
Maybe i can move all apps back to phone via recovery terminal I just dont know what the commands to do this would be. Also i am at work so i cant use adb.
OK first off i want to start off with always backup everything before anything
i finally got it working i had to reverse all the scripts to move my apps, data, etc. work but kept rebooting finnally i did a wipe worked... somewhat.... but wouldnt log into google so i created a new password that worked. thanks to everyone for their help (cough)

Solved
Hi,
i solved this problem on my Hero making a complete wipe of my SD card.

Angry birds pigs wont die after 1.4.2 update and data restore??

So I have had issue after issue getting the new version to even INSTALL.. but finally got it after totally deleting the older 1.3.5 version and wiping cache, restart etc.. new install of 1.4.2.. everything works fine....
BUT....
After using titanium backup to restore data there is some kind of bug that makes the birds virtually worthless. I get the data back (levels etc) but when I go try to beat an old level the birds litterally bounce off the pigs without causing ANY damage.
Ive done this 3 different time now, totally removing the game, reinstalling, verified to work "normal" before data restore... and again, not working after the data is refreshed.
PLEASE HELP!
EVO
Myn RLS3
Nets 4.2.1 CFS more

Let me answer my own thread after I finally find the answer minutes after posting this...
Thanks to anuwyn in this thread:
http://forum.xda-developers.com/showthread.php?t=820725
anuwyn said:
Fix for "Application not installed message" and "Installation unsuccessful" on Rooted HTC Hero with FroydVillain 1.5.
I couldn't install Angry Birds and some other applications on the Market after installing
FroydVillain 1.5 and after some debugging I found out why. There seems to be a problem related to
the file "/mnt/secure/asec/smd12tmp1.asec".
Solution: Delete the corrupt file with a terminal app and also delete the market data to be sure.
1. Get "Terminal Emulator" or another terminal app from the Market.
2. Run the "Terminal Emulator".
3. Write:
su (ENTER)
rm /mnt/secure/asec/smd12tmp1.asec (ENTER)
rm /data/data/com.android.vending/cache/* (ENTER)
4. Exit the emulator, reboot and try to install the failing application again.
5. If the above doesn't solve your problem try the following:
- Wiping cache
- Wiping dalvik cache
6. If this doesn't fix your problem just wipe the phone and reinstall everything
Click to expand...
Click to collapse
It SEEMS to have worked!
I know this is kind of an obscure problem that no one else will probably ever have, but figured Id update it just the same.

same thing happened to me, I just restored the older version with the data and then updated the app over the market..worked fine after that

i could never get it to update over the market for some reason... always had to unmount the SD to get it to work.. but couldnt install from the market or save to phone without SD in.
I ended up saving to sd and using root explorer to move it onto the phone, unmount sd, do a cache wipe, install from phone, remount sd. whew!
its updated now and i have successfully done a titanium backup several times. (Thank God)
I have similar issues with fruit ninja attempting to update but just gave up on that one.

[Q] How to delete files permanently in ADB?

My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.

best of luck
nbreed said:
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
Click to expand...
Click to collapse
try plugging it up while its in cwm and access the adb shell while its displaying. the prompt should be ~# if its universal. maybe you can completely wipe everything and flash a recovery at the same time? that may keep it deleted. i dont know. just a suggestion. i hope you succeed... tell me how it goes.

thanks for answering.
i tried all that, even did a complete format of the internal sd card, in adb with parted and also in windows with a mounted card. it says it is deleted, but after reboot it is all back again...

Do you have a backup of a working ROM you can restore?

Crap.... Hmm... Have you tried any formatting software? Try to find a programmer who can wipe it completely, re partition, and reinstall the stock rom. Then try to restore to something before the problems
Sent from my R800at using XDA

Use flashtool. I've heard it can unbrick, maybe it'll help???
Sent from my R800at using XDA

nbreed said:
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
Click to expand...
Click to collapse
this Q
With Q???

Recovery rom can be installed, but is gone after reboot. Formatting in windows or linux (adb) performs without errors, but after reboot, yes you guessed right, it is back. So this internal sd card has a life of its own, the only thing I can do is install a working system with flashing, but then no app will work, every activation of whatever app will give inconsistent uids errors. And I cannot install new apps, because vending.apk (market) will crash. I installed vending by hand (adb), then it work for a moment, but after reboot to use it the normal way, again crashed.
AS LONG AS I CANNOT REPLACE THE SDCARD IT IS HOPELESS?!?

This morning I left the unwilling android tab in the power adapter to be fully charged for a new go. But: it is now a real brick. It won't power up any more, the button lights do not flash anymore, the only thing it does, is showing the battery. Never again will I buy such an expensive underdeveloped piece of plastic crap again!

Calm down... You need to boot into recovery mode and try using formatting the sd. If comp can recognize, format the sd with the computer. It's not the android. It's what you did. Sorry
ROOTED Xperia Play 4G 2.3.3

can you read? i did format the sdcard in adb with parted, i did format it on the pc. but when i reboot EVERYTHING is back again. before rebooting it is totally empty. after reboot the old non-working stuff is back.
end of android, no end of samsung for me

Help
How do I install the radio over abd

News on this issue?
nbreed said:
can you read? i did format the sdcard in adb with parted, i did format it on the pc. but when i reboot EVERYTHING is back again. before rebooting it is totally empty. after reboot the old non-working stuff is back.
end of android, no end of samsung for me
Click to expand...
Click to collapse
I have the very same problem, did you managed to fix it ??

[Q] Wiped Dalvik cache, now apps are gone... how to restore?

Posted this on Android Central, but the only answer I've gotten so far is "Upgrade to CM9" -- which isn't feasible on my device. Yet.
Anyway, here's my issue. I have CM 7.0.3 running on my MyTouch 3G Slide. Before you guys jump all over me for having an old CM7 release, the SYM key does NOT work in any releases above that. Since I actually use that key, I can't update. It's a known issue (see #4570 on CM bug tracker).
If this helps: I used data2ext to move dalvik cache to the sdcard.
[This part is important. I think.] CM7 has a history of wifi issues on the MT3G slide -- there's something weird with the tiwlan.ini, so the solution is to revert to the 6.x version. I did that, it fixed it, and then yesterday it went back to its old behavior. I went into the phone terminal and recopied the 7.x tiwlan to /etc/wifi to see if that would fix it. (E.g., this meant remounting /system to rw.) No go, so I went back to the 6.x tiwlan.ini. Still nothing.
Finally I went into recovery and deleted the cache and Dalvik cache in hopes it might force it to start working again. Good news is that the wifi seems to be working. The bad news is that all my apps have disappeared from the drawer. They're still on the device (visible in Manage Applications). I'm thinking the cache may have not rebuilt itself and therefore can't load any of the apps...?
I have access to CWM, but I can't get anything else to install on the device (e.g., TiBu). When I used adb to try and reinstall Titanium, it gave me this error: "Failue: [INSTALL_FAILED_DEXOPT]."
I'm at a loss. Any ideas?

Quick update: looks like my dalvik-cache moved itself back to /cache instead of /data. Searching on how to fix this... any leads are helpful! :laugh:

Uninstalled Updates to Android System Intelligence and Now Stuck in Infinite Boot?

Hi, I'm kinda at my wit's end with this problem that I'm currently facing and would very much appreciate some help. For some background, I'm on a Oneplus 7 Pro running stock firmware (OOS 11.0.7.1). I originally was planning on installing a Magisk module to spoof my device (Pixelify) to gain Pixel features. I noticed that one of the features was patching over the Android System Intelligence. It didn't work out the way I was expecting and I decided to uninstall the module. That went fine, but I wanted to make sure I was on the correct version of Android System Intelligence as well, so afterwards, I went into settings and "uninstalled all updates" to the app, which I assumed would have reset that particular app back to the version that originally shipped with the device.
Now, here's where the problem began. I restarted my device and I ended up sitting on the boot animation screen for over 20 mins. At that point, I knew something was wrong as it still hadn't booted into the system yet. I went into TWRP and decided to do a full reflash of the ROM (without wiping my data) and reflashed magisk as well. No luck either, still stuck at the infinite boot. So I went a step further and dirty flashed again without reinstalling magisk to see if it might have been any other modules not playing nice. Of course, that didn't work either and I'm still currently bootlooping. It's been going for the past 3 hours now...
In any case, would anyone have any suggestions on what I can do without doing a full wipe? I have access to TWRP and decrypting works fine. All of my files seem intact at the moment and from what I see, the ROM is has installed mostly fine, just something is causing it to hang during boot. Is there any way I can view the code running in the background during boot to see what's causing it to hang? Or maybe some other potential solution that I could try?

HunterBlade said:
Hi, I'm kinda at my wit's end with this problem that I'm currently facing and would very much appreciate some help. For some background, I'm on a Oneplus 7 Pro running stock firmware (OOS 11.0.7.1). I originally was planning on installing a Magisk module to spoof my device (Pixelify) to gain Pixel features. I noticed that one of the features was patching over the Android System Intelligence. It didn't work out the way I was expecting and I decided to uninstall the module. That went fine, but I wanted to make sure I was on the correct version of Android System Intelligence as well, so afterwards, I went into settings and "uninstalled all updates" to the app, which I assumed would have reset that particular app back to the version that originally shipped with the device.
Now, here's where the problem began. I restarted my device and I ended up sitting on the boot animation screen for over 20 mins. At that point, I knew something was wrong as it still hadn't booted into the system yet. I went into TWRP and decided to do a full reflash of the ROM (without wiping my data) and reflashed magisk as well. No luck either, still stuck at the infinite boot. So I went a step further and dirty flashed again without reinstalling magisk to see if it might have been any other modules not playing nice. Of course, that didn't work either and I'm still currently bootlooping. It's been going for the past 3 hours now...
In any case, would anyone have any suggestions on what I can do without doing a full wipe? I have access to TWRP and decrypting works fine. All of my files seem intact at the moment and from what I see, the ROM is has installed mostly fine, just something is causing it to hang during boot. Is there any way I can view the code running in the background during boot to see what's causing it to hang? Or maybe some other potential solution that I could try?
Click to expand...
Click to collapse
When you removed the magisk module and uninstalled the updates, did you boot into TWRP and wipe your cache and dalvik cache(but not factory reset or wipe data partition)? If you didn't wipe cache or dalvik, try booting into TWRP and wipe cache and dalvik cache(but DO NOT factory reset). To wipe cache and dalvik cache, boot into TWRP and sekect the Wipe option, then select "advanced wipes", you'll see a list of partitions, select only the cache and dalvik partitions(do not select any other partitions) then swipe the slider to initiate the wipe, when it finishes, reboot your device, it might take 10 or 20 minutes to boot because it has to rebuild the cache and dalvik cache with the new changes that you've made.
Generally, when making changes to the system partition, booting into recovery after making the changes and wiping cache is required in order for the device to load the system with the changes that were made instead of continiung to load cached data from before the changes were made, this tends to cause issues because the device is loading cached data that it can't use or understand anymore. Also, reflashing your ROM without wiping cache and dalvik cache would not solve this issue. You should do this any time you add/remove/modify/delete/uninstall/edit anything at all in the system partition, even if you only changed one tiny thing, you still need to boot into recovery then wipe cache and dalvik cache then reboot to apply the changes. This is not required when changing things in the user partition but it is absolutely vital that you do it when changing anything involved in the system partition.

Droidriven said:
When you removed the magisk module and uninstalled the updates, did you boot into TWRP and wipe your cache and dalvik cache(but not factory reset or wipe data partition)? If you didn't wipe cache or dalvik, try booting into TWRP and wipe cache and dalvik cache(but DO NOT factory reset). To wipe cache and dalvik cache, boot into TWRP and sekect the Wipe option, then select "advanced wipes", you'll see a list of partitions, select only the cache and dalvik partitions(do not select any other partitions) then swipe the slider to initiate the wipe, when it finishes, reboot your device, it might take 10 or 20 minutes to boot because it has to rebuild the cache and dalvik cache with the new changes that you've made.
Generally, when making changes to the system partition, booting into recovery after making the changes and wiping cache is required in order for the device to load the system with the changes that were made instead of continiung to load cached data from before the changes were made, this tends to cause issues because the device is loading cached data that it can't use or understand anymore. Also, reflashing your ROM without wiping cache and dalvik cache would not solve this issue. You should do this any time you add/remove/modify/delete/uninstall/edit anything at all in the system partition, even if you only changed one tiny thing, you still need to boot into recovery then wipe cache and dalvik cache then reboot to apply the changes. This is not required when changing things in the user partition but it is absolutely vital that you do it when changing anything involved in the system partition.
Click to expand...
Click to collapse
Thanks for the response! Unfortunately, I already wiped the dalvik cache after I reflashed my ROM yesterday and it didn't end up being able to boot. Since the OnePlus 7 Pro is an a/b device, there's no other cache partition to wipe.
I ended up leaving it to run on the boot animation screen until it ran out of battery (just to see what would happen). Besides for the phone becoming burning hot to the touch, it just stayed at that screen for another hour or 2 before it finally ran out of battery. This leads me to believe that it's definitely doing something in the background at that time, but just not sure what.
Edit: Just for some extra context, I also created a flashable zip of the latest OEM version of the Android System Intelligence APK and flashed it to system/app through twrp. Since I'm not able to boot to unlock my device, I thought this was the only way to install the app. In any case, it didn't make a difference either. Not sure if this means maybe the APK wasn't the issue or if this just didn't install the app the way I was expecting. No error codes when flashing the zip though.

HunterBlade said:
Thanks for the response! Unfortunately, I already wiped the dalvik cache after I reflashed my ROM yesterday and it didn't end up being able to boot. Since the OnePlus 7 Pro is an a/b device, there's no other cache partition to wipe.
I ended up leaving it to run on the boot animation screen until it ran out of battery (just to see what would happen). Besides for the phone becoming burning hot to the touch, it just stayed at that screen for another hour or 2 before it finally ran out of battery. This leads me to believe that it's definitely doing something in the background at that time, but just not sure what.
Edit: Just for some extra context, I also created a flashable zip of the latest OEM version of the Android System Intelligence APK and flashed it to system/app through twrp. Since I'm not able to boot to unlock my device, I thought this was the only way to install the app. In any case, it didn't make a difference either. Not sure if this means maybe the APK wasn't the issue or if this just didn't install the app the way I was expecting. No error codes when flashing the zip though.
Click to expand...
Click to collapse
Use TWRP to create a backup of your device in its current state, then try to extract the data from the backup, if the data is intact, it can be restored once you get the device working. If your data is intact in the backup, you can do a full system and data wipe via TWRP then reflash your ROM then restore the data that you want restored. This "should" get you back to where you want to be. Be careful, be certain of what you do at every step or you may end up losing data or not being able to get it to work while at the same time be able to keep your previous data.

Droidriven said:
Use TWRP to create a backup of your device in its current state, then try to extract the data from the backup, if the data is intact, it can be restored once you get the device working. If your data is intact in the backup, you can do a full system and data wipe via TWRP then reflash your ROM then restore the data that you want restored. This "should" get you back to where you want to be. Be careful, be certain of what you do at every step or you may end up losing data or not being able to get it to work while at the same time be able to keep your previous data.
Click to expand...
Click to collapse
Just finished backing up my data through TWRP and and did a full reformat of my device. After reflashing my ROM, I was back up and running! So thanks for the tip! However, after restoring the data partition, I realized that the issue was with the data partition specifically rather than on the system side as I had the same problem again. So I cleared the data partition again but kept data/media (internal storage) intact, and just like that, the device booted just fine this time.
Would you have any suggestions on what I could do to to troubleshoot the data partition? I have some important app info that I need to get the data back from.
Or if not, do you know how to capture logs from a failed boot?

HunterBlade said:
Just finished backing up my data through TWRP and and did a full reformat of my device. After reflashing my ROM, I was back up and running! So thanks for the tip! However, after restoring the data partition, I realized that the issue was with the data partition specifically rather than on the system side as I had the same problem again. So I cleared the data partition again but kept data/media (internal storage) intact, and just like that, the device booted just fine this time.
Would you have any suggestions on what I could do to to troubleshoot the data partition? I have some important app info that I need to get the data back from.
Or if not, do you know how to capture logs from a failed boot?
Click to expand...
Click to collapse
Logs from logcat do not persist through reboot. You need to look at your last_kmsg file, kmsg persists after reboot and it should capture the issue. If you have important app data, it should have been stored in data/media in your Android/(name of app) folder and your apps should be in data/data/app folder.
In the future, I recommend booting into TWRP and creating a backup before you make any kind of changes to your device, then, if the change causes an issue you can just boot into TWRP and restore the backup, this will put you back to what you had right before you made the change. Then you can troubleshoot what caused the issue and find a solution to how to apply your change without causing the issue again.

Droidriven said:
Logs from logcat do not persist through reboot. You need to look at your last_kmsg file, kmsg persists after reboot and it should capture the issue. If you have important app data, it should have been stored in data/media in your Android/(name of app) folder and your apps should be in data/data/app folder.
In the future, I recommend booting into TWRP and creating a backup before you make any kind of changes to your device, then, if the change causes an issue you can just boot into TWRP and restore the backup, this will put you back to what you had right before you made the change. Then you can troubleshoot what caused the issue and find a solution to how to apply your change without causing the issue again.
Click to expand...
Click to collapse
Yeah, lesson learned with that. I'm just glad I was able to backup my data in TWRP, which means I should theoretically be able to extract them back out again if I really need them. But back to the topic, I did check my last_kmsg file and it was unfortunately empty.
What I did do though was since I still have access to my recovery, I pushed my PC's adb keys to my device to be able to execute the command and grab a logcat during boot.
Could you by any chance take a look at the file (it's a onedrive preview link) to see if you might be able to notice the issue? I'm going into the territory of Googling everything and I was just completely lost when I looked at the file as I have no idea which errors actually matter and which ones don't. Thanks in advance!

HunterBlade said:
Yeah, lesson learned with that. I'm just glad I was able to backup my data in TWRP, which means I should theoretically be able to extract them back out again if I really need them. But back to the topic, I did check my last_kmsg file and it was unfortunately empty.
What I did do though was since I still have access to my recovery, I pushed my PC's adb keys to my device to be able to execute the command and grab a logcat during boot.
Could you by any chance take a look at the file (it's a onedrive preview link) to see if you might be able to notice the issue? I'm going into the territory of Googling everything and I was just completely lost when I looked at the file as I have no idea which errors actually matter and which ones don't. Thanks in advance.
Click to expand...
Click to collapse
Too many errors for me to volunteer my time to figure out.
All I can say is, at each line that reports an error, it states the error then lists the service(s) or app(s) that are involved in or effected by that error, everything listed after the error all the way down the list to the next error are related to that error.
Do a Google search for each error and the name of the package that immediately follows that error.

Droidriven said:
Too many errors for me to volunteer my time to figure out.
All I can say is, at each line that reports an error, it states the error then lists the service(s) or app(s) that are involved in or effected by that error, everything listed after the error all the way down the list to the next error are related to that error.
Do a Google search for each error and the name of the package that immediately follows that error.
Click to expand...
Click to collapse
No worries, totally understandable. I think Titanium Backup might actually be my saving grace, as it's able to read TWRP files as well. So all I have to do is run my backup through that and have it directly restore my data. In any case, appreciate the advice you've given so far!

you might probably found a fix but you're supposed to put the other os in the internal storage and not the micro sd card since it wont detect bootable drives just like on a pc and if u didnt install the os on the sd card then you can search for a boot unlocker which can unlock your phone from the infinite boot based on your phone and os
have a good day