Develop Bugs

[Q] Couldn't capture screenshot. Storage may be in use.

Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?

Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium

msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.

Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.

I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.

4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium

No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.

Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.

Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?

I fixed this deleting the "pictures" folder with RootExplorer.

jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!

bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .

My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.

On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!

Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.

Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0

/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk

Media inaccessible after 4.2 SDCard move

I can't view my pictures after upgrading to 4.2
Example attached.
I tried viewing them using different apps and even on PC. Nothing. I cleared media storage data and reflashed my ROM. Full wipe, ect.
Sent from my Galaxy Nexus using xda app-developers app

From what I know, on Android 4.2, system moves all the file in sdcard directory to sdcard0 directory. This means that all the apps that rely heavily on sdcard directory will not recognize the files now. I heard that you can simply just cut and paste all the file, but good luck with that. It'll take forever
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

kyokeun1234 said:
From what I know, on Android 4.2, system moves all the file in sdcard directory to sdcard0 directory. This means that all the apps that rely heavily on sdcard directory will not recognize the files now. I heard that you can simply just cut and paste all the file, but good luck with that. It'll take forever
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Click to expand...
Click to collapse
Already tried that. No go.

Can't view them or can't pull them to PC?

I read that CWM was creating a /0/ partition every time you flash, so if you flash several times you could end up looking like /0/0/0/0/0/sdcard/. Kouche is supposedly fixing the issue, maybe he already did. In addition to not finding your media, if you needed to restore a backup in a pinch you would be effed. Only passing on what I read.

Patience...
On the first boot after reflash, the media scanner needs to go through one full run-through, and then your media apps have to clue in. Give it another reboot or two and it'll be fine.
However it sounds like you impatiently diddled with it as many flashers do... so I have no idea what state it's in by now

I had the same problem on my nexus 7, just deleting everything on sdcard except for the 0 folder and copying everything in 0 to sdcard did the trick for the data itself, but I still have to start over with games while the files are there. Trying to figure that one out now.

I think my pictures are actually corrupted though. Its not finding a lot of my music either.
Sent from my Galaxy Nexus using xda app-developers app

[Q] From 4.2.1 back to 4.1.2.

Hey,
I went back to 4.1.2 (JellyBam) after using 4.2.1 (PA ROM). But there's a 0 folder inside my internal memory folder which leads to all my real files (music, pics etc etc).
So it's like.
-sdcard0
.....-0 (Folder)
..........-DCIM
..........-Downloads
..........-Music
..........-Titanium Backup
..........-etc etc etc
.....+'Music' which is empty
.....+'Downloads' which is empty
.....+etc etc etc
I searched on XDA, but the only solutions I found were:
1. copy every file to my computer, delete the 0 file (or not) and then put the copied files from my computer onto my phone. But there was no progress in the copying process as it was freezing.
2. Format everything, recovery, and some other things I didn't understand.
So I came here asking for help. Hopefully someone knows any other answer.
P.S. I know I can just chance the location of my backed-up files from TB, so there's no problem in that case.
But it is just annoying and sometimes it confuses me.
Thanks in advance :good:

I'm thinking of the same I'm not digging 4.2.1 that much.
Sent from my Galaxy Nexus using xda premium

I believe in 4.2 the /0 folder is the new location for the pseudo SD card instead of under /storage/

That's 4.2+ file structure to support multiuser and mentioned in dozens of threads. Just learn to live with it. Google knows what they're doing.

Meh well that's gonna be 4.2.1 for me...this is way too annoying with the files and folders

Rapydax said:
Meh well that's gonna be 4.2.1 for me...this is way too annoying with the files and folders
Click to expand...
Click to collapse
how is it annoying? you dont see really anything different other than going 1 more folder deeper.

Zepius said:
how is it annoying? you dont see really anything different other than going 1 more folder deeper.
Click to expand...
Click to collapse
Because change is bad obviously. Especially when it adds features.

Zepius said:
how is it annoying? you dont see really anything different other than going 1 more folder deeper.
Click to expand...
Click to collapse
I went back to CM10 (4.1.2) from CM10.1 (4.2.1) and just found it easiest to backup all my files and format the storage. Windows wasnt seeing the storage correctly until after I did that.

brooksyx said:
I went back to CM10 (4.1.2) from CM10.1 (4.2.1) and just found it easiest to backup all my files and format the storage. Windows wasnt seeing the storage correctly until after I did that.
Click to expand...
Click to collapse
How'd you do this? I'm curious to try the cm10.
Sent from my Galaxy Nexus using xda premium

