Related
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Bro you need to use a file explorer from recovery. TWRP custom recovery has a built-in file explorer. That should do the trick
Sent from my SGH-T999 using Tapatalk
aussie88 said:
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Click to expand...
Click to collapse
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
fingolfin14 said:
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
Click to expand...
Click to collapse
Yep I figured that out the hard way lol. Already upgraded to the latest version of CWM to prevent it from happening anymore. Now to get the files out from down there... :banghead:
Sent from my SGH-T999 using xda app-developers app
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Perseus71 said:
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Click to expand...
Click to collapse
I saw that somewhere and tried that. Doesnt seem to be having any effect. Unless im doing it wrong...
I'm plugging my phone into my computer, accessing the phone section when it comes up, going about 20 0s deep and copying it back to the root. It either crashes my windows explorer, or doesnt seem to be doing anything(i think because its already disconnected itself. i tried making a new folder and it wouldn't let). what am i doing wrong?
PS. how would i access my phones internal SD from DOS?
thanks
Try ADB FileExplorer that should not time out on Windows. I have also tried Android File Manager with success. If that does not work, I will look up other options.
Well i tried android file manager. Im not 100% sure exactly how these programs work, but either way its saying i dont have root access. I do and i also have chainfires adbd insecure app which should give me full root access, but its still not working.
I looked at ADB FileExplorer too, but i didnt really get it and it kept saying it couldnt find my phone and something about an incorrect path.
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Perseus71 said:
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Click to expand...
Click to collapse
It never asked for root on my phone. I've tried all the changes and everything else that people have recommended, but im still not having any luck. I guess im too much of a noob for all this lol :crying:
Try Re-mounting internal SD in Recovery and then connect to PC.
nope, still no luck. Its still saying no root and no supersu request is coming up. I guess im missing something....
EDIT: I seem to somehow be "losing" root every time i try to connect to the android file manager. i open an app that requires root and it says i dont have root. I have to reboot my phone to get root to work again. It's weird though, because SuperSU opens fine...
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Lieu10ant said:
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Click to expand...
Click to collapse
If only it was that easy. its behind 400 nested folders. Windows cant go that deep. it freezes and FC's after about 200.
Im giving my phone in to get my power button repaired, so i guess ill ask the software tech there if he can figure it out. But thank you Perseus for all your help last night. :good:
I also have this problem guys, how do i update my custom recovery please?
Hi
Just got my TAB S 10.5 wifi. Painstakingly been trying to setup the pc so the tablet can talk to it. And installed ES File explorer so I can simply copy & paste my music to my SD card when ever I want.
But when I came to it, ES explorer will not let me do it, it says it needs to be rooted, which I don't want to do, I did on my S3 but that was purely to installed Viper for android.
2 questions:
Does anyone know if lollipop will sort out this permission problem when it's released.
and if not, is there a way to write to my SD card without rooting?
Many Thanks
At least make a proper effort at posting a subject line in the right sub forum and somebody might make an effort to reply...
Lollipop should fix sd issue i guess. I am running cm12 and have no problems. And theres no way to write to sd without rooting on kitkat or maybe i havent found a way
Dibbley247 said:
Hi
Just got my TAB S 10.5 wifi. Painstakingly been trying to setup the pc so the tablet can talk to it. And installed ES File explorer so I can simply copy & paste my music to my SD card when ever I want.
But when I came to it, ES explorer will not let me do it, it says it needs to be rooted, which I don't want to do, I did on my S3 but that was purely to installed Viper for android.
2 questions:
Does anyone know if lollipop will sort out this permission problem when it's released.
and if not, is there a way to write to my SD card without rooting?
Many Thanks
Click to expand...
Click to collapse
Did you try stock file explorer?
Dibbley247 said:
Hi
Just got my TAB S 10.5 wifi. Painstakingly been trying to setup the pc so the tablet can talk to it. And installed ES File explorer so I can simply copy & paste my music to my SD card when ever I want.
But when I came to it, ES explorer will not let me do it, it says it needs to be rooted, which I don't want to do, I did on my S3 but that was purely to installed Viper for android.
2 questions:
Does anyone know if lollipop will sort out this permission problem when it's released.
and if not, is there a way to write to my SD card without rooting?
Many Thanks
Click to expand...
Click to collapse
Kitkat introduced SD Card restrictions that meant apps could only read SD card data without being able to write to them or modify anything. Samsung somehow worked around this with their stock My Files app which allows writing to SD.
Lollipop should fix this by default and open up access to ES again
Sent from my Note 4
ashyx said:
At least make a proper effort at posting a subject line in the right sub forum and somebody might make an effort to reply...
Click to expand...
Click to collapse
did not realise the title went missing, my phone is a bit Laggy now and plays up.
Anyway, bit more digging, and I have come across an app called B1 File manager.
anyway, move this to the SD card, and you can write to it's own folder. Then I can assign my media player albums to the sub folder and works a charm!!!!!
And I never tried the stock file manager. I'm still learning what's on here, I've been stuck on jellybean for the past 2 years so there's probably lots on here to figure out.
Dibbley247 said:
did not realise the title went missing, my phone is a bit Laggy now and plays up.
Anyway, bit more digging, and I have come across an app called B1 File manager.
anyway, move this to the SD card, and you can write to it's own folder. Then I can assign my media player albums to the sub folder and works a charm!!!!!
And I never tried the stock file manager. I'm still learning what's on here, I've been stuck on jellybean for the past 2 years so there's probably lots on here to figure out.
Click to expand...
Click to collapse
How does this method work?
Sent from my Z667T using XDA Free mobile app
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
Hi,I have a note 10+ and I had 2 huge folders of music. I connect it with PC and deleted one of the folder, then I got the error that device not responding. I removed the cable, checked the first folder was gone, then I deleted the second folder using solid explorer. But my mobile is still showing the same storage as before. I tried looking with SD Maid and few other memory analyzing apps to see what is taking place. The app "disk usage" showing 95.6gb is taken by system data, but I cannot figure out which folder I should look for.. I also tried clearing system cache from recovery menu.. but nothing is working.
anyone have any suggestions other than resetting the device?
The device is not rooted btw.
thanks
Enable show root storage under settings/other in solid explorer and check if you can spot redundant music folders and if it then allows you to delete it.
I ran into the same issue. Since I updated to Android 10, the storage space was not available after deleting a file or a folder. The only work around was to reset the phone and activate the trashcan everywhere. Then each time you delete a file or a folder, you go to your trashcan and you empty it. Problem solved for me. I guess this is a bug within Android 10 as I have the same issue on both my Note 9 512Gb and my Note10+ 512Gb (both Exynos). Hope it helps!
I think that this issue is generated by the new way of the file management, I read here in XDA before android 10 release, that files generated by an app would only be accessible by that particular app, the author of the article was very worried about this, , because although this supposedly makes the device more secure, it generates other problems, as the one exposed here, I blocked updates because of this very reason, the convoluted new file management
Do you have file guardian from galaxy labs? That's where i found my deleted stuff which still took space. I got back almost 80gb after deleting all of it.
deejhay14 said:
Do you have file guardian from galaxy labs? That's where i found my deleted stuff which still took space. I got back almost 80gb after deleting all of it.
Click to expand...
Click to collapse
Indeed I use it. I found 3gb inside this folder. Mostly app updates! Thanks for your info
I downloaded file guardian from sammobile, installed but cannot find the icon to run it from. It shows up in system/apps/file guardian but of course it can’t be run from there. Where was your icon hiding?
Kind regards.
g0tch said:
I downloaded file guardian from sammobile, installed but cannot find the icon to run it from. It shows up in system/apps/file guardian but of course it can’t be run from there. Where was your icon hiding?
Kind regards.
Click to expand...
Click to collapse
File Guardian is part of Galaxy Labs. You will find the icon under Galaxy Labs app.
Powergeek2017 said:
File Guardian is part of Galaxy Labs. You will find the icon under Galaxy Labs app.
Click to expand...
Click to collapse
Many thanks, I didn't know that. Labs now installed and File Guardian is there. Thanks for your help!
Best Regards,
Hello forumers, please help me...
There is a problem with my Note 8 Pro phone. My files are in ghost form. I can't use them, open them, view them. I can't find some either. I didn't delete any of them. They suddenly disappeared. Some are in ghost form, I can see them but I can't use them I leave: "File doesn't exist or has been"
While playing with the Redmi Note 8 Pro brand M1906G7G phone, when I opened the gallery, the images in it started to twitch (flickering while being processed), all the images were gone in less than a minute. When I tried to check the files from the file manager, I noticed that all the files except system were not in place. So all my files suddenly disappeared before I knew what it was. Nothing happened to my contacts, sms, calendar information and externally installed applications (games, programs). The "second space" wasn't on when this was happening. When I looked at the size used from the storage it was 35.5gb, as if it was reset. The advanced settings of the phone are open, but the phone is not rooted.
I tried various file recovery programs, they couldn't find it. Except for the aforementioned files, only 3% of the files were found. So I think the files are lost, not deleted. There is a loss of at least 30gb. I'm in a predicament. Can anyone help with information on what happened to the files and how to get them back?