As the title reads I continually receive this error only when trying to restore a backup of the DATA partition. Boot, system and system image all claim to restore fine individually but are pointless without data. I spent at least 4 hours yesterday searching for a solution here and on youtube without any luck. Hoping someone has a technical work around to get this restored. I don't have an issue digging into or editing files if need be if you are willing to provide an explanation.
Thanks in advance.
No one has ever resolved this?
Seriously, no help from anyone?
Wow.
Related
Hi,
So I need some help. I rooted my Evo 3D using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1192525
and everything went fine. I created a backup using nandroid (in clockwerkmod in preparation for trying out some custom roms, but upon reboot I got the message:
"the process android.process.acore has stopped unexpectedly. FORCE CLOSE"
at startup. This message repeats if I simply try to acknowledge it and move on.
I tried simply restoring to the backup I created but I get the same message.
I'm not sure what to do next, any help or advice would be greatly appreciated!
ICHNIMBY said:
Hi,
So I need some help. I rooted my Evo 3D using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1192525
and everything went fine. I created a backup using nandroid (in clockwerkmod in preparation for trying out some custom roms, but upon reboot I got the message:
"the process android.process.acore has stopped unexpectedly. FORCE CLOSE"
at startup. This message repeats if I simply try to acknowledge it and move on.
I tried simply restoring to the backup I created but I get the same message.
I'm not sure what to do next, any help or advice would be greatly appreciated!
Click to expand...
Click to collapse
i'm making the assumption you're on a completely stock ROM w/only nand unlock and superuser.apk as you haven't mentioned any other changes. if you've made any other changes, then i would look into reverting those first.
i'm going to give two routes to approach this issue and let you decide which works best for you.
shorter route:
background:the way android is designed is for the /system partition, where all stock apps and stock settings are located, to stay in a read-only state. due to android's setup of having /system stay in a read-only state, all changes/modifications/settings are to be stored on the /data partition. /data is mounted as read/write and /system is mounted as read-only. of course with root access and nand unlock, these can be changed.
suggestion: if restoring your /data partition still results in those FC (Force Close) alerts, i would restore it from a backup as the guide you linked instructs to make before starting.
if restoring the backup still results in the FC message, i would then proceed to erase your /data partition. erasing the /data partition will wipe out all your settings/modifications/changes to all your apps and the system. it should revert the phone to a clean stock state and clear out the issue causing the FC.
long more technical route: logcat contains all the debug output from every application on the phone. it can be accessed through the android sdk, with either of two tools, ddms or adb logcat.
using logcat is definitely a bit technical and it isn't the easier thing to read, become familiar with and research, but its definitely do able! logcat should show what is causing the FC message, but it will be given in java debug code and probably require some researching.
hope that helps! good luck and let us know if you have any other questions/how it turns out!
joeykrim said:
suggestion: if restoring your /data partition still results in those FC (Force Close) alerts, i would restore it from a backup as the guide you linked instructs to make a before starting.
Click to expand...
Click to collapse
I just did this and the problem is gone. I guess sometimes you need someone to point out the obvious to you.
Thanks so much!
ICHNIMBY said:
I just did this and the problem is gone. I guess sometimes you need someone to point out the obvious to you.
Thanks so much!
Click to expand...
Click to collapse
wonderful! glad the solution was my simple fix suggestion as the more complex route takes a lot more time!
lesson learned .. backup backup backup! ive got to the point where i'd rather have tons of backups and no issues .. then a few insufficient backups and issues!
I rooted my phone successfully and passed the test with the app Root Check Basic and I can use Wifi tether and everything. But when I start my phone up and try to use different setting options for my MOFO I get the error:
the process com.android.phone has stopped unexpectedly please try again.
I have tried the system restore,
unfreezing all of my apps,
going to settings manage apps,
clearing the data for each app,
and I also tried doing the system recovery multiple times
and I still get the same error.
PLEASE HELP ASAP
I say thanks ahead of time
Weapon X 20 said:
I rooted my phone successfully and passed the test with the app Root Check Basic and I can use Wifi tether and everything. But when I start my phone up and try to use different setting options for my MOFO I get the error:
the process com.android.phone has stopped unexpectedly please try again.
I have tried the system restore,
unfreezing all of my apps,
going to settings manage apps,
clearing the data for each app,
and I also tried doing the system recovery multiple times
and I still get the same error.
PLEASE HELP ASAP
I say thanks ahead of time
Click to expand...
Click to collapse
sounds good so far, now if your unlocked on cm7 it does that even on my phone
but if your stock you must have pooched it, nothing serious but you will need a computer and RSDlight because honestly, you did everything correct and its still hatin on you follow this link and you should be A-OK and reroot it again
http://forum.xda-developers.com/showthread.php?t=1202666
Thanks for the help! I did try that and I kept getting a error with it. But I just got a new computer and I will try it again and see if it works. If it doesn't do you have any other suggestions?
Reflash with stock sbf and restore frim titanium should be giod
Sent from my MB855 using XDA App
Weapon X 20 said:
Thanks for the help! I did try that and I kept getting a error with it. But I just got a new computer and I will try it again and see if it works. If it doesn't do you have any other suggestions?
Click to expand...
Click to collapse
best thing if that fails is to download the STOCK firmware and try even flashing that, if you come across the error code make sure you post it up in here so we can narrow it down
Just incase the steps above don't work, how would I flash with the stock sbf and restore it from Titanium Backup? I'm sorry I kind of a newbie to the rooting on android all together. Trying to get my experience now with some different forums
Weapon X 20 said:
Just incase the steps above don't work, how would I flash with the stock sbf and restore it from Titanium Backup? I'm sorry I kind of a newbie to the rooting on android all together. Trying to get my experience now with some different forums
Click to expand...
Click to collapse
you would need to use RSDlight which can be found on the threads here or the one i posted above, i would help find the stock sbf but im at work and little on time now to find it. more then likely could be found via google.
everything you need to do can be found in ACS qbkings thread search the development thread and you will find it he does have youtube videos up as well that can help you step through step on reflashing the sbf to rooting unlocking and installing on your phone make sure you give him a thumbs up
Does anyone have a working link for the Motorola Photon 4G stock SBF file? All of the ones I have googled and tried to find were not available links. Anyone?????
Ok so I found out why I was getting that random error message before when I tried to go through the process of getting that stock ROM on the MOPHO to get rid of those errors. It was because I still had my SD and SIM card in still. So after taking them out and going through all the processes I got it working now. Thanks for all of your help!
The process com.android.phone has stopped unexpectedly. Please try again
I would get this same error as well as other system apps crashing on both my captive (Samsung Galaxy S) and Samsung Galaxy SII Skyrocket. The cause was that I restored system apps from older versions of android and they were conflicting with the newer build. When you do the batch restore be sure to deselect system apps such as phone 1.0. Most of these are marked in red so they are easy to route out. Also you can sort by install date to push most of them to the bottom of the list. I did not install phone however I am getting the error now on my new SG2 Skyrocket. Need to test it some more but do not have time right now. It may be CONTACTS/CALLS data, or maybe SMS/MMS/APN Dial Storage data that is the culprit. or maybe i missed contacts 1.0 or phone 1.0 when i did the restore. Anyway I will go back and do it again and let you know my finds.
BTW I am restoring my data to my AT&T SGII Skyrocket which was created on the Captivate running 2.3.3 Cognition 5.2. The SG2II is stock, rooted 2.3.5.
Note, using the Migrate System Data option in TB's preferences may resolve this too as restoring with TB across newer versions of Android have not been this problematic in the past and I forgot to check that option. Haste makes waste.
FIX
OK I got tired of my phone messing up so I took the time out to fix it.
My suspicions were correct, in my case the culprit was:
[CONTACTS/CALLS...cts Storage 2.3.5
You can either choose to not restore the offending data or if you have already done so and are experiencing the:
The process com.android.phone has stopped unexpectedly. Please try again
error you can delete the data for the offending item(s) via TB.
To remove the data just locate in the backup/restore page the item(s) in question in TB and tap on them. choose wipe data. Reboot and it should be fixed.
A heavy handed way to avoid this or if you are not sure what is the offending data you can simply use the restore missing apps + data batch option in TB. This will ensure no system apps are replaced as this is the cause of the problem in the first place (replacing an app or its data with and outdated version).
If you go this route and still need the missing data imported, use google's cloud (account sync) to retrieve your contact, calender, and other data. As for text messages, you can carry these over with a free app on the market Backup SMS.
your findings are awesome! I just bumped into this "com.android.phone" FC problem with my newly flashed Samsung Galaxy S2.
Thanks a lot
Hi everyone
I'm facing a very annoying problem. my Atrix show and explain the problem to me even though I telephonist is all programmatically, they said I need to format but I think I have hardware.
When I turn off my phone every December 6 turns. For example, when I delete one to two applications, photograph shoot, when I reboot the phone by the programs have come back, if my photography is gone, WhatsApp My speech is going back to December 6.Connect the phone to the PC in the same way music, rom, etc. when I threw the zip file .. usb disconnect the look of the phone seems to have deleted files, seems to throw more precisely, I cant go to the factory settings, I cant format sd card.Fastboot mode operations such as hard reset formats'm doing. When he opened successfully but says does not change anything from December 6 phone again Cwm in the mount process data, cache, system, Preinstall, gives an error when formatting. Original GB Stock ROM flashing with RSD, but the phone while flashing process is going repositionable 6 december. Most application itself off, the process terminates, etc.. In short, I can not do any operation with built-in storage, screwing with my head.
Restore backup operation did with cm7 but it did not work .. I'm going crazy I stayed at this rate
ClockworkMod Recovery v5.0.2.0
Checking MD5 sums ...
Erasing boot before restore ...
Restoring boot image ...
Restoring system ...
Restoring data ...
Error while formatting / data!
Click to expand...
Click to collapse
such remains. All unmount / mount have repeatedly tried by .. There's nothing changing.
motorola turkey on the forum topic I said like a friend;
data partition in a way locked there is no problem, linux to interfere with necessary, the easiest services to take, If it fails either of these issues knows linux expert to find, or the phone to open the internal mmc card, remove the atrix in accordance with partitioned, separating reformat back will wear a hardware specialist you need to find. Or one of them will make an application in android professional applications because newly started dating, they needed to find an application that partition control.
Click to expand...
Click to collapse
My english is not good.. When you translate text in many places i used google translate
I hope you can help me and understand. :silly:
Greetings from Turkey !
That was hard to understand, being a non-native english speaker
Please, after recovery fails to write /data, go to main menu-> advance-> show log. There will be the cause of the error.
Hit the damn thanks button instead!
Enviado desde mi MB860
I searched and couldn't find anything on this.
I flashed Infinity Rom on my T-Mobile S5 yesterday. Everything was going pretty well until I rebooted today and I got that error message.
Is there any way to fix it without going through the whole reflashing process again? If I do have to go through the process, how do I avoid this happening again.
Thank you.
The general solution is to wipe the system cache and app cache and data from the application manager. Or you could simply restore your backup of course. Lots more detail in dozens of existing threads if you need any elaboration.
You didn't say what you tried searching for. Since there are literally hundreds of threads about Unfortunately the xxx app has stopped it's surprising that your searches didn't find any of them. I'm not saying that you just claimed to search when you didn't, although a lot of people do that. But if you tell us what keywords you searched on, we can both improve your searches and find the information you are seeking.
.
.
Did you wipe the data when you flashed the new rom? If you didn't, many apps are going to crash including the system ui.
fffft said:
You didn't say what you tried searching for.
Click to expand...
Click to collapse
It sounds like that was my problem. I searched for "com.android.systemui". I probably should've tried something like "the process has stopped."
aooga said:
Did you wipe the data when you flashed the new rom?
Click to expand...
Click to collapse
Yes, I wiped the data and cache before I flashed the new ROM. It was working fine, then I got that error during a reboot. I just decided to reflash with Infinity (I'm a minimalist) which has been working very well. I didn't have backup, so it took a while, but I didn't lose any data.
I've been backing up with Titanium. My next task is to set up nightly automatic backups to my NAS.
During the backup restore, the system partition fails and gives me error 255. I'm restoring from PAC B322 to Stock B322, so there shouldn't be a partition size problem like I was having before... Has anyone else had this error?
Bueller?
Nobody has seen this before? Google hasn't been very helpful..
Please give more info around the error 255. So others didn't have this problem may be able to help.
xordos said:
Please give more info around the error 255. So others didn't have this problem may be able to help.
Click to expand...
Click to collapse
Well, that's really all there is to it... I try to restore a backup and as it is running through the system partition, it stops and says "error 255", failure to restore. I was hoping that was a more common issue
I tried at least 5 times, made separate/new backups, different ROMs, all the same error.
chill8888 said:
Well, that's really all there is to it... I try to restore a backup and as it is running through the system partition, it stops and says "error 255", failure to restore. I was hoping that was a more common issue
I tried at least 5 times, made separate/new backups, different ROMs, all the same error.
Click to expand...
Click to collapse
A few things you can try, save the twrp log and upload to this thread; use a different sd card; reformat the card then try backup/restore.
Uhm, what version of TWRP?
Also, try without MD5.