Database Info

Internal memory is FULL with NO APPS?! HELP

So i've been trying to research this problem for hours now. Ive jumped around a bunch of different roms since owning this gs3. MIUI 4.1 - Aokp 4.2.1 and currently synergy 4.1.2. I think since flashing aokp 4.2 that i get that "0" file when looking for files and such. I can tap "0" like 4-5 times to finally get into the files i want. I'm not sure if this is where my problem is coming from?
Let me say i don't have ANY backups. Im running clockwork and wiped,reset,cache all of that multiple times. I have ZERO apps installed and only a handful of pictures. My internal memory says its full and i get a warning at the top saying that my internal storage is to the max and that some programs might not respond. The bulk of GB used is in the "misc" folder. I've seen other people with this issue but it seems the only fix is to re-format the internal memory and LOSE EVERYTHING. I'm sure someone here can help :/

You delete all those roms you downloaded after flashing them?
Sent from my SCH-I535 using xda app-developers app

Install Disk Usage (if you have the space <grin>) and see what it says is taking up the space:

I feel as though it has something to do with the emulated "0" folders. I have literally 5 of them. I downloaded disk usage and it shows 5 different "0" folders.

Out of pure frustration, I went into the second "0" folder in file manager and deleted it. That in-turn must of deleted the other "0" folders? That free up 7 GB. My pictures and videos are still there but im wondering what else it deleted? It seemed like things would get stored in each of those "0" folders seperatly.

dincfool said:
I feel as though it has something to do with the emulated "0" folders. I have literally 5 of them. I downloaded disk usage and it shows 5 different "0" folders.
Click to expand...
Click to collapse
Ah, yes, the joys of 4.2. I've never flashed a 4.2 ROM, so take what I say with a grain of salt. It's my understanding that when you flash 4.2, it takes everything on the internal SD (/data/media/ folder) and puts it into that "0" folder (part of that whole separate user accounts "feature"). So, if you've installed, let's say five, 4.2 Roms, then that info will have been copied 5 times and put into nested "0" folders.
If it were me, I'd run a nandroid and put it on my external sd. I'd also run a TiBu (under preferences you can switch default location to external sd). Once you're sure you have those, I'd copy whatever data you want to save from the internal (DCIM folder, music, etc) and move it to computer or external sd.
Have a copy of synergy on the external and go into CWM and wipe the internal SD card (mounts -> wipe system, wipe data, wipe cache, wipe internal sd), then reinstall synergy, restore from TiBu and you should be golden.

^^
That sounds about right. Man this right here is enough for me to never want to go to 4.2 until I have too. Is the easiest way to transfer all my files to external SD through a computer? Where abouts in the phone do you transfer/or assign your files to an external SD?

dincfool said:
^^
That sounds about right. Man this right here is enough for me to never want to go to 4.2 until I have too. Is the easiest way to transfer all my files to external SD through a computer? Where abouts in the phone do you transfer/or assign your files to an external SD?
Click to expand...
Click to collapse
Have you installed Android SDK on your computer (ever used adb commands via command prompt)?
Edit: if you open up your phone in windows explorer, you should see 2 folders: Phone and Card (or something like that). You can drag the files from Phone to Card and they'll be on the external SD.

letinsh said:
Have you installed Android SDK on your computer (ever used adb commands via command prompt)?
Edit: if you open up your phone in windows explorer, you should see 2 folders: Phone and Card (or something like that). You can drag the files from Phone to Card and they'll be on the external SD.
Click to expand...
Click to collapse
Gotcha, i'll try that. I have a feeling once more people start running 4.2 they're going to run into this problem as well.

