hello.
i have run into some problems when trying to install the stable mod described in the guide from the sticky post at the top of this category. well more or less, i referenced other guides as well but they were all effectively the same.
after rebooting post installing the cyanogenmod image my phone seemed to be functioning fine. i noticed that the google apps were not available (despite having used the backup and restore proprietary google apps from the recovery menu) so i restarted the phone in recovery mode and flashed the google addon and rebooted again. as soon as the phone came up this time it started throwing up error messages:
"Sorry! The process com.android.phone has stopped unexpectedly. Please try again."
i can dismiss the error dialog but another replaces it. sometimes the process named is different. i cannot recall the other examples right now. i have tried to turn the phone off with the power button, the confirm dialog does appear but is buried under the error messages mentioned above and i cannot get to it to confirm. i have tried holding the power button down hoping there is some hardware shut down. no dice. i am getting ready to pull the battery but thought i better throw this out to the masses before i did so.
huh interesting. it just stopped doing the above. it chimed and then displayed the boot screen in a frozen state.
the only way i deviated from the general directions in the above mentioned post were to flash the google addon package after a reboot as mentioned before.
how safe is it to pull the battery and what would the next steps be? if i wipe the "data/factory reset " and then reinstall the cyanogen img will i be back where i was before the google addon install? i am not really sure what command eliminates the android installation. perhaps i need to do a more extreme wipe of the device. alternatively i can execute a nandroid restore.
now it is back to the dialogs again.
i am mostly concerned that pulling the battery may brick the phone. am i being irrational?
the phone is a nexus one. i am in the uk on vodafone if that is relevant. the packages i installed are the ones listed on posting above.
i did not flash the radio.
any help would be greatly appreciated.
e
edit- i have fixed the issue. i was able to use the adb reboot utility to boot to recovery mode. from there i was able to restore my backup image. i then retried installing the cm and addon packages and kept having the same issue. finally i tried to download a new version of the addon img and that worked. for some reason i had to unmount and remount my sd card after i got everything working again.
correction
sorry the packages i installed were not the ones listed in the post above. they were the ar recovery img (that was the same) the cyanogenmod 5.0.6 image and the google addon.
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.
After flashing a few kernels yesterday, my phone started randomly FC'ing everywhere: Facebook would close when I clicked something, Gtalk after every other message, etc.
Flashing back didn't fix it and my last nandroid was months ago. I started clearing app data and that didn't do it either. In the past I booted to recovery and wiped cache & dalvik cache a few times and it made things better. This time the FC's kept coming and the best option looked like a factory wipe.
Instead, I found a solution that got me going again, cleared all my random FC's, and my phone is running smooth as new. Launcher Pro doesn't crash any more on startup like it did EVERY time, nothing has crashed all day. Here's what I did:
If you don't already have Amon_RA or TeamWin recovery installed, do that. Unrevoked/Revolutionary installs Clockwork/TeamWin but I prefer Amon_RA
Get Root Explorer or another app that can access /data and /cache with R/W permissions
Delete /data/dalvik-cache (delete, do not rename)
Delete /cache/dalvik-cache (delete, do not rename)
Shut down quickly, you won't be able to boot straight into recovery using Quick Boot because all apps will FC now
Hold volume down+power to get into the bootloader (white screen), then press volume down to get to Recovery and press power to select it
In recovery (black screen), wipe cache and dalvik-cache (I do it twice just in case)
Reboot as normal and let the phone get situated after it's done booting. It will take a while (my boot was about 5 minutes, then another 10 before all my apps showed up and it stopped being choppy)
Post back here and report results!
You have to do both the file manager delete and recovery wipe for this to work.
Doing it also had the additional benefit of freeing up a bunch of space (20mb+ for me). I was expecting some apps to be choppy on first load while rebuilding their caches but they were not. No app preferences were lost.
The reason I said delete, do not rename, is that renaming will get your device to 0mb quickly, apps won't be able to rebuild their caches, and previously working apps will keep FC'ing until you do it the right way. I made this mistake.
Please post back and report if this worked for you!
nice! glad you found out a fix because this has happened to me about 3 times in the past month or so. but the only problem i see is that when ever i try to open apps when they are fc'ing left and right is that they fc as soon as i click them. so root explorer wouldn't work for me haha. but glad it worked for you.
PhxkinMassacre said:
nice! glad you found out a fix because this has happened to me about 3 times in the past month or so. but the only problem i see is that when ever i try to open apps when they are fc'ing left and right is that they fc as soon as i click them. so root explorer wouldn't work for me haha. but glad it worked for you.
Click to expand...
Click to collapse
Mine crashed too but only after I deleted the folders. I was lucky enough to at least be able to open most apps but they would crash right after.
An alternative that should work in that case would be to download another app that can access /data and /cache with R/W since it won't have any cache at all. Unfortunately uninstalling the app does not delete its cache from those folders so it has to be a new app.
Both ES File Explorer and SU File Manager should work in that case.
Let me know if you get a chance to try it!
This has just started happening 30 minutes ago or os.
I was running the Sentinel ROM and tried applying that Tablet-Mode fix mentioned in the thread. It failed, and I had to reflash ROM from scratch (so I wiped all data and flashed it). Then I decided I should download 4-5 ROMs to play with, but noticed that I could not. Thought it was just a temporary glitch, I downloaded them from the Goo Manager app and installation went fine.
So I wiped again and flashed a new ROM (the AOKP) and I noticed the downloads still don't work. Tried with Opera, Chrome, and stock Browser. I always get the "Download Unsuccessful" message with the "Untitled" as file title. Any browser, any file, any website, like I said. And it fails immediately - it's not like it tries to download at first.
I also rebooted to TWRP and wiped dalvik and cache, and fixed permissions, still the same problem occurs.
Any help?
Ended up solving it by completely wiping every single thing and reinstalling the PA ROM.
After i tried
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
on lollipop on vodafone uk, i got this error message on boot, i press ok and after reboot i got no root
Then i install superuser through twrp that i previously had and keep getting this error message on boot.
The thing is i cant get past it, its covering the whole screen no operating system ui just that in a white box and a press ok, which doesnt work until after 2 minutes.
EDIT: its just constantly saying programs has stopped responding in a loop and cant get into android system. How do i fix this, i tried fixing permission in recovery but that didnt work.
So what i can do without losing all my work on my phone.
I hope you made a backup before flashing root files
Boot into recovery, clear CACHES, reboot - see how you get on with that
If you flashed CF Auto Root, there was no need to flash SuperSU, as it comes part of CF Auto root, someone else just did that and ended up in a boot loop, had to wipe the phone and flash a stock ROM
Thats the thing i didnt, i watched a video saying it wouldnt delete your files rooting and decided not to backup.
I was stuck on samsung logo half the time and other times stick with "unfortunately MTP application has stopped." in a big white box blocking me getting into android.
I tried fix permission, clear cache and delvin cache and nothing worked.
I just system wiped and got in but lost all my work.
Fortunately Google backed up most of my photos and videos and contacts but no sms messages.
Now i gotta get all my apps back on my device and get it back to how it was and hopefully i did not mess any important texts.
Note to self: Always backup.
EDIT: i just had gaaps not working and giving server error, after trying out ways to fix that i tried all the normal stop app and clear cache, and then did fix permission in twrp, and after doing "also fix SELinux contexts" it messed me over and got me back to that white box.
so another note to self not to use "Fix SELinux contexts" as that messed up my system after getting 30 apps back installed.