Related
Is is possible to change the root folder of the sd card used by android? I don't like having it create so many files/folders in the root of my card...
HDR said:
Is is possible to change the root folder of the sd card used by android? I don't like having it create so many files/folders in the root of my card...
Click to expand...
Click to collapse
Of course, you can place Android where ever you wish... just adjust the rel_path statement on your startup.txt.
For example, my installs are in /sdcard/Androids/TP2Ref - from Android's perspective. So in my startup.txt, I have
Code:
relpath=Androids/TP2Ref
- Just make sure that goes in the cmdline section.
Pretty sure this is in the FAQ... Try searching before you post
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
HDR said:
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
Click to expand...
Click to collapse
Only way to do that is to modify the source. I could easily make the changes in init for you, but the next time rootfs is updated (which will probably be soon since stinebd has to prep it for GB), you will lose those settings.
I'm working on some NAND stuff at the moment, so if you feel adventurous, all you have to do is modify init in rootfs and "compile" it. I have a little guide on compiling stuff (see bottom of post #1 for rootfs): http://forum.ppcgeeks.com/tp2-andro...modules-tinboot-nand-boot-more-beginners.html
I'll have a look at that, thanks.
HDR said:
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
Click to expand...
Click to collapse
I can at least give you a easy solution for the FSCK files (no offense Nate ). Put this in the "CustomCommands" section of your froyo.user.conf:
Code:
rm -f /sdcard/*.rec
im totally agree; i dont see the point of having the possibility of choosing android to start in whatever location we want....if anyways android will keep creating files/folders in the root of our sd card.
if i recall correctly the very first releases didn't have this problem it would be great if u devs can change this behaviour by default
elamodelmerol said:
im totally agree; i dont see the point of having the possibility of choosing android to start in whatever location we want....if anyways android will keep creating files/folders in the root of our sd card.
if i recall correctly the very first releases didn't have this problem it would be great if u devs can change this behaviour for default
Click to expand...
Click to collapse
This is what Android needs by default, and where they would normally be created by the system. It's nice to stick as close to AOSP as we can, because then there's this small group of devs that work for this company 'Google' that then become our system image maintainers. Thanks.
So I understand it's in a hidden partition but how do I access them?
TheUnknown7 said:
So I understand it's in a hidden partition but how do I access them?
Click to expand...
Click to collapse
Well, the partition isn't *hidden* per se, but it can't be accessed without a linux operating system. Windows can't read ext file systems natively, but if you run a linux distro such as ubuntu or fedora, you can. I'm assuming however, that you're running windows, like most do.
You CAN however, access it on your phone. If you prefer using the terminal emulator, you can do this:
(the # and $ just signify superuser/user rights, what should be shown by the terminal emulator, don't actually type the $ and #)
Code:
$ su
# cd /sd-ext
\\ To see a listing of files and folders, type this:
# ls
Alternatively, you may be able to use a root file explorer. In the file manager, click the 'up' button, or whatever will get you back to / on your phone. After this, you should see a number of folders, among these being system, data, dev, sdcard, and sd-ext. Press sd-ext, and there you are, in your sd-ext partition.
Let me know if that works for you or not, or if you didn't understand it.
Well I can run ubuntu with virtual machine, but I didn't find them there either, maybe I missed something? Do you need to enable a special option? Where would they be if I'm in the filemanager via ubuntu?
TheUnknown7 said:
Well I can run ubuntu with virtual machine, but I didn't find them there either, maybe I missed something? Do you need to enable a special option? Where would they be if I'm in the filemanager via ubuntu?
Click to expand...
Click to collapse
Virtual machines and peripheral usb devices can be glitchy. You'd have to run a live cd to really get it to work easily. Or, you can access the files from your phone.
Are you sure its not possible with VM? And when I used root file explorer and clicked on ext there was nothing there
TheUnknown7 said:
Are you sure its not possible with VM? And when I used root file explorer and clicked on ext there was nothing there
Click to expand...
Click to collapse
I only know how to with Oracle Virtualbox. There, if I remember correctly, in the top menu bar, there should be a usb or devices menu, and just select the mytouch slide and it SHOULD attach it to the virtual machine. It might not work though, since I tried doing s-off in the virtual machine and it didn't work. I had to burn a live cd.
It can mount just fine but what would the actual folder be called?
TheUnknown7 said:
It can mount just fine but what would the actual folder be called?
Click to expand...
Click to collapse
It's not a folder, it's a partition. If you're on ubuntu (it's been awhile, so I'm gonna be vague), there should be something in the system/administration menu called disk management or something of that sort. Click it, and it should show a list of devices and their drives/partitions. Check that the ext partition is mounted. You can also check in your Computer folder to see if it was automounted.
MusicMan374 said:
It's not a folder, it's a partition. If you're on ubuntu (it's been awhile, so I'm gonna be vague), there should be something in the system/administration menu called disk management or something of that sort. Click it, and it should show a list of devices and their drives/partitions. Check that the ext partition is mounted. You can also check in your Computer folder to see if it was automounted.
Click to expand...
Click to collapse
I followed your steps to view the sd ext from root explorer but I did not see nothing but a folder that said Parent which only takes you back to the main window. I did a SD Partition through ROM manager but I guess it didn't work. I want to do data2extbutI do not understand some step.
Did you try it through ubuntu like I suggested? And repartitioning through rom manager may have either erased and reformatted the ext partition, or it may have made a new partition alongside the existing one, further limiting your regular sd card space and possibly causing glitches with a2sd.
yes and I've never repartitioned. what is the folder called in ubuntu?
TheUnknown7 said:
yes and I've never repartitioned. what is the folder called in ubuntu?
Click to expand...
Click to collapse
Read my previous post about how to do it, go into administration and disk drives and mount the ext partition. It's a few posts back.
Sent from my T-Mobile myTouch 3G Slide
Probably I missed this question being answered somewhere, but I am tired of searching for it, so here it goes...
I decided not to root my device for now, and I am trying to get the most of it with stock limitations. Generally it is fine, but what bothers me most is the fact that i seem to be unable to write any files on phones internal memory. Is it so, that all / filesystem is inaccessible for write, or is there a dir where i could store some files i would like my phone to be able to access while sdcard is unmounted?
I may be wrong but thats the limitations of a "stock" phone,if you want access to the files you would have to root AFAI
That's exactly the impression I have, and I don't like the idea. I'm ex WM5/WM6 user, and I simply cannot understand why can't I have let's say /tmp/ dir just for myself...
banannq said:
That's exactly the impression I have, and I don't like the idea. I'm ex WM5/WM6 user, and I simply cannot understand why can't I have let's say /tmp/ dir just for myself...
Click to expand...
Click to collapse
Any reason for not rooting then? there are plenty stock roms/alternatives out there.
I grown tired of constantly tweaking my previous htc smartphone, decided to keep this one stock at least for now. I know rooting is an open door I will not want to close
and also I think there's no rooting method for gingerbread so far, is there?
As much as I know a downgrade is involved,I know what you mean about tinkering with the phone!It gets obsessive at times
You should have access to /data/local or at the very least /data/local/tmp
That's where fiels get pushed for rooting.
-Nipqer
The problem is I cannot even open /data directory
How are you trying to access the /data folder?
Cause if its some file manager app, some of them will only read sdcard.
-Nipqer
I'm used fre3vo to get temproot on my device (Z, Android 2.3.3),
and after that called:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
i can write to /system, but after reboot or remount into readonly all my changes dissapearing. Should i need S-OFF on my device? Can i get S-OFF without rollback to v1.34 on temp rooted 2.42?
Yeah the emmc is write protected when you are s-on, so any changes to /system will dissappear on reboot.
Unfortunately you cannot get s-off without downgrading to 1.34.
-Nipqer
Nipqer said:
How are you trying to access the /data folder?
Cause if its some file manager app, some of them will only read sdcard.
-Nipqer
Click to expand...
Click to collapse
Normaly I use total commander for android, but tried also ES File explorer, Linda manager, andexplorer... all of them basicaly let me view / folders (with exception of /data, /root, /cache etc) so i think it is filesystem condition rather than file manager fault...
banannq said:
Normaly I use total commander for android, but tried also ES File explorer, Linda manager, andexplorer... all of them basicaly let me view / folders (with exception of /data, /root, /cache etc) so i think it is filesystem condition rather than file manager fault...
Click to expand...
Click to collapse
try root explorer. you can still view directories without root (the app will just tell you that it failed to request superuser access). I'm pretty sure everything under /data is r/w access by default. My phone is rooted so I can't verify whether or not you can write to that directory on stock (I'd assume you could as long as there's free space available) but I can definitely recall being able to look at all my directories on stock using root explorer.
sephiroth1439 said:
try root explorer. you can still view directories without root (the app will just tell you that it failed to request superuser access). I'm pretty sure everything under /data is r/w access by default. My phone is rooted so I can't verify whether or not you can write to that directory on stock (I'd assume you could as long as there's free space available) but I can definitely recall being able to look at all my directories on stock using root explorer.
Click to expand...
Click to collapse
I guess it doesn't matter what software i use android simply locks me out of internal phone memory. It sucks, because phone was advertised as having over 1GB of internal storage space (no mention about it being inaccessible), and i can't even store ringtones on my device (have to use sdcard, and suffer side effect of it being unmounted at times). What a shame... with all the greatness, android sucks at very simple things
banannq said:
I guess it doesn't matter what software i use android simply locks me out of internal phone memory. It sucks, because phone was advertised as having over 1GB of internal storage space (no mention about it being inaccessible), and i can't even store ringtones on my device (have to use sdcard, and suffer side effect of it being unmounted at times). What a shame... with all the greatness, android sucks at very simple things
Click to expand...
Click to collapse
Don't blame Android for your carrier locking down your device
Sent from my HTC Vision using XDA App
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.
Hi guys,
I am trying to figure out a way to copy clockworkmod directory to my PC, as the backups are taking up too much unncessary space on the phone. The problem is that via MTP Windows Explorer simply hangs and doesn't copy a thing. My guess is that the underlying issue is the huge number of very small files in the /blob sub-directory.
Could anyone guide me how to accomplish this task, please? Or, alternatively, what other methods of backing straight to the PC are there?
Much obliged!
zkvvoob said:
Hi guys,
I am trying to figure out a way to copy clockworkmod directory to my PC, as the backups are taking up too much unncessary space on the phone. The problem is that via MTP Windows Explorer simply hangs and doesn't copy a thing. My guess is that the underlying issue is the huge number of very small files in the /blob sub-directory.
Could anyone guide me how to accomplish this task, please?
Much obliged!
Click to expand...
Click to collapse
MTP sucks. I prefer to use adb for this: adb pull /sdcard/clockworkmod D:\your\path\here
If you don't want to use the commandline, you can alternatively use an app like ES File Explorer to access a LAN share (shared folder/drive on your computer) and copy files this way.
adb pull?
Any time I transfer anything large it's what I use.
Code:
adb pull /sdcard/clockworkmod/ /Backup/
I believe that's the directory.
Just rename the "clockworkmod" folder to whatever it truly is if not.
This will put a "Backup" folder on your C:\ drive.
Edit:
Ninja'd.
Thank you very much, guys! I hadn't realised that adb pull could be used for copying a whole directory.
Reverse of this
Can anyone tell me how to reverse this using adb (i.e. move the directory back onto the phone)? Thanks.
grouseuk said:
Can anyone tell me how to reverse this using adb (i.e. move the directory back onto the phone)? Thanks.
Click to expand...
Click to collapse
[GUIDE] How-to copy files from/to your device
from Petrovski's sig
Thanks for the help with ADB pull. I knew about the push command, but being the noob I am I would never have thought that the opposite was that simple.
Now I have a GNex and I'm almost out of internal memory. I've copied my entire clockworkmod folder to my PC. I was wondering if I could delete the contents of the clockworkmod folder off of my phone (since it's all on the PC) to regain some storage space, and then only return the deleted contents to the phone when I need to do a nandroid restore without any problems occurring. I wouldn't want to go do all that only to arrive upon a large problem when I try to go back to stock JB JRO03C or anything like that.
kbolt said:
Thanks for the help with ADB pull. I knew about the push command, but being the noob I am I would never have thought that the opposite was that simple.
Now I have a GNex and I'm almost out of internal memory. I've copied my entire clockworkmod folder to my PC. I was wondering if I could delete the contents of the clockworkmod folder off of my phone (since it's all on the PC) to regain some storage space, and then only return the deleted contents to the phone when I need to do a nandroid restore without any problems occurring. I wouldn't want to go do all that only to arrive upon a large problem when I try to go back to stock JB JRO03C or anything like that.
Click to expand...
Click to collapse
I want to know this exact answer as well.
if you dont rename the folders, you wont have a problem.
I've found that the GNex toolkit makes it pretty easy to make backups, move them to your PC and restore plus a whole lot more. It's pretty good.
http://forum.xda-developers.com/showthread.php?t=1392310
+1 for adb
Large File Tip
THANK YOU!!
Jubakuba said:
adb pull?
Any time I transfer anything large it's what I use.
Code:
adb pull /sdcard/clockworkmod/ /Backup/
I believe that's the directory.
Just rename the "clockworkmod" folder to whatever it truly is if not.
This will put a "Backup" folder on your C:\ drive.
Edit:
Ninja'd.
Click to expand...
Click to collapse
Unable to see clockworkmod folder through file explorer
HI All,
Am not able to see the clockworkmod folder through File Explorer. Whereas after i take a backup through recovery, i can see the backup exists in /sdcard/clockworkmod/backup.
Please help.
Hi All,
Can anyone help with the above issue?
Use adb pull or an ftp server running on your device.
Sent from my Galaxy Nexus using Tapatalk 2