Related
Well again.... Im about to lose my minda because of this damn thing! Now I'm getting a fc every 5 sec... Process acore? My tab is essentially dead? Can't do anything author a fc, can't go into settings our anything... I want to smash this thing! I just got it working well and now this? Anyone know what that process is? I cam do anything with it now, cant load a new rom because I can't get into settings. Its just in an intimate loop of fc. The real disaster is im in idaho, where I got it as a gift, and I'm flying back to nc in the morning.. Can't take out back before I leave..
Anyone know anything about the fc?
Sent from my SAMSUNG-SGH-I897 using XDA App
Setting---appliction----Clear the contacts and ContactsProvider data .
I can't get into settings... It fc's every time I try to go into settings. Any other way to do it?
Sent from my SAMSUNG-SGH-I897 using XDA App
I think I need to do a reset, but if I can't open settings I'm lost? Not sure how it happened, it just started doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App
pqrs said:
I think I need to do a reset, but if I can't open settings I'm lost? Not sure how it happened, it just started doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you can get ClockWork to run on boot .You might need to wipe data and reinstall the rom..Not much you can do when it is constantly Fc'ing
Well I don't have cw on the tab, its still stock.. I'm hoping I can plug into a pc, download it and get root that way? Then possibly load a new rom... Otherwise I'm screwed.
Think that will work?
Sent from my SAMSUNG-SGH-I897 using XDA App
Maybe you should restore it back to factory settings...
http://forum.xda-developers.com/showthread.php?t=861950
That will bring it back to how it was out of the box, then start over.
If there are still issues then possible hardware problems?
Had this issue, even after NV flash. I was able to get CW (even with the fc) on and wipe, and partition the sd to 2gb. That seems to have cleaned it up.
This forum is the greatest on the entire internet!
Glad to hear you got it working. Imo, your issue is probably the worst thing about running stock - if you get these FC's, there's really no fix unless you take the risk of using a mod.
I believe it's the same reason why Staples pulled the devices - too many returns due to FC's OOTB.
Yes, it's too bad they did not include the "easy" button to reset to stock. Even with the upgrade, it may be enough to ultimately kill off the device. With all of the recovery images on my laptop now, I can put humpty dumpty back with ease. It's good for me, I plan to watch for returns. I could use a couple more of these.
I got cw installed and vegan, the table works like I'd expect now! This thing is awesome! Thanks for the help.
A resolution
I had this same issue happen to me on a new ROM not factory. I couldn't get into settings either to do the contact wipe. But Titanium was installed on it and I was able to wipe the contact data through there. Just an FYI if anyone else runs across the same problem.
Thanks to you Snyper....I just picked up my tab after placing it down for 10 mins and saw this error. Just a quick search in the thread and there is the answer. Man this forum rocks!!!
Just happened to me running vegan 3
clearing contact info worked like a champ!
thanks guys
I have the same issue. But, I don't have CW installed, Titanium won't load up. How can I manually get the clockword APK file on there to attempt to install it?
Any other ideas?
Gravislord said:
I have the same issue. But, I don't have CW installed, Titanium won't load up. How can I manually get the clockword APK file on there to attempt to install it?
Any other ideas?
Click to expand...
Click to collapse
Clockwork is not an apk. Read this
Post 1
http://forum.xda-developers.com/showthread.php?t=865245
Post 1
http://forum.xda-developers.com/showthread.php?t=892090
roebeet said:
Glad to hear you got it working. Imo, your issue is probably the worst thing about running stock - if you get these FC's, there's really no fix unless you take the risk of using a mod.
I believe it's the same reason why Staples pulled the devices - too many returns due to FC's OOTB.
Click to expand...
Click to collapse
Hi,
Having had this acore FC problem last night, I have a couple of questions:
1) In your post above, you seem to have thought that this only happens with stock TNT. But, in this thread, it seems like others that are not running stock TNT also encounter this problem. So, it this a potential problem with all ROMs, or just with stock TNT?
2) From reading through and other threads, one fix when it happens is to clear the Contacts and ContactsProvider data, either using Settings, if you can get to it, or using Titanium, if you have it. I'm assuming that what both of those steps do is to clear out the tables in SQLlite for the Contacts and ContactsProvider apps. Is that right? If it is, do you, or does anyone know the command lines that would do the same thing?
The reason for the latter question is that when I had the problem, I could still do adb shell. If there was an sqllite command I could have used to clear the problem, I definitely would have done that, instead of having to install CWM, re-partition, and re-flash stock 3452!
Thanks,
Jim
I followed the showcase step by step Rom/kernel and I'm stuck in a pickle I have no marketplace no third party apps and no room on my phone to add anything I still have super user fcs on twlauncher but everthing else still works as far as i know haven't flashed any Roms or kernels cwm is not working guess i got the wrong on 3.0.0.0.1 or something like that tried to flash the cwm for all didn't work and recovery gives me a message that says E:can't mount /Dev/block/mmcblk0p1 (invalid argument ) any one please help I'm new to all this starting to understand I think but still lost on how to fix also my showcase is from n-telos I don't think its any different keyword think it came with 2.2.1 but I think they up graded at the store
Did you do factory reset after flashing the froyo update?
Sent from my SCH-I500 using XDA App
livinsacrfice said:
Did you do factory reset after flashing the froyo update?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It came with froyo but I have tried a factory reset yes
im running cm9 and hefe kernel. my problem im having with my txt msgs is when i go over 160 characters it fails to send and im not sure why its doing this, im using the "go sms txt msg" app as the stock is annoying and a disturbance due to not being custimizable (yes if your going to say try the stock txt msg app, i have tryed and it still fails to send when over 160 characters) and my friends that i am txting have 3g/4g phones so it shouldnt be an issue, so im wondering if anyone else has come across this issue or knows how to fix the issue as i have looked and havnt found the answer to fixing it. i am also having the issue that when i send a pic msg to anyone 90% of the time they will recieve the txt but not the pic, i am also still unable to send/recieve pics over wifi (not to worried as i can just turn wifi off and send pic or recieve them)
Try changing the modem
Sent from my SGH-T999 using xda app-developers app
Try the KG4 modem. Link in my sig.
jeffsf said:
Try the KG4 modem. Link in my sig.
Click to expand...
Click to collapse
is needing to wipe anything necessary before doing this?
E: whats the differences between the 3 modems that are posted in that link?
Jenovah said:
is needing to wipe anything necessary before doing this?
E: whats the differences between the 3 modems that are posted in that link?
Click to expand...
Click to collapse
not to much, some work better in different areas. you could flash kg4 modem or use go sms or handcent sms, there have to setting that will allow you to make long text
You shouldn't need to do anything but flash.
Then again, backups are cheap insurance
Posted from my AOKP-ified SGS4G
jeffsf said:
You shouldn't need to do anything but flash.
Then again, backups are cheap insurance
Posted from my AOKP-ified SGS4G
Click to expand...
Click to collapse
i made a backup, flashed what you recomended, and instantly after flashing and started up i got a android.system.error has stopped working??? any ideas? i even fixed permissions to see if that would help and the error still came up
i am needing help, i am getting an android.process.acore has stopped working and i have to restore to fix it but it only comes back, should i try reflashing the modem?
Jenovah said:
i am needing help, i am getting an android.process.acore has stopped working and i have to restore to fix it but it only comes back, should i try reflashing the modem?
Click to expand...
Click to collapse
Were you on KJ6 earlier? If so, I would go back to that and just keep that modem, unless you really have major issues with it. If you still are experiencing issues, flash back to stock (either with the heimdall one click or the gremlin remover) and start over.
Sent from my SGH-T959V using xda app-developers app
cpkelley94 said:
Were you on KJ6 earlier? If so, I would go back to that and just keep that modem, unless you really have major issues with it. If you still are experiencing issues, flash back to stock (either with the heimdall one click or the gremlin remover) and start over.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
i was using kg4 as jeff recomended for my txt msg issue
E: i must say i am getting annoyed that every time it reboots on its own, it restores back to the kg4 modem and gives me the android.process.acore error
I would try going back to KJ6, and if that doesn't work, use the heimdall one click back to stock and start again from a clean slate. Sometimes multiple flashes can cause problems within the phone and starting over with a one click is the only way to fix it.
Sent from my SGH-T959V using xda app-developers app
I remember Raver telling someone awhile ago the the android.process.acore error was caused by leftover data from a previous flash. I wood save everything with titanium backup, then reflash the ROM, making sure to wipe caches, data, and factory reset. Then restore your apps with titanium making sure to only restore the apps and not the previous system data.
Every time I try to flash the official opo aosp they made it says failed. I've flashed plenty of ROMs over the years so I know what I'm doing as far as flashing it correctly, no idea why it says that.
Sent from my One using xda premium
Uncheck mount system ?
Maybe tell us what your procedure was?
You've got to give more information when looking for help. Otherwise you waste your time and ours.
I installed it a few weeks back with no issues. Twrp 2.7.1.0, I think.
I did a factory reset and then wiped system. No problem.
NaterTots said:
Maybe tell us what your procedure was?
You've got to give more information when looking for help. Otherwise you waste your time and ours.
I installed it a few weeks back with no issues. Twrp 2.7.1.0, I think.
I did a factory reset and then wiped system. No problem.
Click to expand...
Click to collapse
Like with any ROM, I wiped and factory reset and then installed the zip and it failed. Multiple times.
Sent from my One using xda premium
C-4Nati said:
Like with any ROM, I wiped and factory reset and then installed the zip and it failed. Multiple times.
Sent from my One using xda premium
Click to expand...
Click to collapse
And yet you still gave no actual information. Have fun figuring it out.
I shall not be back.
Oh, you do know there are like 4 different recoveries floating around here right?
I'm using the most recent TWRP 2.7.1.0, the error I keep getting when it fails is "E: Error executing updater binary in zip 'it names the zip here' then says error flashing zip 'names the zip here'. No idea why, then below that it says updating partition details... and just stays stuck at that screen cause it failed, so I just always end up going back and restoring a back up. I have no idea why it's doing this.
edit- Could it have something to do with the name of the device? I have the unlocked version sold in america and etc, not the chinese version, but on the stock rom under phone name it said "one" now I just flashed a custom rom and it says A0001 or something like that.
Have you tried downloading again? Could be a bad download. A0001 is normal.
Sent from my OnePlus One
OPO forums had something about this. The latest update changed the name of the device from bacon to A0001. The update script of the AOSP ROM is looking for bacon. One guy said he removed those references from the updater-script in META-INF/com/google/android and got it to work. Same solution did not work for some other people. All the people I saw saying they couldn't flash it were coming from 33R.
So, I've had my rooted G2 for awhile. Automatically updated to D800-20Y a few weeks ago. Decided I wanted to try CM out and used Autorec to get a custom recovery. Everything seemed to work great, booted into recovery and I keep getting error #30 can't make a folder for TWRP backup. Obviously this is during me trying to backup my current setup. What is going on here? I don't want to try to flash anything until I have a backup. Help is appreciated!
mungerank said:
So, I've had my rooted G2 for awhile. Automatically updated to D800-20Y a few weeks ago. Decided I wanted to try CM out and used Autorec to get a custom recovery. Everything seemed to work great, booted into recovery and I keep getting error #30 can't make a folder for TWRP backup. Obviously this is during me trying to backup my current setup. What is going on here? I don't want to try to flash anything until I have a backup. Help is appreciated!
Click to expand...
Click to collapse
I just got " Forced" the D800-20y update last night it kept my root but was wanting to install TWRP also. Did you ever get anywhere with this issue? Where you able to backup?
Sent from my LG-D800 using XDA Premium 4 mobile app
vxkillswitchxv37 said:
I just got " Forced" the D800-20y update last night it kept my root but was wanting to install TWRP also. Did you ever get anywhere with this issue? Where you able to backup?
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I ended up flashing the device with fresh software and traded it off for an s4. I didn't want a device that was going to update on its own without my consent. Never had an issue with Samsung and updates before