Database Users

Cannot see twrp back up files. Please help.

I recently switched over to team win recovery from cwm. I do like the ui and functionality way better then cwm. The problem I'm having is that I cannot access my back up files from my PC via USB. When I use the file browser that is built into twrp I can see the back up files in the twrp folder. When I plug my tablet into my PC via USB and open the twrp folder it is empty. Also when I open the twrp folder in es file browser it is empty there too. I would like to store the back up on my PC rather then on my tablet. Am I missing something? I was having this same problem with titanium with backed up apps so I upgraded to the paid version and uploaded my back ups to Google drive. After that I looked in the titanium back up folder again on my PC and all the sudden the files were there when before they were not. Its very frustrating. Please help.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.

Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.

mtrs said:
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Click to expand...
Click to collapse
Thank you for the tip. I went everywhere yesterday...
Best buy, radio shack, staples etc looking for an otg cable and had no luck. I'm going to order one online today. I will give the other techniques a try today though. I'm not familiar with pseudo terminal but I'm gonna dig in anyway. That's the best thing about these gadgets for me is hacking in and figuring out. Thanks again for your help!
mtrs said:
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
Click to expand...
Click to collapse
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

norcal61 said:
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Click to expand...
Click to collapse
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
Cool, that totally makes sense. Can't believe I didn't try that all ready. I will definitely make a new back up with the latest version of twrp. I'm running the same ROM and kernel as the back up that I currently have stored. Gonna give it a shot right now and let you know how it works.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.

norcal61 said:
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
Click to expand...
Click to collapse
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.

mtrs said:
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
Click to expand...
Click to collapse
It worked! I deleted the twrp folder all together and it worked like a charm. I'm now able to see and move the backups to my PC. Thank you very much for your help. It is greatly appreciated!
Sent from my Nexus 7 using Xparent Green Tapatalk 2

Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.

trungdtdev said:
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
Click to expand...
Click to collapse
I had the same issue and tried searching for "TWRP" to locate every instance of that folder. Turns out that I had previous backups in:
/mnt/shell/emulated/TWRP/BACKUPS/
I am happy to report that I was able to delete several past and hidden backups and recovered over 9gb of space!

[Q] Why can I not delete my /sdcard/clockworkmod folder?

So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.

Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7

BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..

I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.

erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?

I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app

Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.

cannot use backup restore mnt/shell/emulated

http://onlybestandroidapps.com/the-new-multi-user-management-in-android-4-2/
recovery is still looking for backups in mnt/sdcard. filesystem only recognizes mnt/shell/emulated. big issue!!!!!!!!

xkwwwx said:
http://onlybestandroidapps.com/the-new-multi-user-management-in-android-4-2/
recovery is still looking for backups in mnt/sdcard. filesystem only recognizes mnt/shell/emulated. big issue!!!!!!!!
Click to expand...
Click to collapse
Yes, please post this in every 4.2 thread.
They are moved on the drive, as are all files. Recovery's will have to update, it's not the end of the world.
If you need them RIGHT NOW, boot into recovery, adb shell into the device, and go to /data/media/0/TWRP to find your backups. You can copy them to /data/media/TWRP or whatever, that's the absolute path where TWRP is looking.
CWM will be similar, different filenames.

I have no idea what that blog said as it was written by either a robot, a 3rd grader or babelfish.. You decide.

[GUIDE] VM HTC Desire 816 Root How-to

Hello everyone, I recently purchased the Desire 816 for Virgin Mobile, and could not find anything on rooting this device.
So... I figured it out on my own! I decided to write out a tutorial since there isn't anything out there about rooting this phone!
I'm also including a nandroid backup of my stock rooted rom if you don't want to go through all of the steps. You will still need custom recovery.
1. Unlock your bootloader, install custom recovery, and flash superuser. I used v_superuser's guide for this, so thanks to him!
Use his guide to install custom recovery and root: http://forum.xda-developers.com/showthread.php?t=2775801
The custom recovery he links to isn't made for the VM variant of this phone, but it works!
Now you can restore my clean install, rooted nandroid backup (link at end of post) if you don't want to do the following steps and still have full root.
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/showthread.php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into your favorite root explorer and mount as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!