If you do have the SDK set up, a faster way to do it (if you're moving a butt-load of data) is to open a command prompt on the computer and navigate to where you want the data. For instance, I use C:\Backups. I'll then create a 2 folders within Backups (one for internal and one for external sd) and give them the date as a name. For instance, C:\Backups\Internal_2_5 and C:\Backups\External_2_5.
Then I'll be in C:\Backups and issue these commands:
Code:
adb pull /data/media/ Internal_2_5
adb pull /external_sd/ External_2_5
Depending on how much data you're moving, it could take awhile. Now, you could pick and choose what you want to pull:
Code:
adb pull /data/media/DCIM Internal_2_5/DCIM
would only pull that DCIM folder.
When I dump all of it, I'll wipe everything, install my rom, get it all up and going, then go through each of those backup folders and delete the stuff that's not "mine" (ie the Android folder(since your new rom built it's own folder), etc), then I'll push it back to the phone:
Code:
adb push Internal_2_5 /data/media/
adb push External_2_5 /external_sd/
Clean wipe, clean install, and all the data that I wanted back.
(fair warning, if your cards are full, that push pull commands could take several hours...)

[Q] Sure Glad I Bought A 32GB Nexus 5 Instead of 16GB

I am amazed at how little free space I have remaining on my 32GB N5. It shows 26.8GB total space, and I realize some is used for overhead.
Running stock rom and really not that many additional apps, and no pictures, movies, or music on the phone, I am at around 8GB free space remaining.
The phone’s storage tab reports:
Total Space: 26.08 GB
Available: 8.00 GB
Apps: 1.69 GB
Pictures & Videos: 1.19MB
Audio: 304KB
Downloads: 1.8MB
Cached Data: 44.09MB
Misc: 2.96GB
When I look in Misc, 2.43GB of the 2.96 is TWRP nandroid backups, 538MB is TI Backups, the rest is insignificant. Adding up all of what is shows as used totals about 3GB. Add the 8GB available, you have 11GB. So what happened to the other 15GB?
I have installed a utility to help me analyze space usage, and it shows the biggest space user is TWRP, with 2.4GB in backups. Those are important to have and I don’t begrudge the space, but man, this is supposed to be a 32GB phone.
One problem with disk space analyzers is that they tend to look for large files, but you can have 10,000 small files that will occupy more total space than a few large ones.
Those of you who are running relatively stock, how much free storage space do you have on your 32GB Nexus 5?

michaelnel said:
I am amazed at how little free space I have remaining on my 32GB N5. It shows 26.8GB total space, and I realize some is used for overhead.
Running stock rom and really not that many additional apps, and no pictures, movies, or music on the phone, I am at around 8GB free space remaining.
The phone’s storage tab reports:
Total Space: 26.08 GB
Available: 8.00 GB
Apps: 1.69 GB
Pictures & Videos: 1.19MB
Audio: 304KB
Downloads: 1.8MB
Cached Data: 44.09MB
Misc: 2.96GB
When I look in Misc, 2.43GB of the 2.96 is TWRP nandroid backups, 538MB is TI Backups, the rest is insignificant. Adding up all of what is shows as used totals about 3GB. Add the 8GB available, you have 11GB. So what happened to the other 15GB?
I have installed a utility to help me analyze space usage, and it shows the biggest space user is TWRP, with 2.4GB in backups. Those are important to have and I don’t begrudge the space, but man, this is supposed to be a 32GB phone.
One problem with disk space analyzers is that they tend to look for large files, but you can have 10,000 small files that will occupy more total space than a few large ones.
Those of you who are running relatively stock, how much free storage space do you have on your 32GB Nexus 5?
Click to expand...
Click to collapse
No problems with storage here. I'm on stock with custom kernel, 1 nandroid backup. I have about 16.5GBs left, where about 8GB is my music and the other 2-3 are my apps and the nandroid backups.

Here's mine... 32GB rooted running stock rom..

Thanks. I thought this was abnormal. Not sure how to go about finding that 15GB.

When I went to 4.4.2 I loaded 4.4 fresh and the side loaded 4.4.2.. Not saying you should do that.. But it will reset all the space on the phone
Sent from my Nexus 5 using xda app-developers app

Thanks for the help, folks. I whacked it all the way back to stock, and installed the factory 4.4.2 image, then unlocked, installed twrp and supersu, and I am back in business with tons of free space. I have all my apps installed and now it shows over 23GB available.
I still have no idea where that 15GB went, but I figured whacking it was easier than troubleshooting it.

michaelnel said:
Thanks for the help, folks. I whacked it all the way back to stock, and installed the factory 4.4.2 image, then unlocked, installed twrp and supersu, and I am back in business with tons of free space. I have all my apps installed and now it shows over 23GB available.
I still have no idea where that 15GB went, but I figured whacking it was easier than troubleshooting it.
Click to expand...
Click to collapse
The "missing space" in the mass storage window is all the stuff on the /mnt/shell/emulated/ folder, outside of the /0/ (sdcard) directory.
For example, Nandroid Backups are stored there normally (at least CWM stores them on /mnt/shell/emulated/clockworkmod/ so they don't get wiped with the data on /0/). If you got your backups inside the /0/ folder you're in danger...
Check with the "diskUsage" app, on the root section, "mnt/shell/emulated" and you'll see what do you have there using your space (/obb/ is a symlink to /0/Android/obb/ and isn't using any space there really),

RusherDude said:
The "missing space" in the mass storage window is all the stuff on the /mnt/shell/emulated/ folder, outside of the /0/ (sdcard) directory.
For example, Nandroid Backups are stored there normally (at least CWM stores them on /mnt/shell/emulated/clockworkmod/ so they don't get wiped with the data on /0/). If you got your backups inside the /0/ folder you're in danger...
Check with the "diskUsage" app, on the root section, "mnt/shell/emulated" and you'll see what do you have there using your space (/obb/ is a symlink to /0/Android/obb/ and isn't using any space there really),
Click to expand...
Click to collapse
Thanks much. That diskUsage app is very cool, much better than the one I paid for.

nandroid backup create a new file each time you back up, so if you back up alot, you will found that the back up size is huge, just delete some old dated back up and keep the lastest one is ok
Sent from my Nexus 5 using XDA Premium 4 mobile app

RusherDude said:
For example, Nandroid Backups are stored there normally (at least CWM stores them on /mnt/shell/emulated/clockworkmod/ so they don't get wiped with the data on /0/). If you got your backups inside the /0/ folder you're in danger...
Click to expand...
Click to collapse
Where as this is the common lost space issue, its not so they don't get wiped. Its just easier to leave them there than detect if you're on a /0 device and dynamically set it. Twrp and philz do though.
Custom recoveries don't wipe /0 anyway - they run rm -Rf with an exclusion on 0.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
Where as this is the common lost space issue, its not so they don't get wiped. Its just easier to leave them there than detect if you're on a /0 device and dynamically set it. Twrp and philz do though.
Custom recoveries don't wipe /0 anyway - they run rm -Rf with an exclusion on 0.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Are you saying that CWM and so started saving backups out of "/sdcard" (now /0/), and now when you wipe on them they wipe everything (including their backups that are outside of /0/) but /0/?
It has no sense. They'd have failed big time if so...

RusherDude said:
Are you saying that CWM and so started saving backups out of "/sdcard" (now /0/), and now when you wipe on them they wipe everything (including their backups that are outside of /0/) but /0/?
It has no sense. They'd have failed big time if so...
Click to expand...
Click to collapse
No.
I'm saying in the CWM source code for FUSE devices, /sdcard is mounted to /data/media - which was fine until android 4.2 which brought multi-user support. So even though other recoveries have moved with the times and updated their mount point to be /data/media/0, CWM simply didn't bother changing. It's not because they're "protecting from wipe" (in fact CWM doesn't wipe /sdcard anyway, only stock recovery does that), it's just they never updated it. That's why the backups are "outside" of /sdcard. No other reason.
Having backups outside of /sdcard has it's downfalls too. You cannot easily copy data from /sdcard to computer. Or copy a backup back to the device that can be restored.

rootSU said:
No.
I'm saying in the CWM source code for FUSE devices, /sdcard is mounted to /data/media - which was fine until android 4.2 which brought multi-user support. So even though other recoveries have moved with the times and updated their mount point to be /data/media/0, CWM simply didn't bother changing. It's not because they're "protecting from wipe" (in fact CWM doesn't wipe /sdcard anyway, only stock recovery does that), it's just they never updated it. That's why the backups are "outside" of /sdcard. No other reason.
Click to expand...
Click to collapse
Then okay, they didn't even bother to update, but as a result, the backups folder is outside the /0/ media mount point, and so, any application that wipes the real /sdcard mount point (/0) like the stock recovery as you say, won't wipe them.
Thanks for the explanation tho. I don't understand why they didn't even move a finger, but as a result the backups are more protected if you keep changing stuff and you like cleaning /sdcard (real /0 ) without touching the outside /mnt/shell/emulated folder (which contains vital data like said backups or the copy of the EFS folder usually).
rootSU said:
Having backups outside of /sdcard has it's downfalls too. You cannot easily copy data from /sdcard to computer. Or copy a backup back to the device that can be restored.
Click to expand...
Click to collapse
You can recover/push them easilly with adb tho.

RusherDude said:
Then okay, they didn't even bother to update, but as a result, the backups folder is outside the /0/ media mount point, and so, any application that wipes the real /sdcard mount point (/0) like the stock recovery as you say, won't wipe them.
Thanks for the explanation tho. I don't understand why they didn't even move a finger, but as a result the backups are more protected if you keep changing stuff and you like cleaning /sdcard (real /0 ) without touching the outside /mnt/shell/emulated folder (which contains vital data like said backups or the copy of the EFS folder usually).
You can recover/push them easilly with adb tho.
Click to expand...
Click to collapse
adb just isn't as convenient. But yes they are more protected but not by design. But also it has a problem in that your storage menu doesn't show true breakdown of space being used.

rootSU said:
adb just isn't as convenient. But yes they are more protected but not by design. But also it has a problem in that your storage menu doesn't show true breakdown of space being used.
Click to expand...
Click to collapse
Yeah.. but that drawback is minor. I would opt for a simple solution: Some root variation of the used space. Either:
a) A mod that makes the storage option to include all the stuff on /data/media/ including everything outside /0 .
b) Using another program that shows the real usage.
I don't really think that nandroid backups are "user data" per se, since this is as vital as the system itself for the user. Its logical to have it protected somehow :fingers-crossed:.

Its protected by the user not being an idiot. If they are an idiot, losing their backup is karma
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

[Q] Can someone explain to me the Android File System

So, I'm trying to understand how and why the file system acts the way it does.
Example. I have
/sdcard
and this has a bunch of stuff under it
then i have
/sdcard/0
this has some of the same stuff under it as /sdcard, but is a different file system
Why can I not just have a simple file system that I can understand! I seem to have issues with space because sometimes wiping the phone does not wipe the /sdcard/0 so I am working out of /sdcard/0 as opposed to the base of /sdcard
Any help? I am an idiot so explain like I'm 5, if possible.
Thanks in advance.

n0xide said:
So, I'm trying to understand how and why the file system acts the way it does.
Example. I have
/sdcard
and this has a bunch of stuff under it
then i have
/sdcard/0
this has some of the same stuff under it as /sdcard, but is a different file system
Why can I not just have a simple file system that I can understand! I seem to have issues with space because sometimes wiping the phone does not wipe the /sdcard/0 so I am working out of /sdcard/0 as opposed to the base of /sdcard
Any help? I am an idiot so explain like I'm 5, if possible.
Thanks in advance.
Click to expand...
Click to collapse
5 year old explanation.
4.3 and above Android systems implement a multi user file setup similar to what Windows and OSx uses. The 0 folder is your account, your significant other could be 1, your dog could be 2, this keeps going depending how many users are registered to the device. It's actual intent is to use multi user on a tablet interface, not a phone, but because jellybean is used on both phones and tablets the file structure is the same.
Normally you don't have to worry about much of this, but if you came from 4.1 jellybean then multiuser wasn't implemented yet. This would double up your data in both places.
To me it sounds like you're OK, it's going to show double files because it's essentially reading the exact same folder, the format isn't going to understand what you're trying to do because it doesn't really know where to look for your data files. Basically, leave your 0 folder alone because that's where your data is supposed to be stored.
Was that 5 year old enough?
Edit: if you format your internal SD card in your recovery, then you'll erase the doubled data, and your folder structure will be repopulated under the 0 folder system. If you're running out of internal storage that's what you should do. Then clean flash the rom of your choice following the format.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
5 year old explanation.
4.3 and above Android systems implement a multi user file setup similar to what Windows and OSx uses. The 0 folder is your account, your significant other could be 1, your dog could be 2, this keeps going depending how many users are registered to the device. It's actual intent is to use multi user on a tablet interface, not a phone, but because jellybean is used on both phones and tablets the file structure is the same.
Normally you don't have to worry about much of this, but if you came from 4.1 jellybean then multiuser wasn't implemented yet. This would double up your data in both places.
To me it sounds like you're OK, it's going to show double files because it's essentially reading the exact same folder, the format isn't going to understand what you're trying to do because it doesn't really know where to look for your data files. Basically, leave your 0 folder alone because that's where your data is supposed to be stored.
Was that 5 year old enough?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yeah! That's a pretty solid explanation! I couldn't seem to find anywhere that broke it down that way.
So let me ask one more 5 year old question.
I seem to have TONS of space used up on my SD card, that I cannot free up.
I have a 16Gig GSIII, when I attach my phone to windows, I have 7gb free of 12gb. I just wiped system, cache, and dalvik, and have a clean version of Beanstalk 4.4.2.
How am I using 5gb when the OS itself is only, ~199Mb.
Is there anyway to have a completely clean install? Even when I soft bricked, and then revived w/odin and an old kernal, I don't think it was totally clean.

n0xide said:
Yeah! That's a pretty solid explanation! I couldn't seem to find anywhere that broke it down that way.
So let me ask one more 5 year old question.
I seem to have TONS of space used up on my SD card, that I cannot free up.
I have a 16Gig GSIII, when I attach my phone to windows, I have 7gb free of 12gb. I just wiped system, cache, and dalvik, and have a clean version of Beanstalk 4.4.2.
How am I using 5gb when the OS itself is only, ~199Mb.
Is there anyway to have a completely clean install? Even when I soft bricked, and then revived w/odin and an old kernal, I don't think it was totally clean.
Click to expand...
Click to collapse
Yup! I just told you in my post edit, left that out by accident.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Yup! I just told you in my post edit, left that out by accident.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks again! Great answers, and just the info I need!
So, to format it in CWM. I would go to
Mounts and Storage
format /data
or
format /data and /data/media (/sdcard)
i assume I don't touch
format /cache or format /system
and.. last thing I promise, how do I make sure I keep a copy of gaaps and a rom on the sdcard, if I format it?

n0xide said:
Thanks again! Great answers, and just the info I need!
So, to format it in CWM. I would go to
Mounts and Storage
format /data
or
format /data and /data/media (/sdcard)
i assume I don't touch
format /cache or format /system
and.. last thing I promise, how do I make sure I keep a copy of gaaps and a rom on the sdcard, if I format it?
Click to expand...
Click to collapse
You can't keep anything on the SD card after formatting, it'll be completely wiped clean, but you should do the second option. Also you should always format system when you clean flash a rom anyway.
I'd use an external SD card to flash the rom from. Alternatively, you could sideload the rom (if you know how). I don't know how.
Sent from my SCH-I535 using Tapatalk 2

[GUIDE] Photo Recovery from Internal Memory

Hey guys, I've found a way to recover files from the INTERNAL Memory of the Samsung Galaxy S4.
A lot of people have said that it's not possible, but I'm here to prove them wrong.
You have to have rooted your phone before carrying out these steps. Don't post here asking for help rooting, there's plenty of other threads that can help you with that.
I hold zero liability in the event that you make a nice brick out of your phone. If you do not feel comfortable working with these commands, then please don't follow them.
You're going to need an SD Card that's at least the size of the internal memory on the phone. A smaller one would work, but keep in mind not all the files are going to be recovered.
If the SD Card is brand spanking new, you can skip step number 1.
Format the SDCard with a layer of 0's. This is done so that none of the old data will interfere with your recovery. This step is optional.
Root the Device
Install Terminal Emulator
Insert the SDCard
In Terminal Emulator run the command to gain super user privileges
Code:
su
Grant Terminal Emulator super user privileges
Run this command,
Code:
dd if=/dev/block/mmcblk0p29 of=/storage/extSdCard/raw.dd
Wait. Leave your phone plugged into an AC Adapter, and go grab a can of pop. This command will take a looong time. Couple hours to a day.
Once the command is finished running, shutdown your phone.
Remove the SDCard, and connect it to a computer
Download TestDisk
Open PhotoRec
Select the SDCard and press enter
Use the first option of "Unknown"
Then press "Other"
Select the Directory to backup the files to
Profit
'
How it works:
By dd'ing the internal memory to a file on the SDCard, you're doing a raw copy of the data.
Once the data is copied onto the SDCard, PhotoRec will scan the SDCard for deleted data, doing so will scan the raw file for photos. Not just photos, all files can be recovered using this method.
This method works on all rootable phones, provided you can figure out where the dev block for the internal memory is.
Hope you guys get your files recovered. I know I did

Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol

jamieridler said:
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
Click to expand...
Click to collapse
Any app you recommend in particular?

Bingley said:
Any app you recommend in particular?
Click to expand...
Click to collapse
Tbh I just downloaded the first app I came across that was free and had half decent reviews, can't remember what one, it was a little while ago, but there are loads of them in the store.

jamieridler said:
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
Click to expand...
Click to collapse
A lot of those apps are for the external SD Card, only support the FAT filesystem, and not as robust as PhotoRec from TestDisk.
Newer devices(Such as the S4) have an ext3 filesystem I believe, and a few paid apps claim to offer support for it.
... Not to mention TestDisk is Open Source :angel:

zzarzzur said:
A lot of those apps are for the external SD Card, only support the FAT filesystem, and not as robust as PhotoRec from TestDisk.
Newer devices(Such as the S4) have an ext3 filesystem I believe, and a few paid apps claim to offer support for it.
... Not to mention TestDisk is Open Source :angel:
Click to expand...
Click to collapse
Although some might well be limited to FAT filesystem, some are not, its up to the user to check before downloading and installing. After that rather simple search and install, I managed to recover every img file on my phone, current and deleted, and back it all up to external memory, all with a free app, which offers img file recovery for free and any other file type of your choice for a small, one off, cost, if you needed it. I recovered almost 1gb of img files in under 10 minutes.
Am I correct in assuming your method copies the entire contents of the internal memory, or a portion of it, to an SD card before starting the search for deleted files? I'm just an amateur with little knowledge trying to figure out how your method works. Sorry don't mean to bash your method of doing it either, just commenting on this as your post suggest no one has ever been able to do this before and your method is the one and only way it can be done.

But if the device is factory reset, will you be able to get files? If i sell my device i don't want anyone sneaking on my photos.

problems
zzarzzur said:
Hey guys, I've found a way to recover files from the INTERNAL Memory of the Samsung Galaxy S4.
A lot of people have said that it's not possible, but I'm here to prove them wrong.
You have to have rooted your phone before carrying out these steps. Don't post here asking for help rooting, there's plenty of other threads that can help you with that.
I hold zero liability in the event that you make a nice brick out of your phone. If you do not feel comfortable working with these commands, then please don't follow them.
You're going to need an SD Card that's at least the size of the internal memory on the phone. A smaller one would work, but keep in mind not all the files are going to be recovered.
If the SD Card is brand spanking new, you can skip step number 1.
Format the SDCard with a layer of 0's. This is done so that none of the old data will interfere with your recovery. This step is optional.
Root the Device
Install Terminal Emulator
Insert the SDCard
In Terminal Emulator run the command to gain super user privileges
Code:
su
Grant Terminal Emulator super user privileges
Run this command,
Code:
dd if=/dev/block/mmcblk0p29 of=/storage/extSdCard/raw.dd
Wait. Leave your phone plugged into an AC Adapter, and go grab a can of pop. This command will take a looong time. Couple hours to a day.
Once the command is finished running, shutdown your phone.
Remove the SDCard, and connect it to a computer
Download TestDisk
Open PhotoRec
Select the SDCard and press enter
Use the first option of "Unknown"
Then press "Other"
Select the Directory to backup the files to
Profit
'
How it works:
By dd'ing the internal memory to a file on the SDCard, you're doing a raw copy of the data.
Once the data is copied onto the SDCard, PhotoRec will scan the SDCard for deleted data, doing so will scan the raw file for photos. Not just photos, all files can be recovered using this method.
This method works on all rootable phones, provided you can figure out where the dev block for the internal memory is.
Hope you guys get your files recovered. I know I did
Click to expand...
Click to collapse
So i've followed your guidelines to a 'T' with a brand new 64g (huge, i know) Sd card, but the command line responds with, "writer error: file to large". Any advice as to how to proceed?
Really appreciate your efforts on this issue, btw!

[Q] [SOLVED] Impossible to free internal storage

I have an SD card of 64Gb and arround 20-25Gb of datas (including TWRP backup) but only 10Gb remain free. As you can see on the pictures, several Gb are missing. I have an idea of the cause, but no idea of the solution to free them.
I did a dual-boot on my tf700 to put lubuntu aside android. After using it a few months, I had some trouble and try to reinstall it ( I couldnt't syncronise zotero anymore because the version of firefox was to old and it was impossible to get a newer version without upgrading lubuntu and the upgrading of lubuntu was not working...) . As it was not working even after reinstalling lubuntu, I had to reinstall it a few times and I think that every times it occupied more space on my SD. As I'm not an expert, I decided to wipe and abandon my dual boot. I did a factory reset wipe (not including internal storage) and reinstall Cromi 5.4. I don't have the dual boot anymore, but it hasn't free the space....
The only idea I have left to free the space is to wipe also the internal storage... but as I don't think it will help (I may be wrong), I'm not very enclined to do it.
Have you any idea of how I can free this space?

Did the lubuntu installs create additional partitions?
Run ls -l /dev/block to see a list of yur partitions

berndblb said:
Did the lubuntu installs create additional partitions?
Click to expand...
Click to collapse
Unlikely, but who knows.
The other possible explanation would be that the lubuntu data is stored somewhere in /data where it is not detected by the storage settings page.

_that said:
Unlikely, but who knows.
The other possible explanation would be that the lubuntu data is stored somewhere in /data where it is not detected by the storage settings page.
Click to expand...
Click to collapse
Then a simple format of /data should bring it all back, right?

The command ls -l/dev/block indicate ls: Unkwown option '-/' . Aborting
But I installed Partition Table and it indicate that 81% (47Gb) of the memory is in /data (as in the screenshot attached)
I suppose that, as berndblb propose, I should format /data
What's the best ways to do it? With the option "format data" of TWRP ?

berndblb said:
Then a simple format of /data should bring it all back, right?
Click to expand...
Click to collapse
Yes, but this will erase *all* data. Erasing just the offending directory with a root-enabled file manager would be probably faster.
Tugende said:
The command ls -l/dev/block indicate ls: Unkwown option '-/' . Aborting
Click to expand...
Click to collapse
The space after "-l" was not just for decoration.
Tugende said:
What's the best ways to do it? With the option "format data" of TWRP ?
Click to expand...
Click to collapse
Yes. Remember that it takes a very long time (more than an hour) because it does a secure erase.

_that said:
Yes, but this will erase *all* data. Erasing just the offending directory with a root-enabled file manager would be probably faster.
The space after "-l" was not just for decoration.
Click to expand...
Click to collapse
YES! I found it. There was a folder data/media/linux with files taking space for each time I installed lubuntu. I erased it and everything is fine now!
(Sorry for the space after "-l". My eyes saw the previous one but not this one...)
Thanks very much for the help!