Results 1 to 7 of 7

Thread: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

  1. #1
    Join Date
    Nov 2011
    Posts
    54

    Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    Hi, guys that’s the error message that I get in my tablet. I also get a message saying to force close it. I juts don’t understand from where the hell I keep getting this messages its all upon you to solve this problem. I have tried my bit now its upon you all to look in to this matter and suggest me a appropriate solution accordingly.

  2. #2
    Join Date
    Jul 2011
    Posts
    1,795

    Re: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    Ok I would advise you to re flash the firmware that would be a better solution for you to work on, since it’s a problem that is related with the firmware and hence flashing it with the same firmware would give the solution for you, that’s what you need to do. I know it’s a bit difficult procedure but you need to work on it.

  3. #3
    Join Date
    Jul 2011
    Posts
    1,752

    Re: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    Hi, look on this possible solution from Getting error message ‘Process com.google.process.gapps has stopped unexpectedly’ on Asus Eee Pad and try working on it. so do try and let me know if that solution did help you or not.

  4. #4
    Join Date
    May 2011
    Posts
    1,127

    Re: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    Have you tried resetting it to the factory settings. If not then do give a chance for this solution as well. sometimes it does happen that small solutions gives you the best results. So try a reset method directing it to factory reset. Give a try for the said solution. I hope that works out for you. That’s it from my side for you.

  5. #5
    Join Date
    Nov 2011
    Posts
    54

    Re: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    Quote Originally Posted by Aalap View Post
    Have you tried resetting it to the factory settings. If not then do give a chance for this solution as well. sometimes it does happen that small solutions gives you the best results. So try a reset method directing it to factory reset. Give a try for the said solution. I hope that works out for you. That’s it from my side for you.
    Thanks for the solution but I have already tried the reset method in case if nothing is working I would have to switch to the hard reset method only. Since only that looks appropriate to me as of now.

  6. #6
    Join Date
    Aug 2011
    Posts
    2,180

    Re: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    No other option, then get it replaced. Do call up the service center people and ask them to get it replaced, that’s what you should do. I don’t find any other alternate solution for it. since this is a china tablet and I don’t think there would be any benefit doing some internal modification in it. so better it is for you to get it replaced with a new tablet.

  7. #7
    Join Date
    May 2011
    Posts
    1,863

    Re: Getting error” process android.process.acore has stopped….” In SuperPAD 2 tablet

    One of my friend also had a china tablet and he got it solved by re flashing the firmware of the phone. dude I would ask you to get it done, there are lots of helpful threads available in TA to help you with the same. so you can refer them and find the solution on your own.

Similar Threads

  1. Replies: 7
    Last Post: 29-02-2012, 10:19 PM
  2. Replies: 3
    Last Post: 28-02-2012, 08:35 PM
  3. Replies: 7
    Last Post: 22-01-2012, 05:57 PM
  4. Replies: 8
    Last Post: 04-11-2011, 10:12 PM
  5. Replies: 5
    Last Post: 02-07-2011, 10:17 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,680,026,857.88560 seconds with 17 queries