I just get md5 mismatch error when I try to restore
Never mind found out my phone wasn't downloading the whole back up

jcrt2000 said:
I just get md5 mismatch error when I try to restore
Click to expand...
Click to collapse
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.

sirrx7 said:
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
Click to expand...
Click to collapse
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.

Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
It does work. I had to download on my pc to get the whole file downloaded.

jcrt2000 said:
It does work. I had to download on my pc to get the whole file downloaded.
Click to expand...
Click to collapse
Oh nice! Glad you got it working.

Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906

sirrx7 said:
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
Click to expand...
Click to collapse
Thank you, I sold the phone but never noticed that.

Thanks for this, I had deleted my stock backup

problems with the mod.ko
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?

dwest3784 said:
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
Click to expand...
Click to collapse
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..

thanks
sirrx7 said:
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
Click to expand...
Click to collapse
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!

dwest3784 said:
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
Click to expand...
Click to collapse
Right on. Glad you got it working.

driver issue
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?

any help??
dragonclaw88 said:
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
Click to expand...
Click to collapse
i really really need to get this phone rooted any help??

dragonclaw88 said:
i really really need to get this phone rooted any help??
Click to expand...
Click to collapse
Have you plugged it in while in Fastboot? Which OS are you running? I'm on Win 7 x64 and have it set to download drivers from Windows update, I didn't have any problems going that route.

Have you downloaded HTC Sync Manager? It has the drivers required for your PC to recognize your phone.

Kontrary said:
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
Click to expand...
Click to collapse
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????

That Smith app is a problem for most recent HTC phones. It has nothing to do with the CWM backup. It happens with the M8 and our 816.
I just long press the notification, click App Info and force close. It's usually good until you reboot your phone.
Either HTC or Sprint is supposed to be looking for a fix but who knows.
https://community.sprint.com/baw/thread/169142?start=0&tstart=0

jayblaze406 said:
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
Click to expand...
Click to collapse
I was able to stop this annoyance by simply going to Titanium Backup (root needed) and freezing the process.
I typed in Smith in the search bar of TB and it came back with this process/app called
"Smith 4.21-plat_4.4.2-KOT49H"
I believe it happens to come up when a specific "bloatware" app is unaccessible by the device when removed but I have not singled out which app is it so far.
I backed up the app first then froze it and it stopped the Smith popup error permanently even after reboots and power offs.
(You could possibly delete it but until the stock bloatware app that causes this pinpointed i wouldn't recommend it.)
Tested running everything is good no errors rebooted fine checked bootloader and recovery and both are fine as well.
Sent from my 710C using XDA Free mobile app

[Q] how to recover data from a phone that will not boot

I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.

toggly said:
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
Click to expand...
Click to collapse
I would make a backup in your recovery and then flash the rom you had installed. See if that helps.
Edit: You didn't try to update. I changed my comment saying you had tried.

1. Download Aroma File Manager
2. Put a external sd into your phone.
3. Boot into the custom recovery and flash the Aroma file.
4. It will boot into a file browser and you can copy all the files from internal to your external.
ps it's possible that your custom recovery already has a filemanager build in. Then all these steps are obsolete.

I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?

toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.

toggly said:
Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Lennyz1988 said:
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
Click to expand...
Click to collapse
I don't know, that's why I am asking what that icon means?

You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?

toggly said:
I don't know, that's why I am asking what that icon means?
Click to expand...
Click to collapse
The icons means that it's symlinked. If it's not encrypted then you should find the data. It can be in an other place then where you are looking. Try looking in /data/media or some other maps in /data
Or just flash the rom you are currently on without wiping.
soldier9599 said:
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
Click to expand...
Click to collapse
Adb won't work unless he already has authorized adb when his device was booted.

toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager

Lennyz1988 said:
Adb won't work unless he already has authorized adb when his device was booted.
Click to expand...
Click to collapse
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.

peppe130 said:
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Click to expand...
Click to collapse
That did the trick, thanks!!

Nothing

soldier9599 said:
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
Click to expand...
Click to collapse
Yes and I believe that. But from version 4.2.2 android forces rsa encryption. So you need to boot into your rom and enable it. Unless the custom rom/kernel has disabled it, but I haven't seen any that have.