What recovery are you using?
The issue is with resets and CWM recovery. The problem is your app back ups get covered under 0,0,0 and can't be restored, music apps can't see music, gallery can't see pics etc.
Switch to TWRP Open Recovery and the 0 problem goes away.
Best way to get your SD back in line is to use your PC to move everything back up where it should be. Hope this helps, freaked me out when I thought I lost my SD.
Sent from my Galaxy Nexus using Tapatalk 2

I think some of you aren't understanding the OP's question. He doesn't dislike the /0 file structure (or maybe he does, but I don't think that's the point he's making), he just doesn't want to keep it when downgrading to 4.1.2. That's perfectly understandable to me, and actually something I've been thinking about for a couple weeks.
OP- You have a few options. I think the simplest is to go ahead and flash a 4.1.2 ROM, then use a file explorer on the phone to cut from the /0 directory and paste straight into the main sdcard directory. Option 2 is to use a PC and cut and paste the same thing, but I don't know how quick it would be. Another possibility is to copy everything off your phone onto your PC, then format the storage on your phone, then copy everything from the PC back to /sdcard/. This is probably the cleanest and safest option, but also slowest. I'm sure there is also a way to do it with ADB, where you cut and paste from /0 to /sdcard/, but I'm no good with ADB so somebody else would have to give you the commands. ADB is most likely going to be the fastest method as far as file copy progress, but that's only a guess. I'm sure there are several other options I'm not aware of, but those are the ones I've thought of while thinking of doing this on my phone.
Good luck! Let me know which works for you and how it works........

I went back to a 4.1 ROM at one point and it did not immediately move everything back where it could be seen even with the latest recovery. I found that the easiest fix was to plug the phone into my computer right after the first boot and then move the data to the right folders with adb. Very quick and painless. TWRP does the fix going from 4.1 to 4.2 very nicely.

Downgrading to 4.1.2 from 4.2.1
I'm downgrading because I'm have a ton of blue tooth issues. I'm currently backing up my SD to my laptop then from win explorer I'll copy everything from /0 to the top SD directory. It's not any fun at all.
I wonder how many people will actually use the multiple users on their phone/tablet?
\m/
:cyclops:

Tablet - maybe
Phone - probably not
Sent from my Galaxy Nexus

[Q] SD card seemed to double, cannot erase portion of it

I have been having a bit of a problem with my Galaxy Nexus and its driving me nuts because of the storage situation..
Up until a couple weeks ago, I had the latest (at that time) version of AOKP on the phone (4.1.?, JB build 2 possibly). Then, around the first of the year, they updated to their 4.2 version JB-MR1 Build 1. The first time I installed the ROM, I installed it with the wrong GAPPS, ICS vs JB, and the phone went all haywire. I tried to get into the SD card to check which GAPPS was installed, but there were SO many force closes, I couldn't do anything. I rebooted into recovery, tried to go to my SD card, but ALL my info was gone. Basically a clean SD card.
So, I within minutes, I restored back to what I was on and everything was happy. No problems. I then downloaded the right GAPPS, installed the new ROM and GAPPS and everything worked great. Happy happy joy joy..
Today, I went to do a restore and remove some old backups and again, there is a second SD card. There is the normal one, and one labeled under /0/ in the directory.
I can access that directory while in recovery, but cannot with root explorer (or via my computers explorer) to erase it. The problem is, I think it is doubled up my photos and media, and now the card is full..
So, long story just to ask, how can I get rid of this other SD card directory? When talking with a co-worker, he mentioned it creates another directory when a second profile gets created..something I never did.
Any thoughts on how to get this removed so I can have my space back?

MikeDaub said:
I have been having a bit of a problem with my Galaxy Nexus and its driving me nuts because of the storage situation..
Up until a couple weeks ago, I had the latest (at that time) version of AOKP on the phone (4.1.?, JB build 2 possibly). Then, around the first of the year, they updated to their 4.2 version JB-MR1 Build 1. The first time I installed the ROM, I installed it with the wrong GAPPS, ICS vs JB, and the phone went all haywire. I tried to get into the SD card to check which GAPPS was installed, but there were SO many force closes, I couldn't do anything. I rebooted into recovery, tried to go to my SD card, but ALL my info was gone. Basically a clean SD card.
So, I within minutes, I restored back to what I was on and everything was happy. No problems. I then downloaded the right GAPPS, installed the new ROM and GAPPS and everything worked great. Happy happy joy joy..
Today, I went to do a restore and remove some old backups and again, there is a second SD card. There is the normal one, and one labeled under /0/ in the directory.
I can access that directory while in recovery, but cannot with root explorer (or via my computers explorer) to erase it. The problem is, I think it is doubled up my photos and media, and now the card is full..
So, long story just to ask, how can I get rid of this other SD card directory? When talking with a co-worker, he mentioned it creates another directory when a second profile gets created..something I never did.
Any thoughts on how to get this removed so I can have my space back?
Click to expand...
Click to collapse
Android 4.2 has a multiuser framework.
The "0" folder you are seeing is the first user.
Although it's only possible to create more users on tablets without tweaks
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

