XYplorer - Portable File Manager for Windowsbatch file - Windows copy command return codes? - Stack Overflow
to customize your list.
Announcing Stack Overflow Documentation
We started with Q&A. Technical documentation is next, and we need your help.
Whether you're a beginner or an experienced developer, you can contribute.
I would like to test for the success/failure of a copy in a batch file, but I can't find any documentation on what if any errorlevel codes are returned.
For example
if %errorlevel%. eq 1. (
echo Copy x y failed due to ...
if %errorlevel% eq 2. (
echo Copy x y failed due to ...
... etc ...
5,30171540
I'd opt for xcopy in this case since the error levels are documented (see , paraphrased below):
Description
===========
Files were copied without error.
No files were found to copy.
The user pressed CTRL+C to terminate xcopy.
Initialization error occurred. There is not
enough memory or disk space, or you entered
an invalid drive name or invalid syntax on
the command line.
Disk write error occurred.
In any case, xcopy is a far more powerful solution. The
for copy does not document the error levels.
As an aside, you may want to rethink your use of the %errorlevel% variable. That has nasty ramifications (at least in some versions of Windows) if someone has explicitly done something silly like:
set errorlevel=22
In those cases, the actual variable will be used rather than grebbing the actual error level. The "normal" way of doing this is (in decreasing order since errorlevel is a "greater than or equal to" check):
if errorlevel 2 (
echo Copy x y failed due to reason 2
if errorlevel 1 (
echo Copy x y failed due to reason 1
If you are running Win7 or Win Server 2008 or later, you should look into , which is now the preferred mass-copy solution..
4,79432747
480k1159531406
I believe Copy only returns 0 for success or 1 for failure.
XCopy has documented return codes:
0 = Files were copied without error.
1 = No files were found to copy.
2 = The user pressed CTRL+C to terminate xcopy.
4 = Initialization error occurred. There is not enough memory or disk space, or you entered an invalid drive name or invalid syntax on the command line.
5 = Disk write error occurred.
7,04942252
It might also be worth pointing out that xcopy doesn't always return the error code you expect.
For example when trying to copy multiple files with a wildcard but there are no files to copy you expect a return error code of 1 ("No files were found to copy"), but it actually returns 0 ("Files were copied without error")
C:\Users\wilson&mkdir bla
C:\Users\wilson&mkdir blert
C:\Users\wilson&xcopy bla\* blert\
0 File(s) copied
C:\Users\wilson&echo %ERRORLEVEL%
There is also one point I would like to emphasize: xcopy as well as robocopy can only copy files, but they can't rename them.
While looking at the original situation (copy x y, which looks like a rename to me), I have the impression that the copy command still is the only one suitable for this purpose.
Your Answer
Sign up or
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Post as a guest
By posting your answer, you agree to the
Not the answer you're looking for?
Browse other questions tagged
Stack Overflow works best with JavaScript enabled/ How To Fix Your Soft-Bricked Android Device – First Aid Guide
on October 15, 2015
We like to play around with our Android devices. Testing new roms, kernels or other tweaks is, at least in my opinion, part of the whole Android experience. But sometimes things go wrong. First of all: Don’t panic! In contrast to iOS, Android is a rather open operating system which makes fixing a soft-bricked device sometimes really easy. This guide will take you through the standard steps to get your tablet or phone back running. You can revive your device as long as it is only soft-bricked! But beware, depending on your device it can be quite tricky to fix a soft-brick. A rule of thumb is that every device with an unlockable bootloader and accessible stock files (aka ). But don’t you worry: This process will hopefully help you with your problems.
What’s the difference between a hard and a soft-brick?
Before we get started I quickly want to discuss the difference between a soft-bricked and a hard-bricked device. It’s actually quite simple. Ask yourself the following question: What can I do with a brick? It’s simple – basically nothing. You can use it as a paperweight or decoration. You can easily identify a (hard-) bricked device based on the following points:
It does not turn on anymore AND
Your computer / Mac does not recognise it anymore
In contrast to that, a soft-bricked device is only half-way dead. In most cases something went wrong while flashing something like a custom ROM, camera mod or app in your custom recovery mode. Because of this, your device is not booting anymore (the so-called bootloop) or is constantly crashing. The basic solution to this problem is flashing a clean & working version of Android to your device. There are different ways for doing this, but most of the time you’ll restore a backup, flash a custom ROM or stock images to your device.
The easiest fix: Use a toolkit for your device
Make sure to check the
if there is a toolkit available for your device which might make the recovering process far easier. Toolkits often install the correct drivers, download the right files and guide you through the process of getting your phone or tablet back running.
Nexus 5 –
Samsung Galaxy S6 –
Samsung Galaxy Note 4 –
If you rather want to do everything by hand, make sure that the latest ADB and fastboot drivers are installed on your computer. There are two ways to do this:
1. Download the Android SDK and extract them from there. Here’s a .
2. Download t or
Write down the location of the drivers (or copy them to a easily accessible folder) – you’ll need them later!
Android device does not boot anymore
If you’re able to turn on your phone or tablet, but it won’t boot, it mean that the device is stuck in the so-called “bootloop”. This happens if you flashed (installed) something that does not work with your device. This is typically a ROM or Kernel, or a combination of both. What happens in this case, is that your device is trying to load something which overloads the system memory, resulting in the device crashing. In the following I’m going to guide you through different steps that you need to follow. This should help you with finding your problem and getting the perfect solution for it.
Step 1. Does your device boot?
Yes – Go to step 3
No – Go to step 2
Step 2. Try the right button combination for your device to get into recovery mode. It’s usually a combination of the power and volume buttons. DroidViews created a nice list
for the most popular devices.
Does it work?
Yes – Go to step 3
No – It looks like your phone is bricked. Try consulting the
for more help
Step 3. Are you able to access the bootloader or recovery mode?
Yes – Go to step 4
No – Go to step 2
Step 4. Do you have a Nandroid backup?
Yes – Go to step 9
No – Go to step 5
Step 5. Do you still have a (former) working custom ROM zip-file on your device?
Yes – Go to step 6
No – Go to step 7
Step 6. Flash the (former) working Custom ROM and reboot. Don’t flash a custom Kernel unless you’re specifically asked to do so by the ROM developer.
Did it work?
Yes – Enjoy your working device!
No – Go to step 8
Step 7. Try pushing a working ROM to your device. If your device has a SD card slot, simply place the files on it and install the files from there. In the case that your phone or tablet does not have a SD card slot, try pushing the files to the internal storage with ADB. I’ve explained the process here. Go back to step 6
Step 8. Are stock ROM files available?
Yes – Try installing them. Most stock files come with instructions how to install them. Follow them. Your device should be working again
No – Try consulting the .
Step 9. Restore your backup. Your device should be working now again.
Custom Recovery is gone
Sometimes flashing a ROM can overwrite your custom recovery. There are two ways to get it back.
1. You have root access
and use it to flash ClockworkMod Recovery or
Install the
and use it to flash Team Win Recovery Project
Personally, I would recommend to use TWRP. After doing this, your custom recovery should be working again!
2. You don’t have root access
Download the
image for your device and save it into the same directory as the ADB / fastboot drivers
Boot into the bootloader. Key-combinations can be found .
Open the Windows command or Mac terminal and navigate to the direction where the ADB / fastboot drivers are located
Execute the following command: fastboot flash recovery filename.img (with filename.img being the name of the recovery image you downloaded earlier)
Custom recovery should be working again!
You don’t have root access anymore
If your root stops working, there are two ways to get it back:
1. You still have access to a custom recovery
and install the zip file in custom recovery
2. You don’t have access to a custom recovery
Save the file on your devices’ storage
Install the zip file in custom recovery
How to get files to or from a device if you can’t boot to Android
If your Android device does not boot anymore it can be tricky to get files to your device (to install a backup) or from your device (to backup personal files on your computer). Luckily, TWRP and CWMR include ADB drivers.
Open the Windows command or Mac terminal and navigate to the direction where the ADB / fastboot drivers are located
Use the following command to push files to your device:
ADB push filename(or folder) directory on your device
Example: ADB push /backup/ /sdcard/ – This will transfer the complete folder backup from your computer to the SD card on your device
Use the following command to get files from your device:
ADB get filename(or folder) directory on your computer
Example: ADB get /downloads/ /backup – This will transfer the complete folder “downloads” from your device to the /backup/ folder on your computer
The files should now be on your computer or internal storage
Final words
I hope that I was able to offer you a first-aid for your Android emergency. There are many ways to get your Android device back to life. Please comment below or consult the XDA-developers forums if you have any questions!
Are you interested in more Android related guides?
Have a look at our .
& Previous Story
Next Story &
| May 8, 2016
| April 3, 2016
| December 1, 2015
| August 18, 2016
| August 16, 2016
| August 13, 2016
Become a part of us!
Write for trendblog.netThings to Do Before and After Installing a Custom ROM
Welcome! Log into your accountyour usernameyour password Password recoveryRecover your passwordyour email
Latest Posts