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!
Related
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
EDIT: Title should read Jellybean, not ICS
Hi all,
I recently installed AOKP Milestone 1 on my Samsung Fascinate. I'm really loving it so far. I'm coming from Powerwashed GB.
However, I am having problems now creating a Nandroid of my system. I am getting this error:
Code:
Backing up .android_secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Error while generating md5 sum!
This is the error log from recovery:
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dec/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
The first thing I did was flash CWM 6.0.1.5 (blue) with Odin. I then did a cache partition wipe and wipe data/factory reset in recovery, then installed the Rom and Google Apps in the post.
I've done a couple of days of research to no avail. I suspect it has something to do with my SD from the failed nandroid and error code, though the data seems fine on it and I'm able to mount it. Also, I have plenty of free space to make the backup.
Also, am I using the latest/correct version of CWM for the Fascinate? This was an issue that came up when I was doing some research. Rom Manager is no help trying to find updates.
Thanks in advance!
A quick search (always do a search first!) found this thread http://forum.xda-developers.com/showthread.php?t=1971865&highlight=md5 which seems to be your exact issue, and droidstyle was kind enough to give a solution to it. Hope that helps.
Crawshayi said:
A quick search (always do a search first!) found this thread http://forum.xda-developers.com/showthread.php?t=1971865&highlight=md5 which seems to be your exact issue, and droidstyle was kind enough to give a solution to it. Hope that helps.
Click to expand...
Click to collapse
Thanks Crawshayi! I hate to be that guy . Not sure how that thread eluded me.
However, droidstyle's answer seems to be a way to restore a nandroid backup with the same error. I'm not entirely sure my phone is making a complete backup. I'm going to try and downgrade my CWM to create a nandroid again.
Do I understand that correctly?
Thanks!
Well never having this problem myself I can't say I'm too sure what it all means since I've never tested it, however I think you're right about it being a way to restore it instead of create it. I would maybe shoot a pm to droid since he's still active on the boards I believe, and I can't see why he'd have any problems clarifying it for you. Good luck
Also, I completely understand the value of a nandroid in certain situations, but why not just back up the apps you want to with a good program like Titanium backup and just run through the settings quick every time you flash a rom? That's what I do and it doesn't take much time honestly. I've never needed a nandroid to get back to working order this way. You might be thinking, well what about setting up all the home screens again? That would be a pain in the ass but luckily Nova Launcher has a backup function too so when I restore it all my widgets and icons are exactly how I left them. Just food for thought.
Crawshayi said:
Well never having this problem myself I can't say I'm too sure what it all means since I've never tested it, however I think you're right about it being a way to restore it instead of create it. I would maybe shoot a pm to droid since he's still active on the boards I believe, and I can't see why he'd have any problems clarifying it for you. Good luck
Click to expand...
Click to collapse
Good idea -- I'm going to PM and post results here. Thanks again for your help!
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.
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.