Lord Yurij said:
Android 4.2 has a multiuser framework.
The "0" folder you are seeing is the first user.
Although it's only possible to create more users on tablets without tweaks
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Am I crazy saying that it could be taking up a couple gbs of space on my card? It seems that since this started up, my SD is almost full.
Any idea how to merge, or remove that? I can only access the 0 folder while in recovery, and no other time.

They put in symlinks to the folder so you can access it from different directories. The information shouldn't be doubled unless you personally did it.

Reading this might help you understand:
http://forum.xda-developers.com/showthread.php?t=2107194

Lord Yurij said:
Android 4.2 has a multiuser framework.
The "0" folder you are seeing is the first user.
Although it's only possible to create more users on tablets without tweaks
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
eqjunkie829 said:
They put in symlinks to the folder so you can access it from different directories. The information shouldn't be doubled unless you personally did it.
Click to expand...
Click to collapse
Thanks for the everything and helping me understand...
I did not copy over anything to that directory, and in fact cannot even access it outside of Recovery. It just looked to me that things were copied over by the file structure, which is why I thought it duplicated things. It just seemed odd to me that when all this happened, my SD card seemed to get much fuller..
Thanks again..

MikeDaub said:
Thanks for the everything and helping me understand...
I did not copy over anything to that directory, and in fact cannot even access it outside of Recovery. It just looked to me that things were copied over by the file structure, which is why I thought it duplicated things. It just seemed odd to me that when all this happened, my SD card seemed to get much fuller..
Thanks again..
Click to expand...
Click to collapse
Late but useful info for "the next guy". When you install 4.2 its creates a multi-user environment, correct. And you do loose half your space (assuming it was full when you upgraded). Here's why. In 4.2 there is only /data/media which is where your internal SD card (sdcard) is symlinked to (ie: the actual location of your files). When you install 4.2, all of /data/media is copied to /data/media/0 for the first user, then /data/media/11 for the second user, then /data/media/12 for the third user and so forth. Each user gets their own /data/media directory which has all the files that the single user had in 4.1 For each user you add, say its only yourself, you just lost half your space because /data/media still exists but now so does /data/media/0 (a duplicate copy). So you sdcard's space is divided by the number of user accounts your system has installed in 4.2. Hope this clarifies things.

elfaure said:
Late but useful info for "the next guy". When you install 4.2 its creates a multi-user environment, correct. And you do loose half your space (assuming it was full when you upgraded). Here's why. In 4.2 there is only /data/media which is where your internal SD card (sdcard) is symlinked to (ie: the actual location of your files). When you install 4.2, all of /data/media is copied to /data/media/0 for the first user, then /data/media/11 for the second user, then /data/media/12 for the third user and so forth. Each user gets their own /data/media directory which has all the files that the single user had in 4.1 For each user you add, say its only yourself, you just lost half your space because /data/media still exists but now so does /data/media/0 (a duplicate copy). So you sdcard's space is divided by the number of user accounts your system has installed in 4.2. Hope this clarifies things.
Click to expand...
Click to collapse
Thanks. After a bunch of research, that is what is happening, and why my phone is always full of "stuff" now.
Now, if I could only access the /0 folders from my desktop...then I would be set..

MikeDaub said:
Thanks. After a bunch of research, that is what is happening, and why my phone is always full of "stuff" now.
Now, if I could only access the /0 folders from my desktop...then I would be set..
Click to expand...
Click to collapse
you do. its what you see when you plug your phone in.
if you have a old recovery and are flashing roms, it will create multiple /0 folders.

Zepius said:
you do. its what you see when you plug your phone in.
if you have a old recovery and are flashing roms, it will create multiple /0 folders.
Click to expand...
Click to collapse
If that is the case, I would like to access the standard folder, the copy, or original, or whatever the none /0 folder is..

MikeDaub said:
If that is the case, I would like to access the standard folder, the copy, or original, or whatever the none /0 folder is..
Click to expand...
Click to collapse
then you need root to explore /data/media/

Zepius said:
then you need root to explore /data/media/
Click to expand...
Click to collapse
Right. I would just find it handy to do via my desktop...

