Related
Hi everyone.
While I consider myself as a veteran in installing and modifying ROMs, I've come by a slightly weird and disturbing problem.
Twice within a week, I've experienced that my phone randomly reboots and then I'm back to stock launcher and all apps in /system/app are inaccesable. I can see them in Root Explorer and through adb, but they are not launchable.
The only solution left is to do a full wipe and reinstall.
The first time I experienced this was while using an MIUI-Au ROM. I thought it might be ROM related, so I wiped completely and installed Oxygen 2.0.1. Then the same thing happened again while I was playing with ADWLauncher Ex, and I did notice some small app-hangs. Not force closes, but I had to tilt the phone before the menu responded.
I've now wiped again, completely. I've even formatted the sdcard outside the phone. ADW is responding fine, but I'm worried this might happen again.
I'm testing if it can be app-related. While on the two installs where it happened, I had installed Swype *and* SlideIT at the same time (although using SlideIT as default). Now I'm using the stock Gingerbread keyboard in Oxygen to see if it might be Swype, SlideIT or the combination of the two installed at the same time that caused this.
But have anyone experienced this besides me?
Is there a solution other than a complete wipe - sort of "reactivating" the apps?
Thanks in advance
Have you tried a non-A2SD+ ROM like CM7 RC2? or ROMs that don't use A2SD at all?
m4a1rifle said:
Have you tried a non-A2SD+ ROM like CM7 RC2? or ROMs that don't use A2SD at all?
Click to expand...
Click to collapse
I can't say I have, but I'll add it to the list of things to test if it happens again. Thanks for your suggestion.
debichu said:
I can't say I have, but I'll add it to the list of things to test if it happens again. Thanks for your suggestion.
Click to expand...
Click to collapse
Definitely try it, because I have the same problem as you last time using A2SD+ ROM (LeeDroid's), I scan + fix my sdcard then wipe and re-install the same ROM, the problem seems to go away at first, then after awhile it came back... from there i switch to non A2SD version of LeeDroid, and even never move apps to SD (aka Apps2SD), the problem did not re-appear anymore...
Well, then the next question is: Why does A2SD+ affect this? Is there a solution 'cause I like the ability to move apps to /sdcard. Or to put it in another way: can I do anything about it?
It's not something I've experienced before. So A2SD+ just stops working? Meh, I don't know Let's see. I haven't encountered any issues so far, and I'm still without SlideIT/Swype.
I think it's due to the way it's accessing the SD-card, some people will not have issue running A2SD, but if your SD-card is faulty(or prone to corrupt), then apps will keep FC like that, fixing it using chkdsk just temporary workaround, it will start failing again... IMHO, A2SD is sensitive to the quality of the SD-card...
but, there is a possibility your case might not be due to A2SD at all
just a suggestion/previous experience...
Hi guys, I need a little help if you don't mind. So I rooted my girlfriends Incredible (slcd screen if it matters at all) with Unrevoked 3.32 and I tried to install Rom Manager so I could flash cwm and install CM7 just like I have on my Inspire 4G.
I had to uninstall it because it won't run. Even when I restart the phone Rom Manager crashes as soon as the phone boots up and I haven't run any apps whatsoever.
Can anyone tell me why this is happening so i can get CM7 installed on this phone. I can boot into recovery by cold booting with Volume - pressed with the power at the same time but I'm scared to just flash CM7 on there without cwm in case it bricks the phone on her.
Thanks
Predtechhacker said:
Hi guys, I need a little help if you don't mind. So I rooted my girlfriends Incredible (slcd screen if it matters at all) with Unrevoked 3.32 and I tried to install Rom Manager so I could flash cwm and install CM7 just like I have on my Inspire 4G.
I had to uninstall it because it won't run. Even when I restart the phone Rom Manager crashes as soon as the phone boots up and I haven't run any apps whatsoever.
Can anyone tell me why this is happening so i can get CM7 installed on this phone. I can boot into recovery by cold booting with Volume - pressed with the power at the same time but I'm scared to just flash CM7 on there without cwm in case it bricks the phone on her.
Thanks
Click to expand...
Click to collapse
Try to fix permissions to see if it helps.
mmuzzy said:
Try to fix permissions to see if it helps.
Click to expand...
Click to collapse
How do I fix permissions if I can't run Rom Manager? I thought that's where you fix permissions, at least that's where I do it on the inspire.
Predtechhacker said:
How do I fix permissions if I can't run Rom Manager? I thought that's where you fix permissions, at least that's where I do it on the inspire.
Click to expand...
Click to collapse
You said you can boot into recovery. Look in the advanced options, you'll see it there also.
Cool. I had no idea about that option. Thanks man
Uninstall it and go from there. Its not permissions, though you can run them in recovery too. The most common way to brick a phone is pulling the battery while flashing something. make sure everything you flash is for her phone and always wipe data/dalvik cache, factory reset before changing roms after doing a nand backup so you always have something to go back to
This post should be in Q & A
Crans said:
Uninstall it and go from there. Its not permissions, though you can run them in recovery too. The most common way to brick a phone is pulling the battery while flashing something. make sure everything you flash is for her phone and always wipe data/dalvik cache, factory reset before changing roms after doing a nand backup so you always have something to go back to
This post should be in Q & A
Click to expand...
Click to collapse
The fix permissions was to try to address why Rom Manager was FC'ing. Fixing permissions often fixes FC's for me so I'm not really sure how you can just brush it off as not it. Perhaps you can enlighten me why anyone would bother running it if it doesn't do anything?
Didnt mean to hurt your feelings also didn't say not to run it. Just went through this problem on my inc and it was not the permissions, it was due to using an incompatable recovery
If rom manager is corrupt what does that make the permissions it contains. do you think the recovery contains diferent ones?
Crans said:
Didnt mean to hurt your feelings also didn't say not to run it. Just went through this problem on my inc and it was not the permissions, it was due to using an incompatable recovery
Click to expand...
Click to collapse
Crans said:
If rom manager is corrupt what does that make the permissions it contains. do you think the recovery contains diferent ones?
Click to expand...
Click to collapse
You didn't hurt my feelings. I just thought it was interesting that you shut it down as if it wasn't a possibility. Apps aren't a self contained entity, they rely on other parts of the OS too so the FC on Rom Manager might be a symptom of permissions issues in another part of the OS such as libraries, config files, directories, etc.
He never mentioned being able to even run it after installing it, let alone get a backup out of it.
You don't need to go through rom manager to run a nand backup and no we obviosly don't know all of this guys problem other than I'm sure his girls pissed for messing with her phone when he doesn't know how to troubleshoot
Crans said:
You don't need to go through rom manager to run a nand backup and no we obviosly don't know all of this guys problem other than I'm sure his girls pissed for messing with her phone when he doesn't know how to troubleshoot
Click to expand...
Click to collapse
sigh... yes, yes you can run a backup without it. again, i was giving advice on something to try since the thread was about ROM Manager FC... nevermind.
good luck OP
I booted into recovery last night, fixed permissions, reinstalled ROM Manager and it all worked perfectly. Now the only other problem i have is my mobile data on the phone. So we originally bought this phone off Craigslist and found it had a screwed up MEID, so i successfully cloned the MEID and ESN from her Palm Pre to this Incredible. Everything now works correctly except for mobile data/web. The phone, WIFI, and Bluetooth all work great but unless she's on WIFI she can't access the internet.
I have the mobile data option checked in the Wireless & Network settings but it still doesn't go online. Can anyone PLEASE help me figure out why i have no mobile data on this phone??
Thanks guys
Did you dial *228. Option 2 afterwards?
Sent from my ADR6300 using XDA App
Yes, i did *228 option 1, and *228 option 2 after i did that.
Does anyone know (1) what a PRL is and (2) if PRL's are different for each phone on Verizon's network or if PRL's are the same for every phone on the network?
To my understanding the prl controls how your phone communicates with the towers. I would call Verizon..can't hurt..you may need to ruu.
Sent from my ADR6300 using XDA App
seems like you may have gotten ripped off here, have you checked if the devise has been turned in on an ins claim or reported stolen, Glad permissions worked for you, good luck
rom manager force closes on me too alot. i just go to settings apps and click clear data under rom manager it works correctly again after
rom manager force closes on me too alot. i just go to settings apps and click clear data under rom manager it usually works correctly again after
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
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!
Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!