Please help me. I have many songs, movies and many imp files and documents in the internal storage and suddenly all is gone. Though it shows that it takes the space. Last night I connected my phone to the pc to copy a kernel modules into my phone. I copied and flash and the phone went into bootloop. Then I flashed the previous kernel I was using-ncx and it booted normally. Then I realized many files are missing but the phone is using the space for those. Then o rebooted and flashed the kernle again thinking that it was a kernel issue. After o rebooted I got everything. Then the whole night everything was normal. When I woke up I saw that the same thing happened aagin after a reboot. I rebooted because sound was my playing. It said unable to play media. It rebooted and sound played but the same files where again missing. The I flashed stock kernel. Still the same. Then downloaded viper Rom 3.3.6 and flashed it with and without full wipe and still the same. Please help anyone. I don't have a backup of these missing files and its very urgent.
What happends when you mount the sdcard as a mass storage device inside the recovery ? That way you go around the rom and see the space and hopefully the files directly ! Then at least we can say its a rom problem and not sdcard problem !
Mr Hofs said:
What happends when you mount the sdcard as a mass storage device inside the recovery ? That way you go around the rom and see the space and hopefully the files directly ! Then at least we can say its a rom problem and not sdcard problem !
Click to expand...
Click to collapse
I tried that but it shows the same files and folders that it shows inside the Rom.
When you have your phone mounted to your PC.
Control Panel -> Folder Options -> Select "Show hidden files/folders".
See what that does for you.
Did you try to flash a 4.2 rom? 4.2 rom's usually move your data from /sdcard/ to /sdcard/0/ or something, which might explain why you cant see the data when you flashed your previous rom.
When connected to pc and show hidden files. Nothing happens. I already had viper Rom since it released. After copying files from of pc it happened suddenly. I thought reflashing the Rom would solve but no. The titanium backup folder is also gone. The sd card does uses space so I think the files are recoverable. Please help me to recover them. Please.
I found something. The files are still there in the internal storage but not directly in the sd card. It automatically got moved in to a new folder>>> sdcard/0/
Everything is there. How to solve this issue? Make my phone recognize that folder as internal storage or just make it like before?
muid02 said:
I found something. The files are still there in the internal storage but not directly in the sd card. It automatically got moved in to a new folder>>> sdcard/0/
Everything is there. How to solve this issue? Make my phone recognize that folder as internal storage or just make it like before?
Click to expand...
Click to collapse
Lol that happened to me when I flashed my kernel unrepacked. just move everything back to /sdcard
Sdcard/0 is a file structure that happen when you flash 4.2 roms because of the multi user feature. When you flash other roms make sure you copy all files from sdcard/0 to the root folder before flashing
Sent from my HTC One X using xda app-developers app
I just came from the LG G2X that I had CWM and switch Roms almost weekly and never had the problem that I'm having now but I feel that CWM may be (at least) partially at fault (although there may be a problem somewhere between the keyboard and chair as well). The problem is now I only have 198MB left on the "Phone" that as of two days ago was just about 9.1GB. In those two days I have installed the OUDHS CWM , made a backup with CWM, installed SuperSU v1.25 , installed the Stock Deodexed/Zipaligned JDQ39.M919UVUAMDB 5/3 , made another backup with CWM and now I'm out of space. With CWM on my G2X I was use to it putting the backups on the external SD card. I take it with the OUDHS version it puts it on the phone somewhere. But I can't find out where. I've looked using ES File Explorer to search root and everywhere else but I can't seem to locate where all the backups are being cached. I'm also concerned that it may be that when roms get installed they don't just lay down on top of the the old rom's space. But I can't find anything in the forum that neither supports nor disproves that concern.
Thanks,
twitch
I found mine under /data/media/clockworkmod/backup ... check there
laparka said:
I found mine under /data/media/clockworkmod/backup ... check there
Click to expand...
Click to collapse
That's were they were. Thanks! Now if I can figure out how to get CWM to work off of the external SD card it will save me some cut and paste time.
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.
Hello everyone, I flashed stock rom (Sense7-Marshmallow-4.11.401.1) into my Desire EYE. Everything is okey, but while moving or copying a file into Internal Storage it says "xXx can not move here". I downloaded ES and FX File Explorer, tried every way. FX File Explorer says " Access was denied". Although I have full access on External Storage, I have no access in Internal Storage. Even photos or videos can't save internal storage.
Is there any suggestion ??? I flashed 3 times, but it doesn't work. I think the problem is 'permission' file. I know the problem, but I don't know the sollution
Thanks for everything
fcansun said:
Hello everyone, I flashed stock rom (Sense7-Marshmallow-4.11.401.1) into my Desire EYE. Everything is okey, but while moving or copying a file into Internal Storage it says "xXx can not move here". I downloaded ES and FX File Explorer, tried every way. FX File Explorer says " Access was denied". Although I have full access on External Storage, I have no access in Internal Storage. Even photos or videos can't save internal storage.
Is there any suggestion ??? I flashed 3 times, but it doesn't work. I think the problem is 'permission' file. I know the problem, but I don't know the sollution
Thanks for everything
Click to expand...
Click to collapse
having same issue after flashing similar or maybe the same rom u did ,,, also the device is lagging like badly frame per second lag unusable ,,, trying diffrent solutions to use the eye any way if this failes i will try flashing ubuntu on it just to see if it would fix it
-tried relocking bootloader and unlocking (deleting everything again starting all over)
-had a working cyanogenmod recovery mode - lost it while trying to change it with flashing a twrp 3.2.1 -0 for desire eye that i found here on xda
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar? Ans: Apparently yes, it is a "feature", aren't we lucky.
Am I missing some special setting? Ans: No.
Any thoughts on what the issue could be or if there is a fix? Ans: It can be fixed using root magisk.
Are your mount points similar/different? Ans: Guessing not and isn't related to the problem.
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)? Ans: Not the cause of the problem.
Thanks
meltwater.
i thought i was the only one with zero bytes files. and when you transfer them back- all good
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
dvijetrecine said:
i thought i was the only one with zero bytes files. and when you transfer them back- all good
Click to expand...
Click to collapse
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
SUPERUSER said:
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
Click to expand...
Click to collapse
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
meltwater said:
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
Click to expand...
Click to collapse
Magisk is the new "supersu" standard when it comes to root.
So it is the root per say. Yes you need root. But you root your phone by installing Magisk, its kind of a multi-tool.
You need to unlock your bootloader, if not already unlocked if you bought it that way like I did from Tradingshenzhen.
It will say Unlocked on the bootloader mi splash screen when you turn the phone on if the bootloader is unlocked.
And then you need to properly flash TWRP. Other than that you can stay on stock rom and use Magisk
Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ExSDCard Write Access Enabler module thread https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
I see something I did not see before.
In the thread OP mentions:
Since the v3.3 ZIP version, a feature has been added especially for Oreo (Android 8) users, on this Android version, several special permissions can be used by any app.
For exemple, theses specials permissions are used to get access to reading logs, managing the power of the device.
If you want to use this special feature, you just have to follow theses easy steps:
- creating a simple file named "ExSDCard_Oreo_apps" in the module path, so: /sbin/.core/img/ExSDCard/ExSDCard_Oreo_apps (remove any extension).
- Write all the apps package names that require a special permissions, one by line, for exemple:
Click to expand...
Click to collapse
So with this you can apparently create custom rules for apps that don't support selecting the external SD card path.
Maybe you should look in to that and experiment
This bug happened across android 8.0 in various brand.
Since I familiars with ES File Explorer, I solved by root the phone, convert ES File Explorer into System app via Titanium Backup, then everything work perfectly fine. No more 0 bytes copy file.
ES File Explorer still work even I un-root my phone by uninstall Magisk.
If you're really not want to root your phone or any other reason. Just copy file that you want then restart your phone. Copied file will now become usable file.
My bootloader isn't unlocked and for now I'd rather avoid rooting my phone (may well do so later).
Good to know there are work-arounds, and that my device hardware is ok.
Will have an experiment and see if I can live with it until I have a go at rooting. Even if I do the temp fix of ES explorer.
Thanks for the info and tips.
Same **** for me. 1 year to solve this stupid bug and they dont have fix this **** yet
Say thanks to xiaomi[emoji108][emoji867]
Enviado desde mi MI MAX 3 mediante Tapatalk
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Wmateria said:
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Click to expand...
Click to collapse
Yep, looks like it is a solid bug. For now, I'm living with it and use the space I have on internal memory to transfer data to before using a System file manager to transfer to SDcard.
Been trying some app development and now found the "Install via USB" bug.
Again can work around it, but it does spoil debugging with Android Studio.
There are certainly some odd bugs on this phone, I suspect down to Xiaomi going "off plan".
meltwater said:
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar?
Am I missing some special setting?
Any thoughts on what the issue could be or if there is a fix?
Are your mount points simlar/different?
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)?
Thanks
meltwater.
Click to expand...
Click to collapse
no need for this post. erased.
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
jorgeepelos said:
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
Click to expand...
Click to collapse
Get a Mi Mix 2S
Wmateria said:
Get a Mi Mix 2S
Click to expand...
Click to collapse
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk[/QUOTE.
It's people like you who make the community bad when you out your hatred in the forums or is not knowledgeable enough because main post talks about THIRD PARTY FILE MANAGER APPS not 1ST PARTY Xiaomi File Manger APP and thinks it's the end of the world on here and the Xiaomi forums. And trust me there is plenty of you people around pushing Devs and OP here by complaining when other people already stated the fact many times on a thread, and trust me, I hardly take offense. "Read", it works.
Click to expand...
Click to collapse