[Motorola Droid RAZR] Ohmster:
Dam, I am sorry. I forgot you must be root to execute that command.Screenshots below. Yeah, I know. Another dammed book by Ohmster, but this really tells you what you need to know and do. First a quick explanation of what we are doing:

You cannot pull up a dmesg unless you do it as root. I will explain how below.

When you first open Terminal, you get a prompt like any other command window such as in Windows or Linux. In Linux or Android, your prompt will end with a $, meaning you are a "user". A user does not have the root permission to call up a dmesg. If you enter the command "dmesg" at a user prompt ending with a dollar sign, $, you will get a reply "Operation not permitted" (This is the error you got that you could not write down.). So, you must become root first and get the root prompt ending in a hash like this, #.

In the example terminal commands below, the Firebrick Red color is your prompt, commands typed in are Blue. The stuff before the $ or # prompts is your username, followed by your status such as user, $, or root, #. First enter the su command, su. (If you have never done this in Terminal before, superuser screen will come up, grant root to Terminal.) Once you enter the su command, your $ prompt will change to a root prompt, #.

u0_a49$cdma_spyder:/ $ su

root@cdma_spyder: /# dmesg > /sdcard/dmesg.txt

After doing these two steps in Terminal, you will have dmesg.txt on your internal sdcard where you can now copy or move it to external sd-card or PC via WiFi in ES File Manager or USB cable. The first screenshot shows you the above commands successfully carried out. The second screen shows the same thing, only this time we move to the sd-card, look for the dmesg.txt file with the ls command, view it, and see that yes, it is indeed present on /sdcard/dmesg.txt. This second step is not necessary, all you need do is open your file manager, go to internal sdcard, and you will find the dmesg.txt file at the bottom under all of the folders. Move it to your ext-sdcard and copy to PC if you have/use one.

* Because you have this insane, repetitive crash report, once you get the dmesg.txt file created to sdcard, reboot to Safe Strap and from there, use the Safe Strap File Manager to copy the file to ext-sdcard, OR, you can plug in your USB cable to PC, go to the Mount button in Safe Strap, check boxes for Internal and External sdcards, tap the Mount USB button, and these two sdcards will open Windows File Explorer windows that you can use to drag and drop the file to your PC.

** If tapping the Mount USB button does not immediately open the Windows Explorer windows, unplug the USB cable, wait to hear the audio disconnect sound from PC, and plug USB cable back in. The cards will mount in Windows and the Explorer windows will open.

If you wanted to, you could even right click in these windows and Format either or both sdcards. But DO NOT DO THIS for obvious reasons.

I did use this option when I wanted to start fresh, and that is how I lost my /pds file because I had not backed it up. It really will Format these cards!

The third screenshot shows the dmesg.txt file, selected in CM11 File Manager, ready to copy or move. If you use ES File Explorer, you can copy to Dropbox, with WiFi turned on, copy it to your home PC, or with Bluetooth turned on, copy it to another Android device or anything with Bluetooth.

Because ES File Explorer has all these neat copy to Dropbox, Gdrive, WiFi, and Bluetooth options, plus is a root explorer, and is completely free and Ad Free, this is a must have app for any serious Android user.

The forth screenshot shows the newly created dmesg.txt file in ES File Explorer.

Dwillian, I am really sorry to put you through all that w/out telling you to become root first in Terminal. I do this so often in Terminal that I "forget" to mention this step as it is just an automatic thing I do out of habit. Now you know how to get that dmesg off the phone and onto your PC or so you can attach it to a post to show others members here in XDA.

If you need much more detailed system logs, use a nice System Log Reader like CatLog - Logcat Reader! Also free and very powerful. You then get *everything* in the system log, can save it to a text file anywhere, and you can use a

Filter Word

to thin out so much information such as "phone" to only show log entries that pertain to the phone such as your "com.android.phone process stopped unexpectedly" that is constantly showing up. Nice free tool!

I swear to God, I am going to genuinely help you and get a sincere Thanks button tap out of you, one way or another, bra. LOL! :laugh:

You are probably fed up right now but you do now have the tools you need to document and log this issue. This would be *very* helpful to someone trying to debug this like Michael or even maybe ourselves because we can see what is going on. What you really need to do if you can manage it is (You can only do this in Trebuchet Launcher. Otherwise you must go through /Settings/Apps/Dialer.) to hold finger on the Dialer icon, when you feel phone shake and see the circle App Info icon appear, top right screen, drag the dialer icon on top of it to open Dialer in App Info. Then as soon as you see the Clear Data button light up, tap clear data fast! This will clear any corrupted dialer data and may put an end to your incessant error screen once and for all. I hope so. Fifth screenshot show the Dialer in App Info and there is is... Bottom right, the "Clear data" button. Nail that biatch with a quickness and a purpose, dude! :fingers-crossed: