OK it looks like I goofed and didn't backup the right messaging app in titanium...
However, before I decided to install a my new ROM I took a image backup in CWM and I'm guessing the messages got backed up too. I would reload the backed up image that CWM did but I'm getting this pesky MD5 mismatch nonsense.
So rather than faff with that, is there a way I can extract the messages / sms history from the image and restore it whilst in my new ROM environment?
Thanks...!
invertgoat said:
OK it looks like I goofed and didn't backup the right messaging app in titanium...
However, before I decided to install a my new ROM I took a image backup in CWM and I'm guessing the messages got backed up too. I would reload the backed up image that CWM did but I'm getting this pesky MD5 mismatch nonsense.
So rather than faff with that, is there a way I can extract the messages / sms history from the image and restore it whilst in my new ROM environment?
Thanks...!
Click to expand...
Click to collapse
you can use root explorer to extract the tar file for the /data backup. should be on your sdcard under the clockworkmod folder.
then you can use root explorer or an sqlite reader and navigate to /data/data in your extracted folder, and find the messaging app folder. then use the sqlite reader to read one of the .db files. sooner or later one of those .db files will have you messages in it. I dont think you can restore this(you can try to copy the .db and put it in the /data/data for your current messaging app) but you can at least read it.
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
if it extracts to an img you will have to
Code:
mkdir datafolder
busybox -o loop data.img datafolder
then navigate through that datafolder with the instructions above.
Related
Today I wanted to see what the JellyBean for SGS III is like so I made a nandroid backup of my current setup. After playing with JB for a while, I wanted to restore the backup, but I was greeted with an error message.
I've been messing with this the entire F****** day and so far I've isolated the file that is corrupted (it's /system/app/Keystring_factory.apk).
So I need to delete that file from within the archive. The problem is how do I do that? When I try to copy the file to my computer, it hangs on it and says "corrupted file" (tried windows explorer but also total commander). I am able to open the archive on my SGS III using something like ZArchiver, but it doesn't have the option to delete the file from within the archive.
Help?
Deusdies said:
Today I wanted to see what the JellyBean for SGS III is like so I made a nandroid backup of my current setup. After playing with JB for a while, I wanted to restore the backup, but I was greeted with an error message.
I've been messing with this the entire F****** day and so far I've isolated the file that is corrupted (it's /system/app/Keystring_factory.apk).
So I need to delete that file from within the archive. The problem is how do I do that? When I try to copy the file to my computer, it hangs on it and says "corrupted file" (tried windows explorer but also total commander). I am able to open the archive on my SGS III using something like ZArchiver, but it doesn't have the option to delete the file from within the archive.
Help?
Click to expand...
Click to collapse
U can extract cwm with titanium backup or use a file explorer to extract the backup and delete the file then zip it.
But I would flash a new Rom and extract cwm with TB and restore the parts u need with TB.then when all is good make a new backup.
I don't think it's a good idea to restore a corrupted file even if u find the errors
Btw. Fayaab has tweeted that he is going to release a JB for gs3 tomorrow and this should be working
Tried that too, Titanium got stuck at the file. 7-Zip got stuck even when "Testing Archive". I'll write the file off as corrupt. Interestingly enough, the data.ext4.tar is also corrupt. Does this mean it's a time for a new microSD card? Or is it CWM that's writing corrupt files somehow?
Access system files from recovery any use .
http://forum.xda-developers.com/showthread.php?t=1646108
Works on SGS3
jje
I've accidentally formatted my SD card in Recovery menu (I chose "format /sdcard" instead of "format /system") and now I'm recovering files from it via Recuva. I really really REALLY want to get back my SMS messages backed up with Titanium Backup, but I don't know what's the name of the file, and Recuva didn't keep folder structure of SD card, so there about 10,000 files in one folder and I don't know which one should I put in which folder to make Titanium Backup recognize it and restore. could anyone help me with it?
I guess I won't manage to recover SMS messages, but I've found files from my yesterday's CWM backup. so far I've got data.yaffs2.img, system.yaffs2.img, .android_secure.vfat.tar and _android.md5 that I suspect is md5 checksum of the backup. is there any way to use them again in recovery OR extract SMS messages from them?
I don't know about yours but in mine the three files are:
1. com.sonyericsson.conversations-20130222-110607.tar.gz
2. com.sonyericsson.conversations-20130222-110607.properties
3. com.sonyericsson.conversations-4dd5b9970089dead9ce60a0ff6fbf.0c6.apk.gz
So thus the three files in your phone will also be something starting with com.sonyericsson.conversations....search for them and then try to restore it Best of luck
Press THANKS if I helped,
Best Regards,
AJ
thanks, but I can't find them :/ but I found files from my yesterday's CWM backup. anyone could help me figure those out?
The files that CWM make are:
1) .android_secure.vfat.tar
2) .android_secure.vfat.tar.a
3) cache.yaffs2.img
4) data.yaffs2.img
5) nandroid.md5
6) system.yaffs2.img
If you find the files just store them in folder clockworkmod->backup->Then a folder with date and time when you made the recovery. It should be like YYYY-MM-DD.Hour(should be in 24-hour format).Minutes.Seconds(lol you might not remember it)
But i'm not sure if without this type of naming it will work or not. You could always give it a try
Press THANKS if I helped,
Best Regards,
AJ
---------- Post added at 05:04 PM ---------- Previous post was at 04:57 PM ----------
And if you want to get the data just use get the tool from here and use it to extract the data.yaffs2.img
Press THANKS if I helped,
Best Regards,
AJ
C:\karta\yaffs-mmssmsdb-calls-extractor>extract -s data.yaffs2.img
Failed to extract messages: file is encrypted or is not a database
DatabaseError('file is encrypted or is not a database',)
Warning: failed to remove temporary file c:\users\kuba\appdata\local\temp\tmpr85yj0
Click to expand...
Click to collapse
I guess I'll just have to live without those. thanks for the help anyway!
waitaminutewaitaminutewaitaminute!!! I found it! the file name of SMS backup is com.android.providers.telephony-rrrrmmdd-hhmmss.tar.gz, that's why I couldn't find it. but it's back! problem solved! free round for everyone!
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful!
I've tried, but didn't generate a new checksum?!?
Tedo said:
I've tried, but didn't generate a new checksum?!?
Click to expand...
Click to collapse
Are you sure u typed the commands correctly. The command surely creates a nandroid.md5 file in the nandroid backup folder with the checksum values.
parkourkarthik said:
Are you sure u typed the commands correctly. The command surely creates a nandroid.md5 file in the nandroid backup folder with the checksum values.
Click to expand...
Click to collapse
all good and well...why step one though? if you're just rm'ing it...seems a little unnecessary....? sorry i just performed step one then looked at step 2 and thought..wtf! lol unless theres something im clearly missing....?
sinner99 said:
all good and well...why step one though? if you're just rm'ing it...seems a little unnecessary....? sorry i just performed step one then looked at step 2 and thought..wtf! lol unless theres something im clearly missing....?
Click to expand...
Click to collapse
I am sorry did i miss saying that u can use any one of the fixes!! That means it's not a step by step it's either this or that, u can use whatever u wish that would be easy for u aong the two methods..
Sent from my GT-S6102 using XDA
Files not found
where to find these nandroid backup files
rjawan said:
where to find these nandroid backup files
Click to expand...
Click to collapse
Hi,
Look on your sd card/clockworkmod/backup.
Missing backup files
Have an AT&T Samsung Galaxy S4 (SGH-i337) Have made a couple of backups with CM and they show up in the Backup and Restore when in CM app. The path shows /mnt/shell/emulated/clockworkmod/backup but when I use ES File Explorer or Explorer they are not to be found. I can open /mnt/shell but the shell folder says 'Empty Folder'.
The reason I want to open the backups is to fix the MD5 checksum errors I always get when trying to restore.
It must be something simple but I can't figure it out.
parkourkarthik said:
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful!
Click to expand...
Click to collapse
ems_pilot said:
Have an AT&T Samsung Galaxy S4 (SGH-i337) Have made a couple of backups with CM and they show up in the Backup and Restore when in CM app. The path shows /mnt/shell/emulated/clockworkmod/backup but when I use ES File Explorer or Explorer they are not to be found. I can open /mnt/shell but the shell folder says 'Empty Folder'.
The reason I want to open the backups is to fix the MD5 checksum errors I always get when trying to restore.
It must be something simple but I can't figure it out.
Click to expand...
Click to collapse
Have you granted ES File Explorer Root permission ? Have you looked on both the Internal, and External SD ?
Have looked everywhere but don't know about granting ES File Explorer root permission....... Thanks for the quick reply.
prboy1969 said:
Have you granted ES File Explorer Root permission ? Have you looked on both the Internal, and External SD ?
Click to expand...
Click to collapse
---------- Post added at 11:02 PM ---------- Previous post was at 10:30 PM ----------
Granted Su to ES File Explorer, was able to see my nandroid.md5 files, edited and now restoring backup... Thank you very much for your expert help.
Now I have to figure out how to move my apps to my SD card. Thanks again!
ems_pilot said:
Granted Su to ES File Explorer, was able to see my nandroid.md5 files, edited and now restoring backup... Thank you very much for your expert help.
Now I have to figure out how to move my apps to my SD card. Thanks again!
Click to expand...
Click to collapse
You can move them with Titanium Backup.
TEAM MiK
MikROMs Since 3/13/11
cant access MD5
i installed CWM & made a rom backup, it said "Backup completed" & wiped data & &dalvik cache. now when tried to install custom rom, in recovery mode it doesnt opens ext sd card(where my custom rom is) & also when i try to restore backed up rom it says MD5 mismatch. As a result i am stucked up in recovery mode. now how to access that rom backup? my phone doesnt starts so i cant get it through ES explorer. also backup is in internal sd card so cant open it in computer also
parkourkarthik said:
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful!
Click to expand...
Click to collapse
atulbuddy said:
i installed CWM & made a rom backup, it said "Backup completed" & wiped data & &dalvik cache. now when tried to install custom rom, in recovery mode it doesnt opens ext sd card(where my custom rom is) & also when i try to restore backed up rom it says MD5 mismatch. As a result i am stucked up in recovery mode. now how to access that rom backup? my phone doesnt starts so i cant get it through ES explorer. also backup is in internal sd card so cant open it in computer also
Click to expand...
Click to collapse
You can find any other ways to Mount the SD card in recovery, with the help of adb shell or any other methods to access the backup file.
Else with the help of externel sdcard flash any stable ROMs and then try the restore thing.
Else try flashing the stock firmware available for your model.
Hit thanks rather than typing it
Thanks for the info!! Still working in android 4.4. Just saved me, thank you.
hi guys. i tried all your steps but no success. when i try with android emulator i get /system/bin/sh:cd/sdcard..... not found
and i try to edit the file and i install notepad but i get just some symbols inside the file so i have no ideea where the first line ends
I dont have PC or ADB. any other way to fix the problem?
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful![/QUOTE]
I dont have PC or ADB. any other way to fix the problem?
ok my esf folder is empty and now my s4 is stuck in factory mode. me being me they never got backed up and now i have no clue what to do. i have tried to unroot and go to stock with odin3 and no luck then rerooted. is there any way to fix this? would upgrading to ME7 fix this? i would rather not go to ME7 but if i have to i will. i just want my phone to get out of factory mode. :crying:
I could tell u also me7 wouldn't fix it...
hyperdrive powered s4
---------- Post added at 04:21 PM ---------- Previous post was at 04:19 PM ----------
Can someone please help him to repopulate his efs without a back up... I've seen it has been done i really can't tell him how do so
hyperdrive powered s4
---------- Post added at 04:31 PM ---------- Previous post was at 04:21 PM ----------
If I gave him an efs backup of mine and just filled in his imei number would this potentially work?
hyperdrive powered s4
---------- Post added at 04:48 PM ---------- Previous post was at 04:31 PM ----------
Okay scratch that idea, u need to Odin to stock and sent for repair to Samsung or get a warranty replacement sorry man...hopefully you can send Sammy a note saying not to take the upgrade while they have it for repair
hyperdrive powered s4
Do you not have a back up of your efs folder? Did you try copying the efs folder to your pc using dd if=/of= to see if anything is there? Did you enable the hidden menu and enter the code related to your efs?
Sent from my TouchPad using xda app-developers app
Surge1223 said:
Do you not have a back up of your efs folder? Did you try copying the efs folder to your pc using dd if=/of= to see if anything is there? Did you enable the hidden menu and enter the code related to your efs?
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
He didn't have a backup
hyperdrive powered s4
Basiclly if i run a TouchWiz rom my esf if missing and it puts my phone in factory mod, but if i have something like cyanogenmod it is fine. I have been running cyanogenmod since the begging of september. Than decide i wanted to try hyperdrive and and found out my esf folder is all messed up now
I have never backed up the efs folder before but after reading this thread I made a copy and saved it to my external sd card. I hope I never need it. Good luck to the OP!
So are u sayin if u put cm back it fixes your efs folder if so, your efs folder is being put in a different spot and the touchwiz rom cant find it
Sent From My Hyperdriven S4
ebsk8er06 said:
So are u sayin if u put cm back it fixes your efs folder if so, your efs folder is being put in a different spot and the touchwiz rom cant find it
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
ok if i flash a touch wiz ROM its gets stuck in factory mode because my phone esf folder is missing every all the files, but if i flash CM it is works fine. so either CM does not need those files or it moved them somewhere else. So im going to try a TW ROM and with root explorer to try and search for factory mode and see what comes up. worst thing that can happen is it does not work and i will re flash to stock and un root and take my phone to Verizon.
Stop. The first thing you should do is dd these to your sdcard/pc
efs -> /dev/block/mmcblk0p10
modemst1 -> /dev/block/mmcblk0p11
modemst2 -> /dev/block/mmcblk0p12
m9kefs1 -> /dev/block/mmcblk0p13
m9kefs2 -> /dev/block/mmcblk0p14
m9kefs3 -> /dev/block/mmcblk0p15
Sent from my TouchPad using xda app-developers app
If cm is working an u have service and data it has moved the files I've read a thread somewhere telling how to get it back to the right location but I can't seem to find it right now
hyperdrive powered s4
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and may the force be with you!
Leahcim
This was on sammobile.com I don't know if it will work on the s4 but maybe worth a try
hyperdrive powered s4
ebsk8er06 said:
If cm is working an u have service and data it has moved the files I've read a thread somewhere telling how to get it back to the right location but I can't seem to find it right now
hyperdrive powered s4
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and may the force be with you!
Leahcim
This was on sammobile.com I don't know if it will work on the s4 but maybe worth a try
hyperdrive powered s4
Click to expand...
Click to collapse
well the thing is the IMEI number is the correct one and i am connected and have service it's just that my phone is stuck in factorymode anyways i backed up the EFS folder and deleted it and it was regenerated but was still empty. if anything im going just unroot and take it to Verizon
Well just delete the factory mode apk
hyperdrive powered s4
ebsk8er06 said:
Well just delete the factory mode apk
hyperdrive powered s4
Click to expand...
Click to collapse
I know i could do that and i wanted to try to fix it but after all i have tried i give up lol. the only bad thing is there is no lock screen , but i will get over it
Very simply, how do I browse and extract the contents of a TWRP Nandroid backup on my Windows PC?
I am trying to browse a TWRP backup but I have a feeling I need to do a bit more fussing around. The backup is split into data.ext4.win000 through data.ext4.win007 and each of the parts has an accompanying .md5 with the same naming structure (ie. data.ext4.win000 and data.ext4.win000.md5.) There's also a data.info file as well.
The system backup is the exact same as described above for the data, except it's only 2 parts (system.ext4.win000 and system.ext4.win001, with the accompanying md5 files and the info file.)
Can someone provide a bit of guidance? I'm using a Windows 7 Home Premium machine.
kwest12 said:
Very simply, how do I browse and extract the contents of a TWRP Nandroid backup on my Windows PC?
I am trying to browse a TWRP backup but I have a feeling I need to do a bit more fussing around. The backup is split into data.ext4.win000 through data.ext4.win007 and each of the parts has an accompanying .md5 with the same naming structure (ie. data.ext4.win000 and data.ext4.win000.md5.) There's also a data.info file as well.
The system backup is the exact same as described above for the data, except it's only 2 parts (system.ext4.win000 and system.ext4.win001, with the accompanying md5 files and the info file.)
Can someone provide a bit of guidance? I'm using a Windows 7 Home Premium machine.
Click to expand...
Click to collapse
Simply rename the file to data.ext4.tar and use winrar to extract it.
I'm revamping this thread because I'm...desperate!
I have a nandroid backup (TWRP 2.8.7.0) and I would like to browse it on my PC. I'm focusing on files with structure data.ext4.win000x (where x goes from 0 to 2).
I'm able to open with 7-zip (should be equivalent to winrar) every individual file but size is faulty: every file is nearly 1.5 Gb while the content of the zipped file that I see it's around 50 kb. If I concatenate the files with the command copy /b data.ext4.win000? outputfile regardless the extension I give to "outputfile" I'm no longer able to open it with 7-zip.
Any suggestion/hint please ????
Not finding entire folders/files while browsing backup
I find the same thing regardless of the mechanism I am using to browse the backup. I am looking in /data/data for my own apps' data. Here is what I have tried so far:
1. Nandroid Manager app
2. TWRP Explorer app
3. ZArchive app
4. In a terminal, cat data.ext4.win??? | tar -tv > less (and then searching for my apps' package names
I was looking inside my nightly full backup to extract and recover some files I accidentally deleted. Cannot even find folders for the package names (except for 1 app). However, when I do a full restore from the same backup inside of TWRP Recovery, the missing files are indeed restored. So I know they are in the backup.
Why can I not find them and get at them any way else? I must be missing something simple.
Thanks
BTW - in the recovery.log file in the backup folder, I see the folders/files in question being "added". Very odd.
BTW2 - at least with regards Nandroid Manager app, I noticed that I was seeing some files I know I had removed from my apps some time ago. How could that be? I decided to clear data/cache for Nandroid manager and try again. It took much longer to process the backup for exploring. But now at least that app seems to be doing the right thing and I can see all folders/files.