Moving file to root folder not working? - Asus Transformer TF700

I'm trying to move a file to my root folder from my dowloads and every time I try it goes really slow then freezes. What can I do to move the file?

charger04 said:
I'm trying to move a file ...
Click to expand...
Click to collapse
Is the file size over 4 GB?
Sometimes huge files being moved to the tablet will freeze and quit.

No it is only 700MB
And also I moved it from my downloads to my sdcard and it was fine

What is the space remaining on your internal memory?
Is it more than 3 GB?
Sounds like the Asus slow I\O bug raising it's ugly head...not sure about this however.
Are you on Jelly Bean?

Yes I have almost 20G left in my internal storage and I am on liquidsmooth JB rom
Sent from my Nexus 4 using xda app-developers app

I wonder if booting to recovery then restarting system would help.
Not sure about Liquid Smooth, I don't think that would cause the slow down.

charger04 said:
I'm trying to move a file to my root folder from my dowloads and every time I try it goes really slow then freezes. What can I do to move the file?
Click to expand...
Click to collapse
What do you mean with 'root folder' (for me, that is '/', and moving something there makes no sense), and how did you try to move the file, and from where?

Yes im trying to move it to '/' and I'm just moving it from my sdcard. I've tried using ES browser, root browser lite, and ROM toolbox's root browser and none work

charger04 said:
Yes im trying to move it to '/' and I'm just moving it from my sdcard. I've tried using ES browser, root browser lite, and ROM toolbox's root browser and none work
Click to expand...
Click to collapse
OK, you should know this:
- The root filesystem is a ramdisk. That means, after shutting down, its contents are lost.
- The root filesystem is usually read-only, which is a good idea.
- Every file in there occupies RAM. If you copy 700 MB there, you have almost no memory left to run programs.
- If you fill up the ramdisk too much, the device will simply reboot.
So, in a nutshell, I think you don't want to do this.

charger04 said:
I'm trying to move a file to my root folder from my dowloads and every time I try it goes really slow then freezes. What can I do to move the file?
Click to expand...
Click to collapse
as _that stated the theory, I think you probably missed read something, there is no reason you need to do this, I believe what you want is to move that 700mb file to /sdcard. Just curiousity, what is the 700mb file and why you need to copy it there?

I'm guessing you want the file on the root of your SD...

Related

Miscellaneous files?

