I have 2 Incredibles, mine, and my daughter's. I had hers initially, then gave her that one when mine showed up. On mine, I immediately flashed it to the first leak and 2.05 Radio OTA per instructions here, and it worked great.
On hers, I forgot to do a erase all before flashing it, so it still had all of my old data and apps on it. After flashing, I expected to see the screens revert back to their default state, but they didn't. My custom icon placements were still in place on the home screens. The icons for 3rd party downloaded apps were generic android icons. Opening any 3rd party app would cause a force quit. I did an erase everything, didn't fix it. If I went to the market, apps would show as not being loaded, so I loaded them, same results. I then uninstalled and reinstalled, and the apps all worked again.
So, last night, I reverted both phones. Mine went smooth as butter. Hers did the exact same thing as before. So, I went through all the actions, and got it all working again, no problem. Lastly, she went to change the desktop pattern to a picture, and rebooted the phone (not sure why), but it hung on the first "HTC Incredible" boot screen. Pulled the battery and put it back in, no change. Pulled it, let it sit for about a minute, put it on A/C and put the battery back in, and it came back up as expected. When it booted though, it has gone nuts again. All changes since the flashback were lost, icons were generic, I had to uninstall and reinstall everything.
The thing to note here is that once I get it all set up, it works fine, no problems. All I can figure is the fact that I didn't clear everything before the first flash has caused something in memory to become corrupt, and and isn't getting purged when I do an erase all.
So, does anyone have any suggestions?
Thanks,
Doc
did you do a hard reset?
Sent from my Incredible using XDA App
sounds like you need to clear the davlick cache too. just selecting full wipe isn't always enough.
jdkoreclipse said:
did you do a hard reset?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Ok, what's a "hard reset" as opposed to clearing everything via the Settings -> Privacy -> factory data reset?
seanhassars said:
sounds like you need to clear the davlick cache too. just selecting full wipe isn't always enough.
Click to expand...
Click to collapse
And how does one go about clearing the davlick cache?
Thanks!
Doc
I did the same thing when I flashed mine. I just went back into clockwork and did a format on every choice including the cache and did a reinstall and everything was stock.
Thanks, I'll give it a try!
I'd still like to hear from seanhassars and jdkoreclipse on how to perform the options they suggested.
Thanks,
Doc
Hard reset is the clear storage option in the bootloader.
And you clear dalvik cache in the advanced menu in recovery.
Sent from my ADR6300 using XDA App
I'll be redoing the phone tonight so will take all of this into account.
Thanks a lot to all!
Doc
Related
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
I have tried flashing a couple different roms, including Bonsai, TrulyEpic Rebirth. I get everything up and running, and a few reboots later, I turn my phone on, and I'm back at the setup screen, where you enter your gmail acct info, and it teaches you how to use the Swype keyboard and everything. I get through all that, and i just have a barrage of "this program force-closed" windows. Everytime I do that, I have to start all over. I've had to do this 5 or 6 times since I got the phone on Monday.
What I do is:
Flash DK28 with Odin.
One-click root/clockwork recovery 3.0.0.5
Let the system do the ext4 conversion
factory reset, clear cache partition, clear dalvik cache 3x
flash rom
restore all my apps
then, a few reboots later, I end up with the setup screen, and the barrage of FC notifications.
Am I missing something?
EDIT: WHOOPS. I'm half asleep and didn't read that right. When you say restore apps, are you restoring a cwm backup or are you talking about the app restoration build into the setup wizard?l
Built in setup app.
I used to have this problem too, it was very frustrating. For me, I finally narrowed it down to somehow corrupting the ROM by using the 3-button instant reboot method. Since I was using the no-journaling mod I figured that somehow I was forcing a re-boot while the system was writing something? I don't really know for sure though, but I can say now that I use QuickBoot and avoid the 3-button method, I haven't had any problems. Good luck!
Thanks. I have yet to try the no-journaling mod, nor do I know what the 3 button method is. I've been using a widget called "boot control", but I'll switch back to quick-boot (i've used it in the past) to see if that helps.
I have a Verizon Galaxy Tab SCH-I800 and I woke up today and it was missing some programs that I had installed the night before. Launcher pro keeps crashing so I had to put the Samsung Launcher back on. Now random programs all keep crashing and locking up the device. I performed a factory reset through settings -> privacy -> perform factory reset.
It restarts and goes to the samsung bootloader and I performed wipedata/factory reset.. It says it does it but when it restarts its in the same condition as before.
I've booted directly to the bootloader and tried it too (volume up and power key). I've also tried to wipe cache with no luck..
Any ideas? Can I root it and put a custom rom on it? I saw that there really aren't any roms for the Verizon tabs.. Any reason why?
Thanks for any help..
I just did a restore with all the stock verizon firmware using heimdall and it flashed and everything went through properly..
I booted into recovery and wiped data/cache and restarted...
SAME THING! It will NOT wipe out my existing data.. It restarts with all of my old programs installed and NOTHING will work.. The OS is hosed. How can I wipe this thing back to factory??
kgelso said:
I just did a restore with all the stock verizon firmware using heimdall and it flashed and everything went through properly..
I booted into recovery and wiped data/cache and restarted...
SAME THING! It will NOT wipe out my existing data.. It restarts with all of my old programs installed and NOTHING will work.. The OS is hosed. How can I wipe this thing back to factory??
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue and don't have ODIN setup for it.
Same Issue
Same Issue
I changed my passwords on Facebook, Twitter and Gmail. After about 30 minutes the tablet finally stopped bringing up my information.
Need help!
Same to me...
I've tried to uninstall some apps several time, GTab automatically rebooted and these apps are still there...
Could anyone solve this issue?
Bump...
Bump...
I'm in the same boat..half my apps crash when you try to open them. I've wiped the data partition 3 times, and the cache as well..not avail. Apps are still on the device after a master reset!
scruffy828 said:
Bump...
I'm in the same boat..half my apps crash when you try to open them. I've wiped the data partition 3 times, and the cache as well..not avail. Apps are still on the device after a master reset!
Click to expand...
Click to collapse
I had that problem, and I wound up sending it back to Samsung. It appeared to be a bad part on the board, so they replaced it and it's on its way back now. Not the answer you want, I'm sure, but call it in and get your RMA number.
student.driver said:
I had that problem, and I wound up sending it back to Samsung. It appeared to be a bad part on the board, so they replaced it and it's on its way back now. Not the answer you want, I'm sure, but call it in and get your RMA number.
Click to expand...
Click to collapse
On your new Tab can you perform a hard reset and have it actually work?
my sprint Tab seems to be in the same boat
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.
Hi,
Hopefully someone has a solution for me.
This morning I switched on my TF101 and when I tried to go home from Gmail the button lit up but did nothing. I was convinced it didn't work. So I treid a few reboots and still nothing. I tried some other launchers and still nothing.
On further inspection I realised that when turning on slide unlock that also didn't work. Changing to pin, pattern or password still shows no unlock.
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Lethe6 said:
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Click to expand...
Click to collapse
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
I managed to clear dalvik through terminal emulator. Optimised apps and rebooted but the problem persists.
Sent from my Transformer TF101 using Tapatalk 2
Reaper1242 said:
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
Click to expand...
Click to collapse
If you have CWM, go to advanced, wipe Davlik.
frederuco said:
If you have CWM, go to advanced, wipe Davlik.
Click to expand...
Click to collapse
Thanks, now I remember I used CWM.
I thought I'd report back on this in case the information might help someone else down the line.
I tried the cache/davlik clear method and that did nothing for me. I stuck with it for a few days and eventually resorted to button saviour. I also realised that not only was the home button and any lock screen not working, but when using the ASUS quick settings in notifications it didn't show all settings.
This lead me to believe something in the system itself had gotten warped.
Today I did a Titanium backup, factory reset and restored all apps, data and system data. Initially it was fixed but on restart the problem casme back. I knew I'd restored whatever had caused the issue. My next step was to do another factory reset. Since it takes minutes to manually get the system back I only restored apps and data.
This time, after restore the issue was gone. So clearly the issue was in a system setting.
So for anyone else having this issue. Backup with Titanium, factory reset and only restore apps+data.