Develop Bugs

Stuck in a bootloop!

I plugged my phone into my computer to charge it earlier today, and after a delay of a few minutes, it rebooted into a bootloop. I've been on CM7 nightly 107 for a few weeks now without any issues and having rebooted several times, so I'm not sure what the catalyst could've been. It was at ~30% remaining battery life before it rebooted, so it didn't power down out of necessity.

probably gonna have to wipe and start over.. just hold down the volume down button and power button at the same time.. wipe all then reflash the rom..

I've tried wiping cache and dalvik, but I really don't want to lose my installed apps and settings. Is there any other option, or am I stuck with a factory reset and reflash?

Install Titanium Backup and backup your apps then reboot your phone into recovery. In recovery, wipe user data and reboot. After you go through the inital setup try to duplicate the problem. If it doesn't happen then restore your apps one at a time and try to duplicate the issue after each app restore. If after restoring an app, you are able to duplicate the issue then uninstall the app and see if that fixes it.
If it does happen again prior to restoring apps you need to reflash the ROM. If after reflashing your ROM you have the same issue try a different computer. If it happens on one computer and not the other then the computer is suspect. If it happens on both then the phone is suspect.

I can't get into Android, so I can't back up my apps. Will reflashing CM n107 (or a later CM release) have a chance of fixing it?

Reflashing may work, give it a shot but if that doesn't work then do a full wipe and flash.

Alright. Not what I was hoping for but it's definitely a helpful answer. Is there some procedure for marking this thread solved, or should I just let it sit?

Flashing the rom again alone may fix your problem true.. But if this doesn't then wiping is your only option.. Just let this be a learning experience. Probably every one here has gone through this before once or twice and learned from it. Get an app like titanium backup like mentioned and backup your apps so you don't have to reinstall from scratch. It's such a time saver. Then you can learn how to backup other things like email settings and messages. I recommend sms backup for your messages if you like to keep those.. And in Titanium backup look for the one called Email Settings and you can usually back that up and save your email accounts and all emails. Good luck!

Aeltar said:
Alright. Not what I was hoping for but it's definitely a helpful answer. Is there some procedure for marking this thread solved, or should I just let it sit?
Click to expand...
Click to collapse
No prob. I don't like it when I have to do it either. You don't have enough posts to retitle the thread so don't worry about it.

Stuck on lockscreen after reboot

On both Blazer (w/ rogue and Lost Kernel) and Calks 2.0 (only tried rogue) whenever I reboot my phone nine times out of ten, it hangs on the lockscreen with a random date and random time flashing back and forth between no signal and the regular status bar symbols. It is unresponsive to touch and repeats the process of the keys lighting up, screen comes on for about 4 seconds, keys turn off, screen turns off. Repeat... If I hit the power button, the pop up shows up but I can't touch anything so I end up having to do a battery pull and reflash the rom. I've re-downloaded both roms to rule out a bad copy. I over-wipe every time I flash a new rom formatting system, wiping data, cache, and dalvik, and then flashing Calk's format all.
I messed with it last night and it seems pretty random but more often than not, it happens. If I try to restore a nandroid I had made recently, it does the same thing. In other words, there were multiple instances where I flashed the rom, got it set up, booted to recovery to make a back up, and then it wouldn't boot back up NOR could I get my back up to boot up.
What in the hell could be causing this??? Please and 1000 thank you's!!!!

First of all, sorry to tell you I don't have the answer.
I have this exact same issue and have tried almost everything you have tried, (I didnt have a back up since I just got this phone not too long ago).
My issue started at work when my battery died really fast in the middle of the day after being fully charged. The phone got hot and I just pulled the battery to stop it. Then I came home and am having this exact same issues.
I've spent the last few hours working on resolving this without success. Hopefully someone out there knows how to resolve this issue.
Edit: I am on Rogue recovery 1.10 (cmw v 5.6.2.7) and on Blazer ROM [11/26/11] [v1.2]
Might be the rom since we are both on Blazer...Im gonna try another. Hmm we are on the same recovery too!
Thanks!

Why not flash back to stock and start over?
Sent from the future.

FIXED!!
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.

VegasEvo4G said:
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.
Click to expand...
Click to collapse
Yes this has been an ongoing issue and posted in a few places. Also remember that when Go Launcher updates this may happen to you again. You can always use adb and push a launcher over to your phone incase you find yourself stuck like this again. Or delete launchers so there is only 1 choice

