I've been experimenting with a few different ROMs. First, I used UltimaRom, before moving onto Paranoid Android, and then CM10. Currently, I am using RootBox - Its been the best one so far (rivalling UltimaROM)
However, I've been left with lots of '0' directories in the file system. So, if I'm on root using ES File Explorer, I can click on '0' repeatedly to get sdcard/0/0/0.
Now, this 0 folder is taking a lot of space. Previously, the folder was 3.61GB in size(!). I've deleted it, now - reducing the size to 1.8GB.
However, the problem is that the UltimaROM ... ROM simply does not go away. The ROM is 1.8GB in size! So, its taking quite a bit of space. I've tried ES, Astro, and the delete option from 'Storage' in the settings yet, although they indicate they've deleted it, it doesn't actually go - and instead it just comes back again and again!
I'm sure I've full wiped in every instance. So, factory reset, cleared cache, cleared dalvik cache, and I even cleared system before moving between the ROMs.
I know two of the '0's were formed by bad installs of RootBox - one install failed, then, forgetting to format before retrying, the next one installed. To rectify this, I installed RootBox again - formatting this time before doing so.
How do I delete this thing permanently?! I really want to avoid wiping again, because it takes so long to get all my apps back. And, there's no guarantee wiping will even work! Although, if that is the only way, I will try it!
Sent from my Nexus 7 using xda app-developers app
Download a stock ROM, flash it in recovery, and that should get rid of the 0 folder. Just make sure the 0 folder doesn't contain any files or data that you might want to save.
Better yet, update your recovery to at least 6.0.27.
Sent from my GT-I9300 using xda app-developers app
Will updating my recovery really fix the issue?
Seems like an unusual method... But I'll try it!
Also, I'm trying to avoid reflashing, so in going to look for other solutions before i completely must flash to get rid of the 0 folder,
Sent from my Nexus 7 using xda app-developers app
Recovery has nothing to do with this, you miss understood him.
Stock Rom? Why? Would this realy overwrite the (perhaps r/o) folders?
I think it's the savest way to format your internal /data /system etc from recovery, and flash your ROM clean. Theretical you can move/ delete your existing folders, but this can be very confusing. Some folders/ mounts may be read only at the moment...
If you switching from 4.2 to 4.1 you are left with the 0 folder. Flashing a stock ROM will reformat your file system and get ride of the 0 folder. If you are switching between 4.2 ROMs you may get a 0/0/0/... folder. Updating recovery should revert the 0/0/0/... folder back to the 0 folder.
When I went from CM10.1 to 4.1 I was left with the 0 folder. Formatting the system in recovery didn't solve the problem and flashing a stock ROM did.
Best method use the search function as per Q12 FAQS .
Question has been asked and solved recently .
jje
Related
delete
I am experiencing the same issues. I assume you have this problem with ICS roms, because that's where I get those problems. I am currently running WEUI and half my apps are not at all working. I have also flashed back to stock, tried ICS Slim and MIUI v4, but no luck. I am also getting issues, while listening to music, where the song will keep on playing, but the app will ask me if I want to FC or wait. This has only happened recently. I really do not feel like going back to 2.2 or 2.3. Any help is greatly appreciated
Have you guys tried fixing the permissions?
That usually fixes most force close problems.
Xenoism said:
Have you guys tried fixing the permissions?
That usually fixes most force close problems.
Click to expand...
Click to collapse
Tried it, but no luck. Only option now is to flash a different ics rom, and see if that works. If all else fails I can always go back to bionix.
2 questions:
1 Can you see your internalSD with a file explorer?
2 Did you try wiping /cache and /dalvik-cache and rebooting?
I find a good wipe cure many things wrong (with my phone too )
Woodrube said:
2 questions:
1 Can you see your internalSD with a file explorer?
2 Did you try wiping /cache and /dalvik-cache and rebooting?
I find a good wipe cure many things wrong (with my phone too )
Click to expand...
Click to collapse
1. Yes
2. Yes, usually before I flash a different rom/reflash rom to try and fix this I wipe data and wipe cache patition and dalvik cache.
OK. The first question was to make sure you still had access to your internal and not sole sort of veiled encryption error.
Let me think about somethings and ill get back to you. I am wondering if it wouldn't be a bad idea to format /data and /system to make sure that you don't have any ghosts lurking. If you do, make sure you back up SDs contents to PC just in case.
Woodrube said:
OK. The first question was to make sure you still had access to your internal and not sole sort of veiled encryption error.
Let me think about somethings and ill get back to you. I am wondering if it wouldn't be a bad idea to format /data and /system to make sure that you don't have any ghosts lurking. If you do, make sure you back up SDs contents to PC just in case.
Click to expand...
Click to collapse
All those apps are still force closing on 2.2. Could it be, because I'm restoring them from titanium backup?
I'll try to backup SD onto my Computer and then format sd. It's probably some ghost file that is causing my phone to have errors. It probably is a file that has to do with MIUI since I flashed that as it happened.
Btw thanks for trying to help
Edit: I formatted sd card, put all the files back onto sd card, restored apps with tiatnium backup, but still no luck. I even factory reset,wiped cache and dalvik cache after formatting sd, but still no luck.
Thanks everyone for trying to help. I figued out the problem. Titanium backup was causing all those apps to have issues. I uninstalled all user apps via tb and download them from the market. I am getting no force close what so ever, with dl apps from market.
Usually when that happens from TB, it is from restoring system files (they show in red in the TB list of apps).
I use it to restore user apps + data every time I flash a new ROM, but I never use it to restore system apps, and I don't have any problems with it.
Since you've already restored from the market, you could try running TB and deleting it's backup data and then running a new batch backup of user apps (and no system apps) to have the freshest copy of your apps from a working system. That should allow you to restore in the future, hopefully without issue.
Sent from my SGH-T959 using xda premium
This could be a problem with using TB. TB gives you the option of restoring apps+data. If you're coming from a 2.2 rom to 4.0, you don't want to keep the data from a 2.2 rom. What you can do is restore apps without the data. That should solve your problem.
Hi, I hope someone can help me with this one.
My Prime has been rooted for months now, and I've flashed dozens of ROMS without any issues at all.
Suddenly, after flashing my most recent ROM (CyanogenMOD 9 RC2) I am unable to write to, or delete files and folders from internal storage/sdcard/
I have tried flashing a different ROM, fix permissions from within Clockwork Recovery, Factory Reset, deleting with Root Explorer (selecting Mount R/W) but nothing has yet worked. As a result my Prime is borderline useless.
I am able to create new folders and files within internal storage/sdcard/ and delete them. It is just the existing files that I am having the issues with.
Any advice would be greatly appreciated. Google hasn't been a great deal of help!
Same here and no solution to be found yet .
Sent from my Transformer Prime TF201 using xda premium
kennyn1980 said:
Hi, I hope someone can help me with this one.
My Prime has been rooted for months now, and I've flashed dozens of ROMS without any issues at all.
Suddenly, after flashing my most recent ROM (CyanogenMOD 9 RC2) I am unable to write to, or delete files and folders from internal storage/sdcard/
I have tried flashing a different ROM, fix permissions from within Clockwork Recovery, Factory Reset, deleting with Root Explorer (selecting Mount R/W) but nothing has yet worked. As a result my Prime is borderline useless.
I am able to create new folders and files within internal storage/sdcard/ and delete them. It is just the existing files that I am having the issues with.
Any advice would be greatly appreciated. Google hasn't been a great deal of help!
Click to expand...
Click to collapse
I'm trying a last resort thing . I have Andrawook P2.1 and i was thinking of wiping my data completely in the Aroma installation if it worked i'll hit you with a PM .
Make sure u have the rom u want installed and back up all files and apps
Power down, boot up by holding power and volume down.
When u see more tested display let go of both.
Wait till u see the three icons
Press volume down till u get to the first icon
It will wipe the data on your internal sd without touching ur rom
After reboot and restore!
Worked for me
Sent from my GT-I9300 using XDA Premium HD app
Hello everybody, new user here. I've been lurking for quite a while now, and decided to register since I need a question answered.
So anyway, to the question.
I want to install a custom ROM, LiquidSmooth to be exact, and I want to know, do I need to keep the previous system, the stock system, from Samsung, or can I delete it, and install my ROM? Problem is, I've got no external SD card, and I'm kind of OCD about spacing, I've noticed that when I installed it over the stock ROM, it worked perfectly, only thing that bothered me is that the system emulates a folder for all files, the folders called 0 in a normal file browser, and emulated in others.
Any help would be greatly appriciated.
-RCencelj
RCencelj said:
Hello everybody, new user here. I've been lurking for quite a while now, and decided to register since I need a question answered.
So anyway, to the question.
I want to install a custom ROM, LiquidSmooth to be exact, and I want to know, do I need to keep the previous system, the stock system, from Samsung, or can I delete it, and install my ROM? Problem is, I've got no external SD card, and I'm kind of OCD about spacing, I've noticed that when I installed it over the stock ROM, it worked perfectly, only thing that bothered me is that the system emulates a folder for all files, the folders called 0 in a normal file browser, and emulated in others.
Any help would be greatly appriciated.
-RCencelj
Click to expand...
Click to collapse
Custom rom
it worked perfectly, only thing that bothered me is that the system emulates a folder for all files, the folders called 0 in a normal file browser, and emulated in others.
Yes that is correct
You can delete previous system
jje
flashing a rom wipes system automatically
That's good and all, but how do I go about doing that? Since I don't own or have an external SD card, and I would preferably delete (wipe) everything with TWRP, problem is, if I do that, I delete the file that's on the phone, the .zip file that you use to install the actual ROM, so, where do I put the file so that it doesn't get deleted when I wipe everything off the phone?
*Edit*: Well, if it wipes the system automatically, how can I make it, so that the 0 or 'emulated' folder doesn't exist, and it just stores everything like the default ROM from Samsung? If that's possible.
RCencelj said:
That's good and all, but how do I go about doing that? Since I don't own or have an external SD card, and I would preferably delete (wipe) everything with TWRP, problem is, if I do that, I delete the file that's on the phone, the .zip file that you use to install the actual ROM, so, where do I put the file so that it doesn't get deleted when I wipe everything off the phone?
Click to expand...
Click to collapse
Flashing roms wipes system not whole internal SD card.
You won't loose all files in the internal SD card unless you choose to format internal CD card in the recovery (not needed to flash new rom).
Regards
RCencelj said:
*Edit*: Well, if it wipes the system automatically, how can I make it, so that the 0 or 'emulated' folder doesn't exist, and it just stores everything like the default ROM from Samsung? If that's possible.
Click to expand...
Click to collapse
Firstly it overwrites system rather than wiping so sometimes you can end up with residual files causing problems, hence most devs recommend you format system before flashing.
Secondly the 0 folder is the equivalent on 4.2 roms of the root folder on older roms. You can delete everything outside of the 0 folder, or so I believe but if you successfully delete the 0 folder it will be recreated on the next boot.
Sent from my GT-I9300 using Tapatalk 2
ghostofcain said:
Firstly it overwrites system rather than wiping so sometimes you can end up with residual files causing problems, hence most devs recommend you format system before flashing.
Secondly the 0 folder is the equivalent on 4.2 roms of the root folder on older roms. You can delete everything outside of the 0 folder, or so I believe but if you successfully delete the 0 folder it will be recreated on the next boot.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
So, just so I know I understood you, the 0 folder is the actual system for 4.2.x Android systems, and it can't be deleted/replaced?
If so, can I delete everything in the previous folder, except the 0 folder, like the DCIM, music, etc. folders, and I'm assuming those were used by the previous system, the default Samsung ROM.
Also, to be sure, if I just do a factory reset and install the LiquidSmooth ROM, it should delete the previous system and all files should work correctly on the new ROM?
RCencelj said:
So, just so I know I understood you, the 0 folder is the actual system for 4.2.x Android systems, and it can't be deleted/replaced?
If so, can I delete everything in the previous folder, except the 0 folder, like the DCIM, music, etc. folders, and I'm assuming those were used by the previous system, the default Samsung ROM.
Also, to be sure, if I just do a factory reset and install the LiquidSmooth ROM, it should delete the previous system and all files should work correctly on the new ROM?
Click to expand...
Click to collapse
if you revert back from 4.2.1 / 4.2.2 to 4.1.2 and below
make sure you download the megawipe from below link then flash any ROM you want
flash the megawipe zip file totally clear all your content in internal storage = just like format windows
http://forum.xda-developers.com/showthread.php?t=1832326
Thanks everyone, I got it sorted out now.
[Q] Very Weird "Symptoms" Internal+External Storage deleted files instantly reappear
orbital_71 said:
It call magic
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
For real though what's going on. Whether I use ES file explorer or root explorer, Even TWRP's built in file manager. The first two mentioned will delete the file and say "File Successfully Deleted" and the Storage for Internal/External (which ever it's located in) Reflects the correct change as if it was actually deleted. Yet once you back out of the folder the storage changes right back and I go back in the folder and the file is back...
Another example is moving files,
Just a few minutes ago I downloaded the Latest BeanStalk. I proceeded to move it to my External SD Card. And I deleted several files as well(Several Movies and a Nandroid), I then reboot to TWRP. I get ready to do a backup and notice that the damn storage sizes are back to the same sizes they were before I downloaded the ROM and deleted files. And the ROM is gone, not on Internal where it was downloaded to and moved from. Nor in the External Storage in the folder I moved it to.
Doesn't matter if I delete 17kb or 25GB the storage goes right back to what it was. And what ever files are there no matter if I delete/move/alter. It all goes back to identically the same...
Another odd thing, I made a Nandroid to my internal SD and once I booted back into the system it was gone. Even though it said backup successful. And before rebooting I checked the restore tab and the backup was there
What in the hell could cause that?
Tw1sted247 said:
For real though what's going on. Whether I use ES file explorer or root explorer, Even TWRP's built in file manager. The first two mentioned will delete the file and say "File Successfully Deleted" and the Storage for Internal/External (which ever it's located in) Reflects the correct change as if it was actually deleted. Yet once you back out of the folder the storage changes right back and I go back in the folder and the file is back...
Another example is moving files,
Just a few minutes ago I downloaded the Latest BeanStalk. I proceeded to move it to my External SD Card. And I deleted several files as well(Several Movies and a Nandroid), I then reboot to TWRP. I get ready to do a backup and notice that the damn storage sizes are back to the same sizes they were before I downloaded the ROM and deleted files. And the ROM is gone, not on Internal where it was downloaded to and moved from. Nor in the External Storage in the folder I moved it to.
Doesn't matter if I delete 17kb or 25GB the storage goes right back to what it was. And what ever files are there no matter if I delete/move/alter. It all goes back to identically the same...
Another odd thing, I made a Nandroid to my internal SD and once I booted back into the system it was gone. Even though it said backup successful. And before rebooting I checked the restore tab and the backup was there
What in the hell could cause that?
Click to expand...
Click to collapse
Make sure u are on freezas latest kernel. And twrp linked in my op. Issues with sd otherwise...
Sent from my Samsung Galaxy Note 3 using JellyBombed Tapatalk.
JoshBeach said:
Make sure u are on freezas latest kernel. And twrp linked in my op. Issues with sd otherwise...
Sent from my Samsung Galaxy Note 3 using JellyBombed Tapatalk.
Click to expand...
Click to collapse
It's internal and external though.. And on multiple ROM's
Tw1sted247 said:
It's internal and external though.. And on multiple ROM's
Click to expand...
Click to collapse
Did you update ES File Manager? One of the updates turned on the recycle bin by default, so a bunch of stuff, and space, started appearing (stuff I'd deleted) and depleting (space) until I deselected that option from settings.
Worth a shot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Unfortunately I checked and that option is not enabled on ES file explorer.
Tw1sted247 said:
Unfortunately I checked and that option is not enabled on ES file explorer.
Click to expand...
Click to collapse
Well that sucks.
Might be time for a full wipe and restoration of your rom of choice.
I'm unclear if killing the internal USB storage is a good idea, but at least the default wipe in recovery (system, data, dalvik) makes sense, though you may end up having to do everything.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Well that sucks.
Might be time for a full wipe and restoration of your rom of choice.
I'm unclear if killing the internal USB storage is a good idea, but at least the default wipe in recovery (system, data, dalvik) makes sense, though you may end up having to do everything.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Everytime that I switch ROM's( with the exception to when I am upgrading a build number from the same ROM) I always go to Advanced and check Cache, System, Dalvik Cache .... I then proceed to back up one menu and swipe the "Factory Reset" Wipe option built into TWRP.
I can't even make Nandroids at this point, they just Disappear after I Reboot. So I went side door on this pesky little bastard. And brought in my OTG and 64GB Thumb Drive. And these Nandroids are sticking. Although the current ROM I am running atm (BeanStalk) isn't recognizing OTG inputs. As it's built off of CyanogenMod, and this is one of the known bugs ATM.
Anywasy One of the Kind fellows on the International N3 forum notified me of a certain Build.prop edit that may tackle this issue. So off I go
**Fingers CRossed:good:
Tw1sted247 said:
Everytime that I switch ROM's( with the exception to when I am upgrading a build number from the same ROM) I always go to Advanced and check Cache, System, Dalvik Cache .... I then proceed to back up one menu and swipe the "Factory Reset" Wipe option built into TWRP.
I can't even make Nandroids at this point, they just Disappear after I Reboot. So I went side door on this pesky little bastard. And brought in my OTG and 64GB Thumb Drive. And these Nandroids are sticking. Although the current ROM I am running atm (BeanStalk) isn't recognizing OTG inputs. As it's built off of CyanogenMod, and this is one of the known bugs ATM.
Anywasy One of the Kind fellows on the International N3 forum notified me of a certain Build.prop edit that may tackle this issue. So off I go
**Fingers CRossed:good:
Click to expand...
Click to collapse
OK, this sounds bloody awful.
I am way unfamiliar with AOSP roms (I have clean rom on my Nexus 7 2013, however, so I get the simplicity of it), just isn't my cup of tea for this phone.
I am wondering if you switching between the 2 platforms hasn't caused some issues. I've wondered this before with other major issues, different from this but similar movement (AOSP to TouchWiz KitKat and back).
I'd like to see some definitive input on properly moving from one to the other.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I've found the culprit and its Permissions. Going to the AOSP ROM which was a KitKat ROM set the Permissions on my SD Card to read only. And I don't have the "authority" to change the permissions back.
I've tried editing the platform.xml to no avail. It's starting to get pretty damn frustrating. Even now when I go back to 4.3 ROM's following a clean wipe(dalvik, system, cache... Then factory reset) my permissions remain the same.
I have been having the same problem. I decided to order a new sd card and change my buildprop using ROM Toolbox Pro. I modiified "ro.securestorage.support" from "true" to "false". I will be receiving my new card either today or tommorow. I have had some bad luck with SanDisk and I am going to try lexar. I'm really considering reformatting back to the tried and true FAT32.
Tw1sted247 said:
Everytime that I switch ROM's( with the exception to when I am upgrading a build number from the same ROM) I always go to Advanced and check Cache, System, Dalvik Cache .... I then proceed to back up one menu and swipe the "Factory Reset" Wipe option built into TWRP.
I can't even make Nandroids at this point, they just Disappear after I Reboot. So I went side door on this pesky little bastard. And brought in my OTG and 64GB Thumb Drive. And these Nandroids are sticking. Although the current ROM I am running atm (BeanStalk) isn't recognizing OTG inputs. As it's built off of CyanogenMod, and this is one of the known bugs ATM.
Anywasy One of the Kind fellows on the International N3 forum notified me of a certain Build.prop edit that may tackle this issue. So off I go
**Fingers CRossed:good:
Click to expand...
Click to collapse
I was having similar issues for awhile, not sure if this is what fixed it or if it was something I did unintentionally but here's what I think may have worked: flashed my modem with MI3 once without auto reset on odin and then again with it then I changed my permissions on my external storage with root file explorer, i went into system/etc/permissions/platform.xml and added <group gid="media_rw" /> under the write_external_storage. I wasn't sure if that was the issue so for good measure I used triangle away and reset the flash counter, id been flashing a lot so I thought maybe that had something to do with it. idk. anyways, I haven't had the problem since. aside from APNs, still cant get custom apns to stick for some reason.
---------- Post added at 06:00 AM ---------- Previous post was at 05:54 AM ----------
Tw1sted247 said:
I've tried editing the platform.xml to no avail. It's starting to get pretty damn frustrating. Even now when I go back to 4.3 ROM's following a clean wipe(dalvik, system, cache... Then factory reset) my permissions remain the same.
Click to expand...
Click to collapse
what twrp are you running?
Hello there!
Alright, let me walk you through my problem.
(there's a summary at the bottom)
I own a rooted Asus zenfone go (Z00VD). In the past, I kept on waiting on boots cuz of the optimizing apps thingy that android does sometimes becomes of dalvik. After some research, a guy suggested to download the app(title), so I did and it worked. And it had a obvious warning that I did not follow which is "if you wish to uninstall this app, press unfix".
Alright so here comes the real problem, I decided to install a custom rom (resurrection remix), which made me wipe everything then it always ran into bootloader because it can't delete the dalvik cache (permissions error I think). So, in a great genius manner, I renamed the arm folder to parm(from arm) which allowed the Android rom to make a new dalvik cache.
So now in internal storage, I have a parm folder that is 2.5 gb big and is absolutely undeletable, even with recovery. The folder is owned by root, and it's group is 01028 sdcard_r. I cannot change it's permissions, or move it to external. I was able to move it to DCIM, but am unable to move it back to dalvik folder to u fix. So now, I can only change it's name to profane languages. I have tried using pc(through mounting) , but it still stays(the pc shows deleting it, the phone shows another story).
TL;DR: folder undeletable due to it being grouped in 01028-sdcard_r (I think). Cannot change its place nor its permissions even with recovery.
I'm sorry if I made this a bit too long, but I wanted to show you the story of how I ended up here. You can ask me any info about anything. Thank you for the help