Related
Ok, so I rooted my phone yesterday via "one-click root" and worked like a charm. I deleted alot of bloatware and used info in a thread here in the forums as far as what to remove (Kindle, MobiTV, Amazon Mp3, etc But I also wanted to do a lag fix. I came across a guy that had a lag fix that I wouldn't have to use a pc for that was just a update.zip file that I would install. I followed his YouTube video step by step and had NO problem all the way up until I rebooted my phone. When I did so, my boot animation disappeared and my phone went BLACK! I contacted him and he had me clear user data and sd files and clear cache from the recovery screen. Now when I try and start my phone everything boots up but when I get to my homescreen I can't stop getting Force Closes and this is what the messages say:
----------
Sorry!
The process android.process.media has stopped unexpectedly. Please try again. dumpstate_app_201008310134_android_process_media.log has been saved. Use *#9900# to copy out log.
----------
AND when I try to open the Web it says:
----------
Sorry!
The application Web (processcom.android.browser) has stopped unexpectedly. Please try again. dumpstate_app_201008310147_com_android_browser.log has been saved. Use *#9900# to copy out log.
----------
And same for Gmail App when I try to open it.
And they won't stop popping up. Barely long enough for me to open ANY apps.
I don't know much about rooting yet but I know I probably need to re-install firmware or something that includes ALL the bloatware including the apps I removed with my Root Manager. I just need advice or a solution or something because its deffinatly making me mad!
Thanks for all your help!
Kyle
i had that exact same thing happen to me, but that was when i tried to revert back to non-lag fix. something errored out during the uninstall and i got exactly what you got, a ton of fc's. my solution was i flashed my phone back to factor stock using odin.
probably other solutions, but i chose the cleanest route, maybe not quickest.
Not sure if you would have enough time but you could try Fix Permissions on the Rom Manager app if you have it. If not you could try ADB pushing the APK and maybe you could open it before all the FC's. I have had that help before, but like said above quickest and easiest will just be to start over. Apply the lag fix first this time (you were probably already thinking this ) they seem to work better that way without any of these problems. For me at least
I have no idea where to start! I am brand new to this rooting stuff so I am LOST! REALLY lost! What is the first step for me? Do you know of anyone who can walk me through this?
It appears that more than one lag fix was applied. Start from a clean rom and start again.
[email protected]
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
lwright84 said:
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
Click to expand...
Click to collapse
I think you might be overreacting here.
First, I haven't flashed the SBF yet but I do remember seeing the fail screen on original Droid SBF flashes and it was something you could ignore. You booted back into Android, right? That means it worked.
Second, the Superuser app is supposed to show a blank screen because the purpose of it to manage apps to which you have granted to superuser permissions. If you just installed it, there would be nothing listed.
Third, Froyo restores apps if you have "back up my data" checked under Privacy settings.
Fourth, you never mentioned the Droid 2 bootstrapper. I wouldn't expect ROM Manager to work properly without it.
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
lwright84 said:
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
Click to expand...
Click to collapse
Captivate is not a Droid 2. I'd be surprised if it works without the bootstrapper, since that's the only way to flash anything on a Droid 2.
My suggestion is to keep trying the SBF. Once you get it to work, get the SW update and then root. From there, I wouldn't go messing with anything in ROM Manager until you confirm the files are 100% legit for the Droid 2. As far as I know, only a few themes are working without issue on the Droid 2 - the ROMs all have bugs.
The same thing happened to me. I am assuming we were using the same instructions to flash the .sbf. Here is a link to instructions I followed.
http://forum.xda-developers.com/showthread.php?p=8245826#post8245826
I did not heed the red flag I got when I unzipped the .jpg file. I saw some error message and ignored it, and went ahead with the procedure to end up as many others with "fail".
Long story short, I deleated the .jpg file and downloaded it again.
When I used 7 Zip to extract the files, this time I had no error msg and everything went smoothly.
Question, Im getting alot of "com.google.process.gapps" force closes on my EVO since I restored a few apps thru Titanium Backup. I rooted about a week ago and never had any issues with this. The only apps that I restored was angry birds and a to-do-list app along with all the data that came with the apps. I have tried cleaning caches and restarting the phone and nothing seems to work... what would you suggest? I seen a few threads when i searched - but they were for the G1 and the Captivate, nothing for the EVO... any help would be appriciated...
TIA
JS3
Did u flash any Rom or Theme??
nope, I rooted and am still using the stock ROM... I was going to flash Frost or some thing, but I want to make sure this doesnt carry over to the flashed ROM, or if there is a fix...I would prefere to fix it...
I am also getting a force close on the phone process.... when some one calls me and I ignore the call it force closes the process for the phone as well...
Try reinstalling the gapps.apk. One of them must of been corrupted by the data you restored.
do you know where I can find that at? I have never heard of it...
Also the thing that is confusing, is I can still access my market, maps, latitude, people, gmail... etc
If the apk or files were corrupted, I wouldnt be able to access those apps... i will try to reinstall the apk, but I would like to know what I did to make this error happen, so I know not to do it again...
one thing I think it could have been was there were two "people" files in my Titanium Back up... One was up near the top it said "People 1.00" and then there was one near the bottom with a line thru it that said "People 1.1.1" or some thing to that effect... I deleted the one at the bottom with the line thru it cause I thought I didnt need it any more... could this be wahts up with this error?
I can still access People thru the People widget, but some times it takes abnormally longer to load my list of contacts...
I can also still access Market, Gmail, Maps, Latitude...
I just clciked on Talk and it seems to be the problem, every time I click Talk it brings up the force close issue...
should I just reinstall the Talk.apk?
I also get "com.android.phone" force close when I decline a call...
when I went into my ROM manager, I clicked the "fix permissions" and it says "error occurred while attempting to run privlaged commands"
Any info on any of this would be great...
Anyone out there
Sent from my EVO while tethered into the Matrix thru Wifi...
Okay well I have googled/searched XDA 'til I was green in the face... I still can't figure out how to fix this issue?
Just answer me this, If I do an entire factory reset - will I loose root?
I have wiped the cache thru recovery, Should I try wiping the delvic-cache also, before I factory reset to see if that works??
I can not find any where to download the "gapps.apk" anywhere, I found this one thread that told me to install these in this order:
1. TalkProvider.apk
2. GTalkService.apk
3. Talk.apk
but none of them worked... they wouldnt even install... it just kept saying install failed...so I found another thread with the 2.2 gtalk and it installed...but Im still getting the error...
I have been getting several other errors, like htc.bgp force close (or some thing like that) as well as com.android.phone force close...
So should I just do a NAND restore or should I do a factory reset instead? OR should I run the RUU and start over to root...??
I am at wits end here and am not getting anywhere with searching...
TIA
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Biggest Fro said:
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Click to expand...
Click to collapse
Thanks for the input, I was beginning to think I was invisible... lol... I will try that and see what happens...
Well, I went ahead and tried one more thing before I did what you said to do and I think it worked... I went into my EVO while in Disk Drive mode and I cut my entire Titanium Backup folder out of the phone and copied it onto my Desk top. Then I went into my OLD EVO files from the end of the year and I copied the latest folder into my phone. I then went to Charge only, clicked TB and refreshed the app list... Then I was left with a ton of apps that were not installed on my phone. I then went thru each one and restored the ones that were still installed and deleted the ones that were not... (except for the stock apps that came with the phone), so far so good... I will test it more tonight and see whats up, have not gotten any force closes since I finished...
One thing I would like to know tho - where can I get the stock dialer.apk
Some how it got deleted off my new EVO and when I try to load up one of the htc.dialer.apk from my old EVO - the new one does not recognize it... I am currently useing "dialer one" from the market - but I would prefere to make my NAND back up of the Official stock ROM with all the stock apps...any ideas?
EDIT: Okay, fixed the com.google.process.apps issue but did not fix the other force closes... I guess I will have to try the steps above - and worse case - ill just run the RUU and start all over...
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
sw99 said:
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
But thats the thing - I didnt download anything - I restored two apps, one was opera mini with data and the other was spareparts... then I lost my htc dialer - so I installed Dialer one from the market... I dunno Im just gonna have to do the stpes above and if they dont work - Ill just wipe and run RUU and reroot... no biggie...
Okay I did a NAND restore... then I went thru and set up ALL my apps and settings again and then I did a fresh NAND Backup with clockwork first AND then Amon_Ra... all seemed well except, after I did the Clockwork Backup... I was getting "com.smithmicro.DM has stopped unexpectedly" so searched and read a little and it seemed to have some thing to do with the PRL/Profile updater... so i went into the settings and opened the app manager and cleared the "data" in com.smithmicro.DM and then I restarted the phone and that seemed to fix it... thanks for all the help...
JS3
I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?
Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.
Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.
Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.
I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.
the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???
That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?
Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3
I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.
This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App
Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.
I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....
Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk
^ This is a guaranteed solution to any unexpected FC problems.
k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.
I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.
No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.
I have got a pop up message "Sorry -The process com.android phone has stopped unexpectedly. Please try again." This pop up will not go away at all it appears straight after I press force close. This means I can not access any of the setting on the phone. I believe my SD may be corrupt, as when I try to system restore it just goes to reboot.
I have tried several things like trying to reinstall clockworkmod so I can get to the system restore but the phone just keeps jumping to the boot screen.
I have read in other threads about similar problems and use md5sum to check if I have the correct versions to install. I believe that many if not all data on SD is missing or corrupt. My phone is a brick and I dont have a clue where to start.
I have a orange San Francisco which was running japanese jellyfish 2.2.
All help gratefully welcome
Basically is there any way to wipe my SD card then install what I need onto it, then place into the phone to access the phones system restore to then reinstall every thing or at least access the phone to reset it.
Try put in another SD and see what happens.
i have a sim problem with app rootexplorer