I finally got rid of this loop. I was able to flash a rom via the recovery menu in clockworkmod, since for some strange reason it won't recognize my sd card now.
Playya, so if I wanted to push a recovery on my phone (I have clockworkmod v. 4.015 installed but it won't recognize the sd card no matter what I do to it), can I do this from Root Explorer? ADB? What commands would I use? I am on Linux and am looking for a guide. Thanks.

Nandroid complications?

For the record, running amon ra 3.0.7...(I forget exact version, it's blue and uses capacitive back button) and I wiped everything 3 times before flashing the following ROMs.
Ok so the other night I went ahead and tried Deck's ICS ROM alpha 5. For the most part, a very beautiful port and can't wait till it stabilizes a little more. I can tell It's going to be a beast. But prior to flashing, I did a full nandroid like I always do, and TB backup. Flashed said ROM, tried to restore apps, few complications; couldn't restore games, certain apps such as zedge, or maps. Had to install from market because it would hang, but still restored data upon install. Figured this was due to the ROM having bugs....
Albeit beautiful, couldn't live without calendar, and certain apps wouldn't work. So I restored my decks 1.3d nandroid and instantly got hit with problems. Half my apps showed as properly installed, half of those actually worked without FC'ing. Downloaded maps cuz again couldn't restore, and instantly FC. So I reboot, and get constant FC's from random apps. So I wipe again, this time everything beside sd 4 times, still same problems. So since I wasn't on wifi to pull the ROM I uploaded to Dropbox, I simply did factory reset. TB now restored fine besides games which still puzzles me, but maps went fine.
I've had similar problems with Nandroid in the past. The only use I seem to get is just maintaining the ROM, everything else is fubar.
What is causing this? Is there a fix? Is it simply a pebkac? (Problem Exists Between Keyboard And Chair)
Sent from my OG Evo 4G via XDA app. Did I mention from inside my pocket?

I use that version and flash a lot. I've never had anything like that happen. Are you wiping everything except bat stats and SD? Did you try and fix permisissions? Do u run an ext3 or ext4 partition? Could there possibly be a problem with your SD card. Perhaps back everything on it up reformat and partition and restore your stuff to it. Maybe you could run a disk diagnosis program on your computer to see if there are physical errors?
Just a few suggestions

fitz420 said:
I use that version and flash a lot. I've never had anything like that happen. Are you wiping everything except bat stats and SD? Did you try and fix permisissions? Do u run an ext3 or ext4 partition? Could there possibly be a problem with your SD card. Perhaps back everything on it up reformat and partition and restore your stuff to it. Maybe you could run a disk diagnosis program on your computer to see if there are physical errors?
Just a few suggestions
Click to expand...
Click to collapse
Haven't tried fixed permissions as I just factory reset from in the ROM itself and restored apps as if a fresh ROM, but I will next time issue arises. I have no partition, but have considered doing so but keep putting it off. Been wanting to format my card and one by one out things back on it, but yeah, I wipe everything but bat, unless full, and sd. But I have noticed this issue usually only arises when I have already done a full wipe of everything and try to flash back. If I were to just flash over my current ROM, then restore back, everything works fine....kinda confused...
Sent from my OG Evo 4G via XDA app. Did I mention from inside my pocket?

[Q] Unusual problem installing Jellytime R16

I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?

I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?

Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.

I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).

foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.

Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."

bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?

Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.

Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.

if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?

Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.

Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.

Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app

[Q] unfortunately the process android.process.XXX has stopped

So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.

Are you doing full wipes and factory reset? If you are doing this between each flash then it sounds like you are restoring bad data into your apps.
Transmitted with a portable device using Xparent Blue Tapatalk 2

Try re-flashing the latest Gapps and seeing if that will help.
It has done when I've had the same problem before.

edfunkycold said:
Are you doing full wipes and factory reset? If you are doing this between each flash then it sounds like you are restoring bad data into your apps.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I thought the same thing so I tried without putting back in any apps. And still happened. And if I flash Sonic with TB it does it right away when I get booted up for some reason.

KidCarter93 said:
Try re-flashing the latest Gapps and seeing if that will help.
It has done when I've had the same problem before.
Click to expand...
Click to collapse
Thanks, I'll try to find the latest Gapps now and report back if it helps out. But I'm not real familiar with the Gapps part so it may take some searching to figure out what theya re for Sonic Rom if it matters the rom.

This is the reason why I do not do any backup.. Most stuff on my phone is not important enought to require a back up.. If I have issues, I just reinstall the rom and my apps from the market.. I have only reinstalled my current rom once, and that is because I was not able to change my current prl...

Jorgy11 said:
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Click to expand...
Click to collapse
Sounds like you need to do a FULL Wipe before you Flash. Also make sure your Downloading the Rom over WiFi, or Hardline.

prboy1969 said:
Sounds like you need to do a FULL Wipe before you Flash. Also make sure your Downloading the Rom over WiFi, or Hardline.
Click to expand...
Click to collapse
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.

Jorgy11 said:
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Click to expand...
Click to collapse
Do not restore anything with TB whatsoever and I can assure you it will work. There is corrupt data somewhere.
Transmitted with a portable device using Xparent Blue Tapatalk 2

Jorgy11 said:
I have been doing a full factory reset, wipe system, wipe cach and dalvic. I downloaded the Roms onto my computer and transferred them to sd card. It happens for all ROMs except the stock backup I made.
Click to expand...
Click to collapse
The process I use for Flashing Roms is the same one I've always used. It's the one that's in my Sig. I'll also relink, in case your on the mobile. I have used it for a very long time now. It avoids a lot of the hassles of a bad flash.
http://forum.xda-developers.com/showthread.php?p=17647821

Thank You All
Thank you all for your help!!!
So far I have managed to flash the rom and reboot several times with no issues.
I have only had this GS3 for a week now and I feel I can finally play with some roms and see what I like. I usually find one I like and stick with it. On my EVO Shift I used the same rom for 2 years.
Here is what I did for anyone that may have same problem:
Wiped everything, per-normal.
Loaded ROM.
Loaded a few of the apps I wanted to keep some settings for (like GO Launcher and Handcent) using Rom Toolboxes App manager.
I then rebooted to see if I had any problems... none.
Used Rom Toolbox to install just the apps and no data for my other 50+ apps I wanted to keep.
Made Nandroid backup, which forced reboot... no problems.
Installed Titanium Backup, this is where I was nervous because I thought it might be that app causing problems with asking about new ID and such. Installed just 2 apps that I wanted to keep data for that Rom Toolbox for whatever reason didn't have, maybe I didn't have a recent backup. 2 apps were Tasker and GO Bookmark widget. When asked to change ID I selected "later" and after restoring 2 apps I imediatly deleted TB.
Reboot to see if I got errors... none
Setup all settings and tweaks I wanted.
Made Nandroid backup... no issues yet
I then deleted all TB backups I had on SD card figuring one was the culprit.
I am still nervous to re install TB but at least as of now I have a working nandroid to revert to so after a couple days I will reuse it.
As of now I have had no issues what so ever... and I can tell battery life on this Sonic rom is much better.

Glad your all sorted out . I do not think that Titanium Backup the App itself is was causing the issues. Although I do recognize somethings that could. Restoring GoLauncher with settings Data could cause issues. Especially from one Rom to the next. Hopefully your not trying to restore the Data settings you had on the Shift. Also with Handcent, I would not restore settings across different Roms.
TEAM MiK
MikROMs Since 3/13/11

com.android.phone has stopped
Jorgy11 said:
So I'm having a problem I can't seem to fix.
I'm rooted, have been running the stock everything but with a few tweaks and some bloat removed. Everything works great but I am hoping to improve battery life. So I researched a few ROMs and pick a couple to try. I can flash them just fine with no problems, get all my apps back and set up with no problems. and I can use the phone all day just like normal.
Now the problem: if ever I have to restart for some reason, or even after I make a nandroid back up, when it restarts and boots up I eventually get several messages where processes are one by one stopping. until the phone is useless and froze up.
So it goes through 10 or more of these:
Unfortunately, the process android.process.media has stopped
Unfortunately, the process android.process.phone has stopped
etc, etc,etc
I have tried everything I could find on here to fix, but it seems all fixes are for a single process failing. This happens to me on all Roms I have tried, but I am just wanting to run Sonic. Even if I restore the nandroid I get the messages. If I factory reset or restore my kid-of-stock backup I am fine. If I start over and reflash a clean Rom I can set up and use but as soon as I restart it happens again. Sometimes when restarting I get a message about android updating but can't figure out how to stop that from happening.
Thanks in advance for any help!!! This is very annoying.
Click to expand...
Click to collapse
I had the exact same problem with a reoccurring message that would flash on and off every second or so. I did both a data restart then a reboot of the android software by pushing the down volume button then holding the power button. When the LG logo appeared I released both buttons and followed the instructions for an android factory reboot. Apparently it is the SIM card. The android com.android.phone communicates with the SIM card and allows calls and texts to be sent and received using the android software. My SIM card got damaged somehow and could not receive the call from the android app com.android.phone. I had to buy a new SIM card for ten dollars and had my stored files on the SIM moved to the new one and no more problems. Telus and Bell move the files to the new SIM for free i'm sure other major service providers offer the same free service.

@pokey2000 Thanks for that info. But this is the Sprint S3 section. And the user you are replying to has a Sprint S3. Sprint phones are Cdma and do not have a removable sim card.
His issues where resolved 6 months ago. This is the second thread you bring back up that is old and dead. Please look at and read the thread. Before bringing dead topics back up.
Remember search is your best friend, Have a great day!