My HOX+ is stuck on bootloop, but I'm trying to save my photos from it before I try to revive it (had photos of a very important event before phone went dead, it's really important so I really don't want to lose them). How do I transfer files off it (can't mount from recovery)? Tried using ./adb pull, but which directory path I need to pull the files from? (I'm using Mac)
The threads I read says to pull /sdcard/DCIM but doesn't work (remote object '/sdcard/DCIM' does not exist). My understanding is that HOX+ has a different way to store files, so I don't know how the directory works.
Thanks in advance!
allmidnighter said:
My HOX+ is stuck on bootloop, but I'm trying to save my photos from it before I try to revive it (had photos of a very important event before phone went dead, it's really important so I really don't want to lose them). How do I transfer files off it (can't mount from recovery)? Tried using ./adb pull, but which directory path I need to pull the files from? (I'm using Mac)
The threads I read says to pull /sdcard/DCIM but doesn't work (remote object '/sdcard/DCIM' does not exist). My understanding is that HOX+ has a different way to store files, so I don't know how the directory works.
Thanks in advance!
Click to expand...
Click to collapse
adb pull /sdcard
(Or use the most recent TWRP that has MTP mountable)
Related
I am trying to backup my phone with "adb pull /mnt/sdcard/ SDCARD20121115" but i keep having it fail in the middle of the backup with
cannot create 'SDCARD20121115\Folder\Folder2\Folder3\File.ext'
: No such file or directory
Ideas?
Still having issues with this and not sure how to backup my entire SD card...
Anyone?
Ok so i think i found the two different solutions to my problem.
First what actually was causing the problem was a folder with a $ sign in it. Using the command it looked like it failed on the file right before that folder so it didnt jump out right away.
Second i used a program called android commander that gives a gui. while this wasnt an actually solution i was able to select all but the folder tree structure that was failing instead of doing hundreds of directories by hand.
If anyone has any questions let me know.
*EDIT*
Looks like i had another failure on a folder. The folder had a trailing space "/storage/sdcard0/folder /file.ext"
Possible the $ sign works but to lazy to test.
I tried to search but didn't see anything here. I remember having this issue on another phone but forgot how to fix (not an issue with my Nexus or S3). So anyone figured out how to stop the annoying images from mounting everytime I plug in USB?
I believe you need to remove the CD.iso file.
Once I get my DNA I'll make a bloat free ROM with that and vol wake fixed.
Sent from my ADR6425LVW using xda app-developers app
they are in the \etc folder labled cdrom.iso and PCTool.iso
crackeyes said:
they are in the \etc folder labled cdrom.iso and PCTool.iso
Click to expand...
Click to collapse
Yup, delete those and no more annoying pop-ups.
Sorry to hijack a topic, but I didn't want to create another forum for the same question.
But, how can this be made possible? Do we have to wait for S-Off? (Still kind of new to this whole thing)
I have tried deleting the .ISO files through Root Explorer, no avail.
I tried to use Rexdog's De-Bloating Mod modified slightly to indicate a deletion of the two .ISO files. (I left everything the same except for the "/META-INF/com/google/android/updater-script" File.)
I modified that single file to say this,
Code:
ui_print("Removing Bloatware");
run_program("/sbin/mount", "/dev/block/mmcblk0p32", "/etc");
package_extract_dir("etc", "/etc");
show_progress(1, 15);
delete("/etc/CDROM.ISO", "/etc/PCTOOL.ISO");
ui_print("Unmounting Filesystems . . .");
unmount("/etc");
ui_print("Finished");
I was going off on a whim by editing the single file and hoping that it would work, but it doesn't appear to have worked. Is there something I was missing, or something else?
BigRed35m said:
Sorry to hijack a topic, but I didn't want to create another forum for the same question.
But, how can this be made possible? Do we have to wait for S-Off? (Still kind of new to this whole thing)
I have tried deleting the .ISO files through Root Explorer, no avail.
I tried to use Rexdog's De-Bloating Mod modified slightly to indicate a deletion of the two .ISO files. (I left everything the same except for the "/META-INF/com/google/android/updater-script" File.)
I modified that single file to say this,
Code:
ui_print("Removing Bloatware");
run_program("/sbin/mount", "/dev/block/mmcblk0p32", "/etc");
package_extract_dir("etc", "/etc");
show_progress(1, 15);
delete("/etc/CDROM.ISO", "/etc/PCTOOL.ISO");
ui_print("Unmounting Filesystems . . .");
unmount("/etc");
ui_print("Finished");
I was going off on a whim by editing the single file and hoping that it would work, but it doesn't appear to have worked. Is there something I was missing, or something else?
Click to expand...
Click to collapse
try to make the .iso in lowercase. That is the way it showed up on mine,
BigRed35m said:
I have tried deleting the .ISO files through Root Explorer, no avail.
Click to expand...
Click to collapse
I just deleted those 2 files through root explorer, and plugged in usb to pc. no more pop-ups.
jasonpascoe said:
I just deleted those 2 files through root explorer, and plugged in usb to pc. no more pop-ups.
Click to expand...
Click to collapse
That's only going to work until you reboot. /system is write protected. You have to go onto recovery mount /sys as writeable and use adb to delete the 2 files.
str8upx said:
That's only going to work until you reboot. /system is write protected. You have to go onto recovery mount /sys as writeable and use adb to delete the 2 files.
Click to expand...
Click to collapse
You are indeed knowledgable. You don't happen to know a place where i can fnd instruction on how to do that, would you? (for a noob?)
BigRed35m said:
You are indeed knowledgable. You don't happen to know a place where i can fnd instruction on how to do that, would you? (for a noob?)
Click to expand...
Click to collapse
Make sure you install the htc drivers (htc sync is not required) which is the first option when you plug in your phone to the pc.
Assuming you have usb debugging enabled and downloaded the android sdk http://developer.android.com/sdk/index.html#win-bundle and extracted the zip.
Navigate to the platform-tools folder inside /adt-bundle-windows-x86_64/sdk/platform-tools/
In an empty space inside that folder hold down shift and right click, then select open command window here.
Now in the command window type:
adb devices (your devices serial # should be displayed)
adb reboot recovery
On the phone select: mounts and storage, then: mount /system
Now in the command window type each of the following:
adb pull /system/etc/CDROM.ISO
adb pull /system/etc/PCTOOL.ISO
adb remount
adb shell
rm /system/etc/CDROM.ISO
rm /system/etc/PCTOOL.ISO
exit
adb reboot
You have now made copies of both of these files on to your pc and removed them from your phone.
To restore these files open a command window and mount /sys in recovery as shown above then:
adb push CDROM.ISO /system/etc
adb push PCTOOL.ISO /system/etc
I know it's weird, but basically when I flashed a 4.2 ROM about a month ago, I thought I lost all my files. But after snooping around, I found them in /data/media.
So I'm trying to use adb pull to get the files onto my PC. I do: adb pull /data/media \Downloads\New Folder and it just gives me a list of a bunch of adb commands I could use. So does anyone know how I can get the /data/media folder to my computer? I can't copy it to /sdcard/ because it's over 20GB and won't fit.
Also, I have the Sprint Galaxy Nexus...and yes, I'm rooted. My phone shows up when I do the adb devices command.
I decided just to do: adb pull /data/media and it looks like it's working. Sorry.
Andr3wD said:
I decided just to do: adb pull /data/media and it looks like it's working. Sorry.
Click to expand...
Click to collapse
You probably forgot this post existed, but just so you know the problem was having spaces in your local file path. If you enclosed the local path in quotes (assuming the path was valid) it works fine.
You probably forgot you replied (lol), but thanks for the help... this fits in with what I wanted to do too. Same problem, 4.2 upgrade, thought all my internal media stuff disappeared... decided to do a backup, but MTP is really slow and sucks, so I was looking into ways to use adb to backup my storage.
Hi guys, having an odd problem.
I've made some nandroid backups (about three) via CWM Recovery, and I can't seem to browse to them, or delete them.
It's definitely taking up space, and I'm not sure what to do now.
A backup that I made straight to my external SD card however, seems to be browse-able, so I'm a bit confused now.
Attached are some screenshots from ES File Browser (with root access turned on).
The last screenshot is going to /storage/sdcard0/clockworkmod/ (same directory, but now I can't seem to see anything about "backups").
I've also tried to delete these backups straight from CWM Recovery, but CWM says that it can't access the folder.
Oddly enough, if I do another backup (straight to internal), it seems to put all the files in /sdcard/Clockworkmod/backups but never to be accessed again.
Anyone have any ideas?
Delete via Windows Explorer .
jje
JJEgan said:
Delete via Windows Explorer .
jje
Click to expand...
Click to collapse
Thanks for the suggestion, but nope, that didn't work. (Obviously tried that first).
The folder was shown as empty via Windows.
After a lot of digging and trying different things (including Root Explorer and Terminal Emulator), I've managed to delete it.
I'll post the instructions so other people who may have similar problems in the future can follow it.
First, you'll need ADB and you'll need to reboot into CWM Recovery.
Once you've gotten that sorted, boot into CWM Recovery and go to "mount and storage" and then select "mount /data".
This will mount the /data structure which we need to use.
Afterwards in CMD, use the following:
Code:
adb root
adb shell
After this, you should be logged in as ~ (root)
Proceed to go into the directory using the cd function. (PROTIP: Use the ls function to check where you're going.)
You need to get to ../clockworkmod/backup/
You'll find that you can finally access the /backup/ folder, and you'll then be able to delete the files. Please note that the below command will delete ALL the files within this folder.
Code:
rm -rf *
Afterwards, do
Code:
cd ..
to get back to the ../clockworkmod/ folder and then run the below code to delete the now empty /backup/ folder:
Code:
rmdir backup
no, to be logged in as root you need to type in "su"
Hello everyone,
I am trying to copy my entire sd card from my Nexus 4 to pc using adb pull /mnt/sdcard E:\Backups\nexus-4-sdcard-final\
It's going fine for a while, it's transfering all my files but after a while i get this error message:
Code:
cannot create 'E:\Backups\nexus-4-sdcard-final\Android\data\com.google.android.apps.docs.editors.slides\files\pinned_docs_files_do_not_edit\454c288823047ca656676a9effef1cb5\files\documents\1-MHOqmLRrNLLzh9TfmnCIzJBWxW-TNz3MrEHMsRWjkM\image\1nFkukIkRz4mJ6HfTZCaSv8gv94X-HBr8Rw5Uyy8Y': No such file or directory
I googled for a while and the only thing i found is this guy with similar error but he had folder on his phone with file name longer than 255 characters, it couldn't be created in windows and that's why adb was failing.
My question is:
Is there any flag for adb pull or way to skip files that can not be copied and keep copying?
Or if you can tell me how to avoid this error it's even better solution.
Thanks,
Milos
milos91 said:
Hello everyone,
I am trying to copy my entire sd card from my Nexus 4 to pc using adb pull /mnt/sdcard E:\Backups\nexus-4-sdcard-final\
It's going fine for a while, it's transfering all my files but after a while i get this error message:
Code:
cannot create 'E:\Backups\nexus-4-sdcard-final\Android\data\com.google.android.apps.docs.editors.slides\files\pinned_docs_files_do_not_edit\454c288823047ca656676a9effef1cb5\files\documents\1-MHOqmLRrNLLzh9TfmnCIzJBWxW-TNz3MrEHMsRWjkM\image\1nFkukIkRz4mJ6HfTZCaSv8gv94X-HBr8Rw5Uyy8Y': No such file or directory
I googled for a while and the only thing i found is this guy with similar error but he had folder on his phone with file name longer than 255 characters, it couldn't be created in windows and that's why adb was failing.
My question is:
Is there any flag for adb pull or way to skip files that can not be copied and keep copying?
Or if you can tell me how to avoid this error it's even better solution.
Thanks,
Milos
Click to expand...
Click to collapse
Why not use ADB Backup?
Far better than manually pulling (and easier to restore too).
Jaskaranbir Singh said:
Why not use ADB Backup?
Far better than manually pulling (and easier to restore too).
Click to expand...
Click to collapse
Because I would like to be able to access my files without having to restore them back to a phone.
But if I don't find better solution I will do that. It's better than nothing, right? Thanks for the suggestion.
I have this problem too right now, What was your fix?
The first part of the problem is windows 10 you have to enable long file name support for paths longer than 260 characters . https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ The second part is we need to get Google or one of the XDA members to include a manifest file in the adb that tells windows it supports long file names then it may work otherwise do the adb pull in Linux.
idocinthebox said:
The first part of the problem is windows 10 you have to enable long file name support for paths longer than 260 characters . https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ The second part is we need to get Google or one of the XDA members to include a manifest file in the adb that tells windows it supports long file names then it may work otherwise do the adb pull in Linux.
Click to expand...
Click to collapse
is there a fix yet bro ?
milos91 said:
Hello everyone,
I am trying to copy my entire sd card from my Nexus 4 to pc using adb pull /mnt/sdcard E:\Backups\nexus-4-sdcard-final\
It's going fine for a while, it's transfering all my files but after a while i get this error message:
Code:
cannot create 'E:\Backups\nexus-4-sdcard-final\Android\data\com.google.android.apps.docs.editors.slides\files\pinned_docs_files_do_not_edit\454c288823047ca656676a9effef1cb5\files\documents\1-MHOqmLRrNLLzh9TfmnCIzJBWxW-TNz3MrEHMsRWjkM\image\1nFkukIkRz4mJ6HfTZCaSv8gv94X-HBr8Rw5Uyy8Y': No such file or directory
I googled for a while and the only thing i found is this guy with similar error but he had folder on his phone with file name longer than 255 characters, it couldn't be created in windows and that's why adb was failing.
My question is:
Is there any flag for adb pull or way to skip files that can not be copied and keep copying?
Or if you can tell me how to avoid this error it's even better solution.
Thanks,
Milos
Click to expand...
Click to collapse
did u find any soutions bro