Factors such as the ADEV status can cause initialization to fail.
If this happens, verify the following.
We recommend directly calling InitializeAdev.exe
or InitializeAdevWin.exe
.
The following files also call these functions directly.
If you are using the InitializeAdev.exe
command-line tool, verify that the specified parameters match. (The serial number works with or without a check digit.)
Firmware version 13.0.0-3.0 and later can be used for ADEV. If you try to initialize the system with an earlier version of the firmware, it fails during the process.
Sometimes initializing the ADEV several times results in success. Try to initialize again.
Try to perform initialization after fully charging the ADEV console.
To charge the device you must attach the AC adapter. You cannot charge simply by connecting the device to a PC with a USB cable.
Try initializing the ADEV console again after reconnecting the USB cable and turning the power on.
If initialization is particularly unsuccessful, reconnect the USB cable with the following procedure.
If you are using the device connected to a Relay Box-A, try connecting it directly to the PC without using the relay box.
Exit Target Manager if it is running, and then try to initialize ADEV.
Sometimes Target Manager stays in the system tray, so also check there.
Verify that the ADEV is recognized as a USB device in Device Manager.
For more information, see 6 Initializing the ADEV > ADEV Drivers.
Sometimes initialization is successful after activating safe mode.
Safe mode is a mode that runs with minimum features.
Use safe mode in the following situations.
Safe mode can be activated with user operations.
After safe mode is activated, you may not be able to start in normal mode until the EDEV is initialized, so we recommend using safe mode only when you must restore or initialize.
There are two ways to enter safe mode.
We recommend this method.
Could Not Enter Safe Mode
For cases where the system enters the standard startup sequence and displays the menu despite attempting to enter safe mode, sometimes adjusting the intervals between button operations will fix the issue. (This is because some operations may not be detected if the intervals between button operations is too fast.)
As a guide, try using an interval of 0.6 seconds. This interval is equivalent to 4 beat intervals at 100 beats per minute (BPM). We recommend searching for a video with "BPM=100" that you can use as a guide.
Use the following procedure to verify whether the system has entered safe mode.
InitializeAdevWin.exe
, click Re-Scan to display the systems that are in safe mode in the list of connected systems.ADEV setup may fail depending on the compatibility with the USB 3.0 controller.
Try the following.
Setup has been confirmed to fail when using a PC with the following USB 3.0 controller.
If initialization is unsuccessful after attempting these procedures, contact Nintendo support.
When contacting support, the process will be smoother if you include the following information.
InitializeAdevWin
, copy the log that appears in the log window to a text file and send in the text file.InitializeAdev
, execute a log with the --verbose
option added and save it to a file.%USERPROFILE%\AppData\LocalLow\Nintendo
directory for the PC (and user) that encountered this symptom.
CONFIDENTIAL