MikeDaub said:
If that is the case, I would like to access the standard folder, the copy, or original, or whatever the none /0 folder is..
Click to expand...
Click to collapse
"/data/media/" and "/storage/sdcard0/" or even just "/sdcard/" are the same thing. You dont have copies of files on your phone. If you delete it in one location, it deletes in the other because they are the same. You have the "0" folders on "storage/sdcard0" as well. If you do happen to have copies of files, you can organize it all on your computer if you plug in your phone.

MikeDaub said:
Thanks. After a bunch of research, that is what is happening, and why my phone is always full of "stuff" now.
Now, if I could only access the /0 folders from my desktop...then I would be set..
Click to expand...
Click to collapse
Please thank me by hitting the "thanks" button

[Q] Help me with media issue?

So i was on g2 apps v5.5 rom for some time when all of a sudden my media stopped scanning, i wasnt sure why, rescan media apps werent working either, so i decided to flash a new rom and i chose candykat, since then all of my files that i used to have, pictures, videos, etc have completely vanished. i cant locate the files in 7 zipper, es file explorer, and media scan apps still bring me nothing. Yet my internal storage still has the same amount of space used that it did before, and also when i go into CWM and choose install a zip it shows all the folders and things that i am missing, but that is the only place i see the folders but i dont have access to my files from cwm. Also i have noticed that when i am on 7zipper looking through files my internal storage says storage/emoulated/0 and i have no idea what the emulated is about, if anyone has any info or knows what im talking about please to help, Im not too great with phone stuff but i am okay, so if anyone has any simplified steps to give me on how to fix this issue it would be appriciated, thank you.

No answers anyone?

Just do some searching mate. And use ROOT EXPLORER and give it access.

nsh121193 said:
So i was on g2 apps v5.5 rom for some time when all of a sudden my media stopped scanning, i wasnt sure why, rescan media apps werent working either, so i decided to flash a new rom and i chose candykat, since then all of my files that i used to have, pictures, videos, etc have completely vanished. i cant locate the files in 7 zipper, es file explorer, and media scan apps still bring me nothing. Yet my internal storage still has the same amount of space used that it did before, and also when i go into CWM and choose install a zip it shows all the folders and things that i am missing, but that is the only place i see the folders but i dont have access to my files from cwm. Also i have noticed that when i am on 7zipper looking through files my internal storage says storage/emoulated/0 and i have no idea what the emulated is about, if anyone has any info or knows what im talking about please to help, Im not too great with phone stuff but i am okay, so if anyone has any simplified steps to give me on how to fix this issue it would be appriciated, thank you.
Click to expand...
Click to collapse
The way Kitkat makes the "SDcard"/"Internal Storage" directory is different from how it was on Jelly bean. <--EDIT: By this, I mean that the directory path is different.
The card is reading that X amount of data is on the card, yet you can't see it because your files are technically still there, but under the old directory path.
There are a couple of ways to fix this, but the EASIEST (IMO) way is to first restore a JB Nandroid backup (you can backup your KK ROM first if desired). First thing you'll notice is that the files will be there again. Now, plug your phone into your computer and copy all the files to it.
Reboot into recovery and format the internal SD. It's best to do it from within recovery, because otherwise, JB will just recreate the JB file structure and immediately start saving stuff to it. So when you get to KK, there will once again be the old structure hidden and with some files taking up space.
Now either reflash your KK rom or restore your KK backup.
Boot it up and copy your files back to the phone.
*I ran into this same issue after flashing KK for the first time. This is the exact process I did to resolve it.
Another way is to use a root file browser and locate the old directory and copy everything over to the new one. However, I think this might take quite a long time since the phone can do this only so fast.

spexwood said:
The way Kitkat makes the "SDcard"/"Internal Storage" directory is different from how it was on Jelly bean. <--EDIT: By this, I mean that the directory path is different.
The card is reading that X amount of data is on the card, yet you can't see it because your files are technically still there, but under the old directory path.
There are a couple of ways to fix this, but the EASIEST (IMO) way is to first restore a JB Nandroid backup (you can backup your KK ROM first if desired). First thing you'll notice is that the files will be there again. Now, plug your phone into your computer and copy all the files to it.
Reboot into recovery and format the internal SD. It's best to do it from within recovery, because otherwise, JB will just recreate the JB file structure and immediately start saving stuff to it. So when you get to KK, there will once again be the old structure hidden and with some files taking up space.
Now either reflash your KK rom or restore your KK backup.
Boot it up and copy your files back to the phone.
*I ran into this same issue after flashing KK for the first time. This is the exact process I did to resolve it.
Another way is to use a root file browser and locate the old directory and copy everything over to the new one. However, I think this might take quite a long time since the phone can do this only so fast.
Click to expand...
Click to collapse
Okay, thank you, I will try that soon and see if it works.