I still havent seen an answer for this issue, but I have over 6GB of Miscellaneous Files in Setting->Storage. nothing in there shows that much info, so I know its from loading different ROMs. I have no idea how to get rid of these files. I've been looking all around CWM for something to clear, but I'm not too confident about messing with that.
Does anyone have an idea of how to clear up this stuff?
Do you have a few nandroid backups? Those will register there. If you're using TWRP, there's a TWRP folder and you can remove them or archive them off. Clockwork is the same, I just don't remember offhand where it stores them.
If this isn't it, you can install busybox, and then either adb shell, or use a terminal emulator on the phone and run `du /mnt/sdcard -hl -d 1` you can then drill down to the directories which are the biggest offenders. Changing the 1 to another number increases the depth that it reports.
Coop9 said:
Do you have a few nandroid backups? Those will register there. If you're using TWRP, there's a TWRP folder and you can remove them or archive them off. Clockwork is the same, I just don't remember offhand where it stores them.
If this isn't it, you can install busybox, and then either adb shell, or use a terminal emulator on the phone and run `du /mnt/sdcard -hl -d 1` you can then drill down to the directories which are the biggest offenders. Changing the 1 to another number increases the depth that it reports.
Click to expand...
Click to collapse
Okay. I finally managed to get this started. I went through terminal emulator and found that the /sdcard is only 7.6GB while the number in the main settings says over 10. /android has 2GB from some games, but I can't find anything showing where the 6GB of miscellaneous file is at. Even cwm is only 1.7GB from the one backup I have.
Sent from my SCH-I535 using xda app-developers app
I've been fiddling with this for the last day or so and found that under miscellaneous file, System Memory now shows up as taking 3.67 GB of data. I've been looking everywhere to see where that much info could be, but I'm kinda stuck now.
I now know where that extra space has gone, but I have no idea how to free it up.
Sent from my SCH-I535 using xda app-developers app
Galaxy S4 Miscellaneous Files: what and where are they?
So I'm getting a warning that the internal SD is out of memory, I've moved all movable apps to external SD, photos, music too.
Rooted and have TWIP as recovery *BUT* before I install a custom ROM, I want a backup *BUT* there's no room as the backup wants to use internal SD (not external)
Somehow Miscellaneous Files show over 8GB but in My Files it only shows about 200MB addressable (erasable). I deleted all Dropbox files and saved 200MB.
Where the heck are the other 7.8GB of files? How can I see them please?
Thanks in advance.
greenja said:
So I'm getting a warning that the internal SD is out of memory, I've moved all movable apps to external SD, photos, music too.
Rooted and have TWIP as recovery *BUT* before I install a custom ROM, I want a backup *BUT* there's no room as the backup wants to use internal SD (not external)
Somehow Miscellaneous Files show over 8GB but in My Files it only shows about 200MB addressable (erasable). I deleted all Dropbox files and saved 200MB.
Where the heck are the other 7.8GB of files? How can I see them please?
Thanks in advance.
Click to expand...
Click to collapse
I am in the same boat with no solution
I fixed it
jinan said:
I am in the same boat with no solution
Click to expand...
Click to collapse
backup *everything* and reformat *internal* SD card
http://forum.xda-developers.com/showthread.php?p=44217580#post44217580
hope it helps
greenja said:
backup *everything* and reformat *internal* SD card
http://forum.xda-developers.com/showthread.php?p=44217580#post44217580
hope it helps
Click to expand...
Click to collapse
I did this but didn't solve the problem for me. However, I did find a solution which worked for me. I used CWM, went in to the >Backup and Restore>Delete> and chose to delete all backups in the internal SD. Solved my problem
jinan said:
I did this but didn't solve the problem for me. However, I did find a solution which worked for me. I used CWM, went in to the >Backup and Restore>Delete> and chose to delete all backups in the internal SD. Solved my problem
Click to expand...
Click to collapse
WOW!!!!
i am so happy i found your tip. finally i managed to clean the mysterious 9Gb in my storage.
thank you very much!!!
Clean Data folder
DaemonAshra said:
I still havent seen an answer for this issue, but I have over 6GB of Miscellaneous Files in Setting->Storage. nothing in there shows that much info, so I know its from loading different ROMs. I have no idea how to get rid of these files. I've been looking all around CWM for something to clear, but I'm not too confident about messing with that.
Does anyone have an idea of how to clear up this stuff?
Click to expand...
Click to collapse
Yes its kinda simple, at least it worked for me. Don't forget to thank me
Download ES Explorer
and go into the /data/media folder.
the troublesome files are there. Careful what you delete tho. For myself I had old remnants from another ROM and the entire rom zip file.
Don't forget the thanx button.
A lot of that is cached data for apps. If you use apps like gmusic, it caches music files to the device and that cache folder will grow. Root access will allow you to clear all your data es, including hidden files and that size will drop.
Adjetey Boye said:
Yes its kinda simple, at least it worked for me.
Download ES Explorer
and go into the /data/media folder.
the troublesome files are there. Careful what you delete tho. For myself I had old remnants from another ROM and the entire rom zip file.
Don't forget the thanx button.
Click to expand...
Click to collapse
There's nothing in that folder.
So not that simple.
If you're rooted, get Cache Cleaner NG and let it wipe all that unnecessary data. I run it weekly.
With roms like gummy, you can click on Misc and see which app has all the data... It's likely something like Vine (it had a huuuuuuuge cache) or another app like gmusic.
beepea206 said:
If you're rooted, get Cache Cleaner NG and let it wipe all that unnecessary data. I run it weekly.
With roms like gummy, you can click on Misc and see which app has all the data... It's likely something like Vine (it had a huuuuuuuge cache) or another app like gmusic.
Click to expand...
Click to collapse
Sir (or madam).
I need you to fully understand exactly how amazing of a person you are. I don't know where the data was or what ate it all, but this app got it all back and you are awesome for recommending it.
Adjetey Boye said:
Yes its kinda simple, at least it worked for me.
Download ES Explorer
and go into the /data/media folder.
the troublesome files are there. Careful what you delete tho. For myself I had old remnants from another ROM and the entire rom zip file.
Don't forget the thanx button.
Click to expand...
Click to collapse
It worked for me, I have deleted the folder /data/media entirely。
Tks very much.
I recently ran into a similar issue with my rooted nook tablet. It was killing my sd cards. When I put the sd cards in my laptop, I erased all partitions and that fixed them.
I used to be a moderator in a forum that helped people with car trouble. I have accumulated some good karma. please help me
Eastsun said:
It worked for me, I have deleted the folder /data/media entirely。
Tks very much.
Click to expand...
Click to collapse
glad to be of help
Adjetey Boye said:
Yes its kinda simple, at least it worked for me. Don't forget to thank me
Download ES Explorer
and go into the /data/media folder.
the troublesome files are there. Careful what you delete tho. For myself I had old remnants from another ROM and the entire rom zip file.
Don't forget the thanx button.
Click to expand...
Click to collapse
Six and a half years later on XIAOMI redmi note 8T I habe finally found 6GB of data in orangenfox folder that I dont need ( for miui ota ). Thank you.

