New user and first time rooting and flashing a new ROM. Actually the process appears to have gone well. I do have a keyboard issue which reflashing caused me to see another possible issue.
This is a GT-P7510 32 GB Wi-Fi only device. I had originally flashed to CM 10.1 which brought me up to Android 4.2.2. Also flashed gapps. After the initial ROM flash I had installed some Apps to begin playing with the new settings. But the keyboard issue became more annoying so decided to reflash and start over from scratch again.
After wiping, clearing cache and resetting the tablet I noticed some peculiarities in the directory structure of the memory. The top of the directory structure is a folder named 0 (zero). If I click on this one I get another almost identical directory structure also with another one named 0 as well. This one is almost identical to the root structure. I can then click on this next nested 0 directory structure to find even another directory structure. This last one however also has some files(downloaded data) remaining from a few of the programs that I had originally installed after the ROM upgrade.
I have tried to reflash, wipe, clear data, clear cache, clear dalvick cache and even resetting tablet but nothing seems to get rid of these nested folders. I have done this numerous times now. At first I thought this might have been my Google acct restoring these files but the last few times after wiping upon reboot I do not set up my Google acct or even connect to a Wi-Fi source for any files to be downloaded.
On a recent attempt soon after rebooting I connected my tablet to my computer via USB and observed the directory structure. After seeing the third nested directory structure beginning with a 0 I clicked on it and observed only two folders initially. However when I clicked on one of them I got an explorer error saying something to the affect it was in use and to try again. After several minutes I was then able to see the completely built third level nested directory structure that was busy rebuilding itself.
So my question is how does one truly and fully wipe the memory? If the ClockworkMod Recovery (v6.0.3.0) says I'm wiping data/factory reset is that not wiping all the files on the flash memory? Including wipe cache partition! What does a Factory data reset in the OS do? Where is this old data coming from? Why am I seeing almost three identical directory structure trees nested under each other?
I will admit to being a little weak on Linux file systems.
Related
As of yesterday, my CM7.1 phone won't boot - it gets stuck at the "rotating arrow" blue Android for ever. It's a Samsung Galaxy S II GT-9100.
I have been running CM 7.1.0 for several happy months now, and haven't tried to install or upgrade my ROM. The last action I took before this happened is that I made a full system backup (using CWM 5.0.2.6).
That backup is present on the internal memory. I can boot into recovery, mount drives and access devices using adb shell. So I do have an opportunity to fix what's broken, if I can work out what it is.
Given that the last thing I did was a backup, I checked to see if any of the partitions were full, but none are. (None is more than 42% full according to df; although strangely, df does not show any partition mounted on /.) I tried making another backup, watching carefully - that worked fine. I tried restoring the first backup - no improvement.
I've also tried wiping everything Recovery allows me to that's non data-destructive - cache, Dalvik cache etc. It hasn't helped.
How do I work out what's wrong? Is there a boot log file anywhere which might give me a clue as to what is wrong? I've searched for "*.log" but can't find anything obvious.
I don't want to do a factory wipe if I can avoid it, because obviously that will lose all my data. If I do a factory wipe and restore just the data partition, does that put me pretty much back where I was? If so, how do I restore just the data partition? The Restore option in CWM Recovery seems to do full backups only, and only from a particular directory.
The original CM and Google Apps zips are still on the internal SD (same versions as are currently not working). Would it be worth trying to reinstall those, without wiping? Or would that be data-destructive?
Any other ideas?
Thanks!
Gerv
SOLVED - remove 0-byte data/system/profiles.xml
I tried doing a full factory reset from Recovery. This got the phone booting again, but without any of my data . Fortunately, ClockWorkMod has a "partial backup restore" function. I restored the data partition... and the phone stopped booting again.
So this is progress. I now had some idea where the problem lay. I finally found it using a laborious 5-minutes-per-cycle manual bisection technique. Delete half the stuff on the data partition, reboot, if it still fails, delete more, reboot... once you get it to boot, restore the data partition, narrow it down further. Once you find a top-level directory, repeat the process inside it.
The result: the existence of a single 0-byte file stopped my phone from booting entirely. The file was: data/system/profiles.xml.
I have no idea what that file does (there are only a few references online), how a 0-byte version of it got created, or why having it existent but empty breaks things but if it's not present everything works fine. I have no idea if anyone else will ever see this problem, or if they will ever find this forum post. But still, here's my Wisdom of the Ancients (google the phrase for the relevant XKCD comic).
Is there a super wipe script for the Atrix? I want to delete all directories before flashing a new rom, so there are no directories from uninstalled apps, logs, etc.
When flashing a new rom I do the typical - wipe Dalvik, erase boot, system, userdata, cache, webtop, and preinstall...
the two super-wipe scripts I have tried were not compatible and exited before executing, and I'm having difficulty finding one.
thanks in advance.
sixftsix said:
Is there a super wipe script for the Atrix? I want to delete all directories before flashing a new rom, so there are no directories from uninstalled apps, logs, etc.
When flashing a new rom I do the typical - wipe Dalvik, erase boot, system, userdata, cache, webtop, and preinstall...
the two super-wipe scripts I have tried were not compatible and exited before executing, and I'm having difficulty finding one.
thanks in advance.
Click to expand...
Click to collapse
What you normally do is just fine. But if you want something automated, try this.
Edit:
Great, now you got Super Bass stuck in my head!
thanks for your response.
the script you linked to looks like it is an automated version of the wipe process I was already doing.
this is nice, but I was looking for something that deletes absolutely everything. the wipe process I was using does not delete some directories leftover from uninstalled apps.
sixftsix said:
thanks for your response.
the script you linked to looks like it is an automated version of the wipe process I was already doing.
this is nice, but I was looking for something that deletes absolutely everything. the wipe process I was using does not delete some directories leftover from uninstalled apps.
Click to expand...
Click to collapse
Wiping with fastboot left directories behind? That is surprising. Where were the directories that weren't deleted and how did you determine that?
upndwn4par said:
Wiping with fastboot left directories behind? That is surprising. Where were the directories that weren't deleted and how did you determine that?
Click to expand...
Click to collapse
they were on the internal sdcard... some were directories that were leftover from uninstalled apps that I don't use anymore or don't restore after flashing new roms, some were temp directories that I created for music/movies/whatever. some of them were regular dirs, some were dirs with a period before the dir name (ExampleDir or .ExampleDir)
another example to overexplain, even the "Music" folder still has all my music after the full fastboot wipe process. I thought a super-wipe script would completely format/erase everything so when I flash the new rom and reinstall apps, there is nothing remaining except for the new rom OS files and apps. (so my music folder would be an empty dir after fastboot wipe and flashing a new rom, adobe wouldn't have files and folders everywhere until i restore it with TiBU, etc)
sixftsix said:
they were on the internal sdcard... some were directories that were leftover from uninstalled apps that I don't use anymore or don't restore after flashing new roms, some were temp directories that I created for music/movies/whatever. some of them were regular dirs, some were dirs with a period before the dir name (ExampleDir or .ExampleDir)
another example to overexplain, even the "Music" folder still has all my music after the full fastboot wipe process. I thought a super-wipe script would completely format/erase everything so when I flash the new rom and reinstall apps, there is nothing remaining except for the new rom OS files and apps. (so my music folder would be an empty dir after fastboot wipe and flashing a new rom, adobe wouldn't have files and folders everywhere until i restore it with TiBU, etc)
Click to expand...
Click to collapse
I have never seen fastboot commands for wiping sdcards. You can either delete the folders manually with a file explorer (recommended), factory reset (not CWM, but from within a GB ROM), or format the sdcards.
Neither fastboot nor any automatic "full wipe" scripts touch any kind of user storage. That includes both internal EMMC and external SD storage. Those are left entirely for the user to maintain.
answered my question, thanks! :good:
upndwn4par said:
What you normally do is just fine. But if you want something automated, try this.
Edit:
Great, now you got Super Bass stuck in my head!
Click to expand...
Click to collapse
+1
Personally did this about an hour ago and worked like a charm.
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
Hi,
I'm new around, hope this is the right forum...
I have a galaxy s1 (i1900) which I flashed with a new ROM (2.3.6) in the past and then installed 4.2.2 from a zip, and it worked fine for a few months.
Having the same ROM file I used before, I tried to get it back to 2.3.6, as the 4.2.2 didn't work quite well, causing some problems when trying to make phone calls / receive calls.
After flashing the 2.3.6 again, the phone kept rebooting itself. Having read a few different guides online I tried all options - wipe data, wipe cache, wipe dalvik cache... then did some dramatic things like formatting /system, /cache /sdcard... I know it's not a very smart things to do when you don't know what you're doing, but I guess I felt I have nothing to lose at this point...
I also tried to reinstall 4.2.2 again and it only rebooted to the recovery mode whenever turning it on.
When mounting to USB I see no files in the device at all, only a folder called 'clockworkmod' with file called '.recovery_version' inside, and 2 empty folders named 'external_sd' and 'LOST.DIR'. It also shows it has 13.2GB free out of 13.2GB, which is weird, because the os doesn't occupy any of the capacity.
How do I save this poor device?
Many thanks in advance for your kind help!
Naama
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