Hi
Despite several attempts with different file managers and TWRP versions I can't delete my TWRP backups. The only solutions I have is through the recovery mode or a terminal command (rm -rf /sdcard/...).
No issue to delete folders from other directories though.
Is this the same with new backups?
rootSU said:
Is this the same with new backups?
Click to expand...
Click to collapse
Yep
Primokorn said:
Yep
Click to expand...
Click to collapse
odd. i use root explorer, open twrps file, select backups, long press on the backup i want to delete, then press delete(and its gets deleted). what file explorer do you use?
Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?
rootSU said:
Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?
Click to expand...
Click to collapse
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.
simms22 said:
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.
Click to expand...
Click to collapse
I mean for @Primokorn not in general
Sent from my Nexus 5 using Tapatalk
@Primokorn try root explorer
I tried with root explorer, solid explorer and ES file. Nothing works with these apps.
Actually I already had this issue with old TWRP versions.
I manage my backups from the recovery mode now but that's really odd...
Maybe doing a new fastboot flash could fix it. Last time I had to use Flashify to upgrade because I didn't have a PC.
Then I'll try with adb if needed.
If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.
KJ said:
If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.
Click to expand...
Click to collapse
Yep. Better yet, flash a userdata.img I reckon
Problem solved after flashing userdata.img. Thanks guys.
I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP
iliass01 said:
I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP
Click to expand...
Click to collapse
It's too late for me to try but I keep this in mind. I took the opportunity to clean up my internal memory lol
BTW due to this issue ADB didn't work while being into recovery mode. Everything is fixed now.
Related
Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app
Hey guys, I'm no stranger to CWR but I have a weird issue. I have TOUCH 5.8.1.3 installed but when I go into ROM Manager to "Manage and Restore Backups" to rename a backup it says "you must have clockworkmod recovery installed before continuing! Install the recovery through ROM manager first." This only happens in CM9 because when I switch over to CM10a2 I can rename the backups no problem.
Any ideas?
copene said:
Hey guys, I'm no stranger to CWR but I have a weird issue. I have TOUCH 5.8.1.3 installed but when I go into ROM Manager to "Manage and Restore Backups" to rename a backup it says "you must have clockworkmod recovery installed before continuing! Install the recovery through ROM manager first." This only happens in CM9 because when I switch over to CM10a2 I can rename the backups no problem.
Any ideas?
Click to expand...
Click to collapse
Have you checked, do you still have root?
Try 6.0.1.1 Recovery
copene said:
Hey guys, I'm no stranger to CWR but I have a weird issue. I have TOUCH 5.8.1.3 installed but when I go into ROM Manager to "Manage and Restore Backups" to rename a backup it says "you must have clockworkmod recovery installed before continuing! Install the recovery through ROM manager first." This only happens in CM9 because when I switch over to CM10a2 I can rename the backups no problem.
Any ideas?
Click to expand...
Click to collapse
its because you are on a custom recovery of cwm, not official cwm, imo stay away from rom manager and do everything from recovery, but weird it works on cm10
If you could rename backups in cwr I'd be golden.
...twrp
Sent from my SGH-I727 using Tapatalk 2
Go to ROM manager, press the menu button, manual flash override, select your device, clockworkmod 3.x+
Sent from my SGH-I897 using Xparent Red Tapatalk 2
copene said:
If you could rename backups in cwr I'd be golden.
Click to expand...
Click to collapse
You can rename in ROM Toolbox or Root Explorer, just change the file name. Still don't need ROM Manager. I can't think of any reason to even have ROM Manager, unless for some reason you need to go backwards to an official CWM from Sk8's v6.0.1
aycockonxion said:
You can rename in ROM Toolbox or Root Explorer, just change the file name. Still don't need ROM Manager. I can't think of any reason to even have ROM Manager, unless for some reason you need to go backwards to an official CWM from Sk8's v6.0.1
Click to expand...
Click to collapse
I could have sworn I tried renaming it before in Root Browser and it failed the md5 check. But maybe it was me renaming it on the PC. Either way, it worked this time, thanks a lot. Finally I never have to open ROM Manager again!
copene said:
Hey guys, I'm no stranger to CWR but I have a weird issue. I have TOUCH 5.8.1.3 installed but when I go into ROM Manager to "Manage and Restore Backups" to rename a backup it says "you must have clockworkmod recovery installed before continuing! Install the recovery through ROM manager first." This only happens in CM9 because when I switch over to CM10a2 I can rename the backups no problem.
Any ideas?
Click to expand...
Click to collapse
I use this one for everything:
http://forum.xda-developers.com/showthread.php?t=1777970
Works with no problems, even on the new JB stuff.
Be sure & thank Sk8ter fer it!
edit
^ I'm scared of that one. I like backing up to the computer as well just in case and I don't get the whole "blob" thing and the backups that are 20mb. I understand what it's doing by only backing up new or changed stuff but I still feel safer with the original way.
copene said:
^ I'm scared of that one. I like backing up to the computer as well just in case and I don't get the whole "blob" thing and the backups that are 20mb. I understand what it's doing by only backing up new or changed stuff but I still feel safer with the original way.
Click to expand...
Click to collapse
No need to be scared of CWM Touch 6.0.1.1. I had your exact concern until sk8erwitskil shared with me that in 6.0.1.1 you can CHOOSE between the "dedup" format and the traditional "tar" format. Dedup does the incremental backup and has blob folder... Tar format backs up exactly how his previous version (5.5.0.4) worked.. so you have a single (full) backup folder you can copy to your computer if desired. 6.0.1.1 has a much cleaner UI than 5.5.0.4, and works great. Installed a few days ago and have made multiple backups and restores without incident. Also, the progress status bar works in 6.0.1.1. My internal sd has about 1.5Gb on it and it did a complete tar backup in ~ 5 minutes.
DoctorQMM said:
No need to be scared of CWM Touch 6.0.1.1. I had your exact concern until sk8erwitskil shared with me that in 6.0.1.1 you can CHOOSE between the "dedup" format and the traditional "tar" format. Dedup does the incremental backup and has blob folder... Tar format backs up exactly how his previous version (5.5.0.4) worked.. so you have a single (full) backup folder you can copy to your computer if desired. 6.0.1.1 has a much cleaner UI than 5.5.0.4, and works great. Installed a few days ago and have made multiple backups and restores without incident. Also, the progress status bar works in 6.0.1.1. My internal sd has about 1.5Gb on it and it did a complete tar backup in ~ 5 minutes.
Click to expand...
Click to collapse
Ok so if I use the tar method can I delete the blobs folder and just continue on like before? or does the blobs folder automatically get nuked once you set the default to tar? another thing, I notice that with 6.0.1.1 I now have a .nomedia file when I open the clockworkmod folder with my root browser. Is this normal? it was never there before.
copene said:
Ok so if I use the tar method can I delete the blobs folder and just continue on like before? or does the blobs folder automatically get nuked once you set the default to tar? another thing, I notice that with 6.0.1.1 I now have a .nomedia file when I open the clockworkmod folder with my root browser. Is this normal? it was never there before.
Click to expand...
Click to collapse
All the .nomedia does is stop media scanner from looking in that directory. Set it to tar and if it doesn't delete the blobs folder delete it yourself and your good to go.
Sent from my SGH-I897 using Xparent Red Tapatalk 2
My backup with CWM 6011
gmillz said:
All the .nomedia does is stop media scanner from looking in that directory. Set it to tar and if it doesn't delete the blobs folder delete it yourself and your good to go.
Sent from my SGH-I897 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Somebody PLEASE correct me if I'm wrong here...
I use BOTH 'dedup' & '.tar' formats to backup my phone. I'm a flashaholic and test EVERYTHING. I use the 'dedup' to back up before I test something new because it only backs up the new stuff I added without repacking EVERYTHING, so it's a bit faster and takes up less space. Once a week or so, I do a '.tar' backup so I can archive it to my PC and remove it from my SD card (to conserve space). I DO also have multiple SD cards, one of them is dedicated to 'test' ROMs. I do a '.tar' backup on that before I flash the 'test' ROM, that way I don't trash my 'good' SD card with all of my pics, music, contacts, etc.(in case something goes terribly awry).
So it seems to me that BOTH formats are very useful.
I may be taking extra steps but after losing ALL of my data, I thought it time to refine my backup habits. LOL
sucess
gmillz said:
Go to ROM manager, press the menu button, manual flash override, select your device, clockworkmod 3.x+
Sent from my SGH-I897 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
:good: thanks this worked a treat
When I try, it says that its been disconnected, if I use a file manager on the phone it won't let me delete anything off, any ideas on this?
Did you push any data by adb or mtp via recovery?
I copied data via recovery, I take it that's where my problem came from?
you used
adb push backup /data/media/0
Click to expand...
Click to collapse
right?
lowsnamebrand said:
I copied data via recovery, I take it that's where my problem came from?
Click to expand...
Click to collapse
TO your device?
If so, yes that is where the problem came from. If you PUSH data TO your device via recovery (not single files but folders) It screws permissions. There is a zip to fix it which I can link to, if you can confirm that is what you did.
rootSU said:
TO your device?
If so, yes that is where the problem came from. If you PUSH data TO your device via recovery (not single files but folders) It screws permissions. There is a zip to fix it which I can link to, if you can confirm that is what you did.
Click to expand...
Click to collapse
please share the link
kamilmirza said:
please share the link
Click to expand...
Click to collapse
In this thread:
http://forum.xda-developers.com/showthread.php?t=2239421
is a sdcard fix permissions script (flashable zip)
Of course if you can't write to sdcard, you'll either need to adb push / MTP via recovery or using a root explorer, set all permissions to read, write for /data/media/0/Download
That's exactly what I did sir, so I reflashed everything, now (of course) everything is running like a champion, appreciate the info,won't be making that mistake again
lowsnamebrand said:
That's exactly what I did sir, so I reflashed everything, now (of course) everything is running like a champion, appreciate the info,won't be making that mistake again
Click to expand...
Click to collapse
Yeah, MTP and ADB via recovery are fine if you need to get a backup on there to restore or some zips to flash, but as soon as you start pushing actual folders, permissions screw up.
Choice is to go through setup wizard and then use Android MTP or push that zip too and flash every time.
Thanks for the info, won't be making that mistake again Lol, side not lollipop is snappy and responsive as all hell
I am having trouble finding my nandroid backup file made with TWRP. I can't even find the TWRP directory! This file system is so confusing! I have tried ES File Explorer, Root Browser, and tried searching the file system using my laptop. I have even searched for "2014-12-13" and nothing is found. Can anyone please help? Nexus 5 on Android 5.0 w/ TWRP v2.8.1.0
I had probaby the same problem as you are facing. N5 with TWRP 2.8.1.0. After making nandroid I could not get the backup to show up within the TWRP folder (which is visible and accessible with ES File Explorer).
This issue was when I was using this specific Lollipop 5.0 rom (don't know if it is rom related or not) :
http://forum.xda-developers.com/showpost.php?p=57372774&postcount=1
Then I went looking for another Lollipop rom, specifically a 5.0.1 version and found this one :
http://forum.xda-developers.com/showpost.php?p=56734946&postcount=1
After flashing this rom and making nandroid the backup shows up normally within ES File Explorer. Not more issues.
Don't know if this helps, hopefully :fingers-crossed:
daffie said:
I had probaby the same problem as you are facing. N5 with TWRP 2.8.1.0. After making nandroid I could not get the backup to show up within the TWRP folder (which is visible and accessible with ES File Explorer).
This issue was when I was using this specific Lollipop 5.0 rom (don't know if it is rom related or not) :
http://forum.xda-developers.com/showpost.php?p=57372774&postcount=1
Then I went looking for another Lollipop rom, specifically a 5.0.1 version and found this one :
http://forum.xda-developers.com/showpost.php?p=56734946&postcount=1
After flashing this rom and making nandroid the backup shows up normally within ES File Explorer. Not more issues.
Don't know if this helps, hopefully :fingers-crossed:
Click to expand...
Click to collapse
I flashed factory image 5.0 Lollipop from Google's website. I don't think our issue is related. I can't even find a TWRP folder.
Nebul0us said:
I flashed factory image 5.0 Lollipop from Google's website. I don't think our issue is related. I can't even find a TWRP folder.
Click to expand...
Click to collapse
Ok I see.
Nebul0us said:
I flashed factory image 5.0 Lollipop from Google's website. I don't think our issue is related. I can't even find a TWRP folder.
Click to expand...
Click to collapse
Look in /data/media/0
Sent from my Nexus 9 using XDA Free mobile app
Nebul0us said:
I am having trouble finding my nandroid backup file made with TWRP. I can't even find the TWRP directory! This file system is so confusing! I have tried ES File Explorer, Root Browser, and tried searching the file system using my laptop. I have even searched for "2014-12-13" and nothing is found. Can anyone please help? Nexus 5 on Android 5.0 w/ TWRP v2.8.1.0
Click to expand...
Click to collapse
Terminal
su
restorecon -FR /data/media/0/*
jd1639 said:
Look in /data/media/0
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
/data folder is empty
Nebul0us said:
/data folder is empty
Click to expand...
Click to collapse
It isn't empty. You're just using a file explorer that isn't very good at reading things that need root permissions
rootSU said:
It isn't empty. You're just using a file explorer that isn't very good at reading things that need root permissions
Click to expand...
Click to collapse
I'm using ES File Explorer. But SuperSU doesn't show it having root access. How do I give it root access? It was my impression that ES was THE way to go for file explorer apps...is there a better one? Obviously opinion, but I'm open to suggestion...
Edit: Okay, using Root Browser I found the TWRP directory and the backup. However when connected to PC, windows explorer can't see it. How do I move the backup to my PC? This is ridiculously complicated to backup to PC...
Nebul0us said:
I'm using ES File Explorer. But SuperSU doesn't show it having root access. How do I give it root access? It was my impression that ES was THE way to go for file explorer apps...is there a better one? Obviously opinion, but I'm open to suggestion...
Edit: Okay, using Root Browser I found the TWRP directory and the backup. However when connected to PC, windows explorer can't see it. How do I move the backup to my PC? This is ridiculously complicated to backup to PC...
Click to expand...
Click to collapse
Install a terminal emulator and run the commands that @Aerowinder suggested. See my /sdcard problems thread in general for more information
rootSU said:
Install a terminal emulator and run the commands that @Aerowinder suggested. See my /sdcard problems thread in general for more information
Click to expand...
Click to collapse
I am trying to run those commands and getting "The selected command does not exist."
Nebul0us said:
I am trying to run those commands and getting "The selected command does not exist."
Click to expand...
Click to collapse
Screenshot?
Nebul0us said:
I'm using ES File Explorer. But SuperSU doesn't show it having root access. How do I give it root access? It was my impression that ES was THE way to go for file explorer apps...is there a better one? Obviously opinion, but I'm open to suggestion...
Click to expand...
Click to collapse
open the side menu and expand the tools menu, find root explorer and hit on
rootSU said:
Screenshot?
Click to expand...
Click to collapse
Nebul0us said:
Click to expand...
Click to collapse
I don't know that terminal. Try "terminal emulator"by jackpal
rootSU said:
I don't know that terminal. Try "terminal emulator"by jackpal
Click to expand...
Click to collapse
This is what I get when I try to install that terminal...which is why I went with that other one...
Nebul0us said:
This is what I get when I try to install that terminal...which is why I went with that other one...
Click to expand...
Click to collapse
That's a known issue on Lollipop. It happens when 2 apps require the same permission.
Have you got ROM toolbox installed? That app is known to conflict with jack pal
If not, you'll need to run a Logcat whilst installing to find out which app is conflicting
rootSU said:
That's a known issue on Lollipop. It happens when 2 apps require the same permission.
Have you got ROM toolbox installed? That app is known to conflict with jack pal
If not, you'll need to run a Logcat whilst installing to find out which app is conflicting
Click to expand...
Click to collapse
Okay, so I uninstalled ROM Toolbox and the terminal I had. Good call :good:
So now the question is, what did that command do? Hahaha...
/data/media/0 is supposed to be the mount point for /sdcard. Sometimes when flashing lollipop, this association breaks, making your /sdcard contents (and sometimes just some of it) disappear. The command restores that
rootSU said:
/data/media/0 is supposed to be the mount point for /sdcard. Sometimes when flashing lollipop, this association breaks, making your /sdcard contents (and sometimes just some of it) disappear. The command restores that
Click to expand...
Click to collapse
Okay but how does that benefit me? And how can I view my backup locations in windows explorer?
I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?
I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.
Boot cwm, adb shell, rm the file
beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.