Problem rooting

I'm trying to root and I'm following the guide posted for the BLK3 firmware (I'm on stock OTA Jellybean); I have two problems and am hoping someone can help: the first is that I don't know which folder is my SD card. Is it the SCH-I535 folder that appears when I plug in my phone that says "phone storage" and has several folders like: "DCIM, Alarms, etc," or is it the folder titled: "CD: G" that has a couple of Verizon apps on it? Also, when I tried to drag the SuperSU file and the Bootloader file into the SCH folder it wouldn't allow that--there was a black circle that popped up over the folder. I have USB debugging checked, btw. Of course, I also have MTP checked. Could that be a problem? If so, how do I uncheck it? It won't allow me to.
If you cant transfer the file to your phone just browse to the post on ur phone and download via your phone. Im to lazy to plug my phone into my computer personally so I just use dropbox to transfer anything I want to my phone, or airdroid if its a bigger file.
If I download them will they save to internal or external? That's my problem
Sent from my SCH-I535 using xda app-developers app
Kelton Rivas said:
If I download them will they save to internal or external? That's my problem
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
idk, depends on where you save to, use the file explorer and find where you saved it.
x714x said:
idk, depends on where you save to, use the file explorer and find where you saved it.
Click to expand...
Click to collapse
I moved it to "Sdcard/0," is that external or internal?
Kelton Rivas said:
I moved it to "Sdcard/0," is that external or internal?
Click to expand...
Click to collapse
Internal.
prdog1 said:
Internal.
Click to expand...
Click to collapse
So how do I get it into external? I don't see SD card 1 with file explorer (I can only see 0). Don't you need Root to see the other areas of the phone with root explorer? Also, I'm trying to do the root process, but I get stuck at the "Flash custom recovery" step. I've done it three times now, but no matter how many times I flash it (Odin says recovery imagine nand write start, RQT_Closem RES_OK, etc," and once I go back into Odin mode I don't see the custom recovery. :l
http://imageshack.us/photo/my-images/35/26062374.png/
I tried going to mnt > extSdcard > move file and it wouldn't allow that. .it's effectively locked down. >.< Should I try something other than ES file explorer?
Turns out it didn't have an SD card in. So I just put the one from my Rezound in--we should be good now. O:
It says "custom binary download: 4 counts;" which I know is because I've attempted to flash my custom recovery four times--but every time I reboot after doing that it still gives me the Samsung recovery. What to do?

Cannot Resort Backups From d/l'd via ROM Manager After CM 10.1

So I was on CleanROM 5.6 and wanted to give 10.1 a shot. I made a backup and downloaded it to my computer via the ROMManager tool. I ran into 2 issues with 10.1 and decided I'd try again later, so I wanted to flash back to my CleanROM backup that I'd just made. Whether via ROMManager or going straight into recovery the process says it can't open the path to the file. I say the path, as this has occurred with the zip image on internal memory and when I've tried on the SD card.
Soooo, now I'm pretty stuck. Thoughts? I felt like it must have related to the new 4.2 file structure but again, this was an issue whether my zip was on internal memory or the card.
Thanks,
BH
The exact process is:
installing [path]
finding update package.
opending update package.
e: cant open [path] (bad)
installation aborted
CWM says it's leaving a log file but I am not seeing it.
Sounds like your filesystem is like this: "/sdcard/0" and if it is, then do the following:
use Root Explorer or a similar program and navigate to /sdcard/0/ press Menu should give you an option for Multi-Select, select all the folders/files in the /0/ directory, hit menu or down on the bottom choose Move (again depends on the browser) back up one level to the main /sdcard/ directory, and hit Paste. It will tell you there is files with the same information (because the ROM rebuilt the file structure) choose Merge, and let it do its thing. Depending on how many files you have, it may take a little while, just be patient.
Click to expand...
Click to collapse
taken verbatim from here:
http://rootzwiki.com/topic/37316-protip-42-and-recoveries/
I'm going to give it a shot now. I wouldn't have thought this would be an issue restoring since the zip was accessible and I even tried flashing from internal mem, but perhaps it's not as much as issue of reading the file as knowing where to extract the data? We'll see.
All in all, if I could just get 10.1 to stop giving me market errors (920) I'd probably just stick with that at the moment. Alas, have tried all of the interweb's solutions for that too.
Will update, thanks.
So I don't have a /0/ dir on the card, but I do have a /1/. Tried moving the contents of /1/ but it failed. May try another file explorer app (this was via CMs). Interestingly, I was able to flash a ClearnROM install zip, which is 4.1.1 based. Why would that work but the constructed backups wouldn't?
update: I can flash anything else regardless of location, and I am using the latest recovery. def seems like something specific to zip backups made/downloaded via the newest means in ROM Manager
monorailmedic said:
So I don't have a /0/ dir on the card, but I do have a /1/. Tried moving the contents of /1/ but it failed. May try another file explorer app (this was via CMs). Interestingly, I was able to flash a ClearnROM install zip, which is 4.1.1 based. Why would that work but the constructed backups wouldn't?
update: I can flash anything else regardless of location, and I am using the latest recovery. def seems like something specific to zip backups made/downloaded via the newest means in ROM Manager
Click to expand...
Click to collapse
Well if the rom zip is on /sdcard or /extsdcard then it will flash fine. If your backups are on /sdcard/1/ then that's literally the same as /0/. Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Well if the rom zip is on /sdcard or /extsdcard then it will flash fine. If your backups are on /sdcard/1/ then that's literally the same as /0/. Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have a similar problem with my file system after flashing from 4.2 back to 4.1 that has me confused.
I flashed to a TW rom after being on CM10.1, and I was using the most recent TWRP when I originally flashed CM10.1. I had the usual problem that everybody seems to have being that the "0" folder was located on my card. I copied the fold over to my normal sdcard folder (unfortunately I used root browser instead of root explorer, which made this much more painful as it does not have the "merge" ability. Root Explorer - accept no substitutes)
After doing the merge though, I have 2 problems.
#1 - My external SDcard is now listed under "storage."
#2 - There is an Sdcard there called "sdcard0 as well as a "extSdCard" in this storage folder with all the same information as the original "0" folder that was on the internal sdcard. Also a bunch of folders named UsbDriveA, UsbDriveB, etc.
Why did this happen? And how should I set up my folders so that it behaves properly? In other words, what does a normal file system look like?
SlimSnoopOS said:
...Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path...
Click to expand...
Click to collapse
So this is where I am confused, does the zip not contain all of the appropriate backup data within itself, and it is looking elsewhere (in the wrong path) for backup data? This seems odd based on the whole idea as well as the size of the file. If this is not the case, when why is whatever scripting is included in the backup looking for an absolute and not a relative path to the data? It should always be relative to the location of the zip file itself.
I really want to try and understand this.
PeterGunz said:
I have a similar problem with my file system after flashing from 4.2 back to 4.1 that has me confused.
I flashed to a TW rom after being on CM10.1, and I was using the most recent TWRP when I originally flashed CM10.1. I had the usual problem that everybody seems to have being that the "0" folder was located on my card. I copied the fold over to my normal sdcard folder (unfortunately I used root browser instead of root explorer, which made this much more painful as it does not have the "merge" ability. Root Explorer - accept no substitutes)
After doing the merge though, I have 2 problems.
#1 - My external SDcard is now listed under "storage."
#2 - There is an Sdcard there called "sdcard0 as well as a "extSdCard" in this storage folder with all the same information as the original "0" folder that was on the internal sdcard. Also a bunch of folders named UsbDriveA, UsbDriveB, etc.
Why did this happen? And how should I set up my folders so that it behaves properly? In other words, what does a normal file system look like?
Click to expand...
Click to collapse
See my attached photo for what your file system should look like. I'm using ES File Explorer and that's my file system.
What do you mean your external SDcard is listed under Settings/Storage? Both of mine are listed, internal storage is first then my external sd card is second. Care to screenshot what you mean?
monorailmedic said:
So this is where I am confused, does the zip not contain all of the appropriate backup data within itself, and it is looking elsewhere (in the wrong path) for backup data? This seems odd based on the whole idea as well as the size of the file. If this is not the case, when why is whatever scripting is included in the backup looking for an absolute and not a relative path to the data? It should always be relative to the location of the zip file itself.
I really want to try and understand this.
Click to expand...
Click to collapse
If you're using CWM, it saves your backups for internal sd card in: /sdcard/CWM/backup and blobs. For your external sd card, it's saved /extsdcard/CWM/backups and blobs. If you flashed any AOSP 4.2 rom, it moves EVERYTHING from your /sdcard/ path to /sdcard/0. See the difference? Example, your music should be in this path /sdcard/Music but instead it's been moved to /sdcard/0/Music on AOSP 4.2. I get what you're saying how it should be looking for where the zip is BUT the multi-user support completely disrupts our entire thinking of how our file system should be because one user could be "rooted" whereas the other user would be completely stock depending on who signed in. It's too early to expect this to just work since Google introduced this in 4.2. It's a take it or leave it thing.
Sent from my SCH-I535 using xda app-developers app
For a standard backup that makes total sense. My confusion is how this happens with a zip, when all of the backup data is confined to that one archive file (or at least should be).
monorailmedic said:
For a standard backup that makes total sense. My confusion is how this happens with a zip, when all of the backup data is confined to that one archive file (or at least should be).
Click to expand...
Click to collapse
When you made a backup with Rom Manager, it saved to /sdcard, since flashing 4.2, everything on /sdcard moved to /sdcard/1/... Rom Manager and any app honestly would have issues when the file location has changed suddenly and without its express permission. It's not the fault of Rom Manager that it can't find the file to restore your backup. Having an updated TWRP or CWM is supposed to help prevent the /sdcard contents from being merged to /sdcard/0, its not supposed to continue looking for the "new" file destination.
SlimSnoopOS said:
See my attached photo for what your file system should look like. I'm using ES File Explorer and that's my file system.
What do you mean your external SDcard is listed under Settings/Storage? Both of mine are listed, internal storage is first then my external sd card is second. Care to screenshot what you mean?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I can see what I said was confusing.
On the root of my device, among the usual folders, there is one named "sdcard" and another named "storage."
In the "sdcard" folder, all of the folders were empty; however, there is a folder named "0" which contained all of my sdcard contents from my internal sdcard.
In the "storage" folder from the root of my file system, it resembles what you have in your screenshot, except there are no asec and obb folders. In the sdcard folder is a replica of the 0 folder. It contains everything that was in my original internal sdcard. The extsdcard contains everything normally found on my external sd card.
When download something with the stock browser, it defaults to the sdcard folder on the root of file system.
I've attached some screenshots. Let me know what you think and thank you for the help.
PeterGunz said:
Sorry, I can see what I said was confusing.
On the root of my device, among the usual folders, there is one named "sdcard" and another named "storage."
In the "sdcard" folder, all of the folders were empty; however, there is a folder named "0" which contained all of my sdcard contents from my internal sdcard.
In the "storage" folder from the root of my file system, it resembles what you have in your screenshot, except there are no asec and obb folders. In the sdcard folder is a replica of the 0 folder. It contains everything that was in my original internal sdcard. The extsdcard contains everything normally found on my external sd card.
When download something with the stock browser, it defaults to the sdcard folder on the root of file system.
I've attached some screenshots. Let me know what you think and thank you for the help.
Click to expand...
Click to collapse
Oh! This is actually funny, we've been looking at the same thing from two different viewpoints. I see what you mean, /Storage and /sdcard are perfectly normal when you see them on the absolute root file system: "/". I always go to /mnt, that's where I have my file explorer default to open when I launch the app. Sdcard0 = sdcard, and various apps will use the names interchangeably. I have exactly the same paths /sdcard and /Storage, and I do see /Storage/sdcard0 and /Storage/extsdcard along with the same empty USB Drive folders. This is just how the "/" directory is split up. There isn't a duplication of files taking up more space than necessary, it's just showing you another path to get to those files. To reiterate, on "/" you can get to your sdcard contents in at least three paths: /mnt, /sdcard, and also /Storage/sdcard0
All that matters is the /sdcard/0 aka /Storage/sdcard0/0 is GONE. Which, in your original post you said no longer exists correct?
Sent from my SCH-I535 using xda app-developers app
I am still not understanding how there is a problem with executing a zip file that contains all the backup data. It doesn't matter where I move this zip file, as it seems it should be all inclusive of the backup data. Why does it matter the path of this file? What is the script looking for during restoration? Shouldn't it be looking within the archive?
I'm sorry, I feel like a tool, but again, I'm obviously missing some very basic part of what is happening when the file is accessed. As it is all inclusive, why is recovery looking for content anywhere outside of the archive?
monorailmedic said:
I am still not understanding how there is a problem with executing a zip file that contains all the backup data. It doesn't matter where I move this zip file, as it seems it should be all inclusive of the backup data. Why does it matter the path of this file? What is the script looking for during restoration? Shouldn't it be looking within the archive?
I'm sorry, I feel like a tool, but again, I'm obviously missing some very basic part of what is happening when the file is accessed. As it is all inclusive, why is recovery looking for content anywhere outside of the archive?
Click to expand...
Click to collapse
Backups cannot be flashed like other ZIP files. They need to be restored using the restore function of your recovery. The problem is that the CWM restore function is looking for its backups where it puts them (not surprisingly). Android 4.2 moved them to another location and you need to move them back.
SlimSnoopOS said:
Oh! This is actually funny, we've been looking at the same thing from two different viewpoints. I see what you mean, /Storage and /sdcard are perfectly normal when you see them on the absolute root file system: "/". I always go to /mnt, that's where I have my file explorer default to open when I launch the app. Sdcard0 = sdcard, and various apps will use the names interchangeably. I have exactly the same paths /sdcard and /Storage, and I do see /Storage/sdcard0 and /Storage/extsdcard along with the same empty USB Drive folders. This is just how the "/" directory is split up. There isn't a duplication of files taking up more space than necessary, it's just showing you another path to get to those files. To reiterate, on "/" you can get to your sdcard contents in at least three paths: /mnt, /sdcard, and also /Storage/sdcard0
All that matters is the /sdcard/0 aka /Storage/sdcard0/0 is GONE. Which, in your original post you said no longer exists correct?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Correct!
You helped me solve my problem. I was so confused for awhile there.
What should I rename my sdcard after copying everything over from "0"?
I just flashed back to 4.2.1 (AOLP) and I cannot find the contents of my internal sdcard anywhere. In fact, when I check storage on the system settings it only shows that I have a little over 12gbs total space on the internal sdcard. The 8gb I have on TW on the internal sdcard are not recognized by the rom. Any thoughts?

[Q] Internal storage problem

I have a p5113 galaxy tab 2 originally running jb 4.1.1. I upgraded to cyanogenmod 10.1 jb 4.2.2....i don't know much about how the sd card setup works but when I use root explorer I can see my sd card and my external sd. When I was flashing the rom again I notices that what is usually the highest level of the file system isn't really the highest level. in other words what is usually /system is actually /0/system and there are other files at the same level as the /0 file. The files appear to me to be the left over bits from the previous os... In other words they are the /sdcard/android/ and sd/card/pictures type files.... I'm concerned that they are taking up space... How do u get access to these files and is if safe to remove them?
I know this want the most articulate explanation of the problem but I hope I explained it well enough..... It's like I have an sdcard directory containing my root directory. If that's the way the rom works that's fine, but I would like to remove the extra files to get more space
kemmycupid said:
I have a p5113 galaxy tab 2 originally running jb 4.1.1. I upgraded to cyanogenmod 10.1 jb 4.2.2....i don't know much about how the sd card setup works but when I use root explorer I can see my sd card and my external sd. When I was flashing the rom again I notices that what is usually the highest level of the file system isn't really the highest level. in other words what is usually /system is actually /0/system and there are other files at the same level as the /0 file. The files appear to me to be the left over bits from the previous os... In other words they are the /sdcard/android/ and sd/card/pictures type files.... I'm concerned that they are taking up space... How do u get access to these files and is if safe to remove them?
I know this want the most articulate explanation of the problem but I hope I explained it well enough..... It's like I have an sdcard directory containing my root directory. If that's the way the rom works that's fine, but I would like to remove the extra files to get more space
Click to expand...
Click to collapse
do factory reset

[Q] Emulated Drive Kit Kang ROM 4.4

Since i cant yet post in the actual ROM thread i Though i would post here.
Ever since i flashed this ROM, my phone has created a copy of my drive and i can seem to access the original drive without going into the recovery.
It named the emulated drive 0.
When i try and system restore in order to do a clean flash, files carry over from the emulated drive and i cant figure out how to get rid of it. If anyone can help me i would appreciate it.
zepplin139 said:
Since i cant yet post in the actual ROM thread i Though i would post here.
Ever since i flashed this ROM, my phone has created a copy of my drive and i can seem to access the original drive without going into the recovery.
It named the emulated drive 0.
When i try and system restore in order to do a clean flash, files carry over from the emulated drive and i cant figure out how to get rid of it. If anyone can help me i would appreciate it.
Click to expand...
Click to collapse
I hear you bubba, I have wondered what the deal is with the /0, but I've never had any issues whatsoever with it, just have to poke around a bit differently now. I am still interested to know why/what/how though, learning is knowledge.
sammymcalaxy said:
I hear you bubba, I have wondered what the deal is with the /0, but I've never had any issues whatsoever with it, just have to poke around a bit differently now. I am still interested to know why/what/how though, learning is knowledge.
Click to expand...
Click to collapse
only problem is i cant remove the data from the initial drive so i have like 3 gigs left of storage when i could have the full 12 give or take.
I'd format the partitions.... not just wipe; then reflash.
sammymcalaxy said:
I hear you bubba, I have wondered what the deal is with the /0, but I've never had any issues whatsoever with it, just have to poke around a bit differently now. I am still interested to know why/what/how though, learning is knowledge.
Click to expand...
Click to collapse
Learning is knowledge. Mind you, the custom recoveries have newer versions so that part is the only thing that needs updating to today's standards.
So if I go to download the latest twrp (2.3.6.1) do I need to move it to the original SD and flash it from there? If that is the case I have no idea where the original one is. I can't find it in root explorer.
zepplin139 said:
So if I go to download the latest twrp (2.3.6.1) do I need to move it to the original SD and flash it from there? If that is the case I have no idea where the original one is. I can't find it in root explorer.
Click to expand...
Click to collapse
It should download to your Downloads folder if you downloaded it via a browser. If you used GooManager, then it would be in your GooManager folder. What are you using to flash TWRP 2.6.3.1?
SlimSnoopOS said:
It should download to your Downloads folder if you downloaded it via a browser. If you used GooManager, then it would be in your GooManager folder. What are you using to flash TWRP 2.6.3.1?
Click to expand...
Click to collapse
since its a .zip i figured i needed to flash it through my current recovery and then reboot but the downloads folder is in my emulated drive. Basically i cant see the actual drive anymore even in root explorer only the emulated drive and there is like 4 different ones.
zepplin139 said:
since its a .zip i figured i needed to flash it through my current recovery and then reboot but the downloads folder is in my emulated drive. Basically i cant see the actual drive anymore even in root explorer only the emulated drive and there is like 4 different ones.
Click to expand...
Click to collapse
If you're on JB AOSP, then your downloads folder is in /0/sdcard/downloads OR /sdcard0/downloads. Basically, start at /mnt OR /storage and choose "sdcard0" or "sdcard" as the phone interchangeably uses both to refer to internal storage. I'm used to using an IMG file for recoveries, if you don't mind my asking where did you find this TWRP zip from?
SlimSnoopOS said:
If you're on JB AOSP, then your downloads folder is in /0/sdcard/downloads OR /sdcard0/downloads. Basically, start at /mnt OR /storage and choose "sdcard0" or "sdcard" as the phone interchangeably uses both to refer to internal storage. I'm used to using an IMG file for recoveries, if you don't mind my asking where did you find this TWRP zip from?
Click to expand...
Click to collapse
Here is the .zip:
considering i cant post links yet i wont be able to link it too you but it was from the recovery thread in the dev forum.
I can get to that location the "/storage" but when im there i see "/emulated, /sdcard0, /sdcard1, /usbdisk1" .
when i open up /sdcard1 i see nothing and same with /usbdisk0.
/emulated has /0 and /legacy and both of them are identical inside.
but actually as im typing i just found the original sd card.
The path is /mnt/shell/emulated. so i guess thats some progress lol.
Glad you found that. It shouldn't matter, but what file manager are you using? Have you tried connecting to your computer and flipping through everything that way to find it? Ive found that to be a little less convoluted; knowledge is power.
sammymcalaxy said:
Glad you found that. It shouldn't matter, but what file manager are you using? Have you tried connecting to your computer and flipping through everything that way to find it? Ive found that to be a little less convoluted; knowledge is power.
Click to expand...
Click to collapse
Basically the Sd doesnt show up when i use the usb debugging and mtp so i cant access the original Sd from my pc i can only see the emulated drive, which is an issue. but im using root explorer.
Get ES3, open device (the"parent-most" directory) and then select extsd card.
Sent from my SCH-I535 using xda app-developers app

Categories

Resources