3DS:Cleaninty: Difference between revisions

Line 14:

== Features ==

When given the unique data (<code>otp.bin</code> and either <code>SecureInfo.bin</code> or the serial number & eShop region) of a console and the required basic constants, cleaninty can act as the console it's given and do the following:

When given the unique data (<code>otp.bin</code> and either <code>SecureInfo.bin</code> or the serial number & eShop region data) of a console and the required basic constants, cleaninty can act as the console it's given and do the following:

* <code>GenJson</code>: Compiles the console's data into a single JSON file. This JSON is required for ~~almost~~ all other commands.

* <code>GenJson</code>: Compiles the console's data into a single JSON file. This JSON is required for all other commands except <code>RecoverIVS</code>.

* <code>CheckReg</code>: Obtains the console's eShop status and any titles attached to its eShop account, then updates the JSON file if any differences in the data are found.

* <code>SysTransfer</code>: Moves the eShop titles of the source console to the target console. This is the ~~main~~ part of what is known informally as a "SOAP Transfer".

* <code>SysTransfer</code>: Moves the eShop titles of the source console to the target console. This is the secondary part of what is known informally as a "SOAP Transfer".

** Using this command will trigger a 7-day cooldown on system transfers for both consoles, the same as a 'regular' transfer.

* <code>NNIDTransfer</code>: <u>(Still experimental. Use with caution.)</u> Moves only the NNIDs of the source console to the target console. This is not affected by cooldowns and does not trigger one.

* <code>NNIDTransfer</code>: <u>(Still experimental. Use with caution.)</u> Moves only the NNIDs of the source console to the target console. This is not affected by transfer cooldowns and does not trigger one.

* <code>LastTransfer</code>: Provides the date&time of the given console's last system transfer, the number of transfers it has ever done, and the time at which the current cooldown will expire.

* <code>LastTransfer</code>: Provides the date&time of the given console's last system transfer, the number of transfers it has ever done, and the time at which the current transfer cooldown will expire if there is one.

* <code>GetIVS</code>: Obtains the console's <code>movable.sed</code> from the SOAP servers, if the servers have a stored copy.

* <code>SetIVS</code>: Uploads the JSON's stored <code>movable.sed</code> to the SOAP servers. This will overwrite the current stored movable.

* <code>RecoverIVS</code>: Tries to recover a console's <code>movable.sed</code> from only its raw <code>otp.bin</code>~~, serial number,~~ and eShop region data.

* <code>RecoverIVS</code>: Tries to recover a console's <code>movable.sed</code> from only its raw <code>otp.bin</code> and eShop region data.

* <code>EShopDelete</code>: Deletes the target console's eShop account.

* <code>EShopRegionChange</code>: Deletes the target console's eShop account and attempts to create a new one in the entered region. This is the ~~other~~ part of a "SOAP Transfer" and is what grants eShop access again.

* <code>EShopRegionChange</code>: Deletes the target console's eShop account and attempts to create a new one in the entered region. This is the main part of a "SOAP Transfer" and is what grants eShop access again.

** If this fails, <code>SysTransfer</code> any conflicting titles off of the target console first.

* <code>ETickets</code>/<code>ETicketDownload</code>/<code>ETikTitleDownload</code>: Lists all owned eShop tickets / downloads all tickets / downloads the titles attached to all tickets, respectively, from the given console's eShop account.

Line 68:

The commands are the same on all operating systems. Run <code>cleaninty ctr (command) --help</code> for information on an individual command's syntax.

As an example, the list of commands needed to set up two consoles' data and perform a SOAP transfer between them would be as follows:

As an example, the minimum list of commands needed to set up two consoles' data and perform a SOAP transfer between them would be as follows:

# <code>cleaninty ctr GenJson --otp otp.bin --secureinfo secinfo.bin --out soap_donor.json</code>

# <code>cleaninty ctr GenJson --otp otp1.bin --secureinfo secinfo1.bin --out ~~soapee~~.json</code>

# <code>cleaninty ctr GenJson --otp otp1.bin --secureinfo secinfo1.bin --out soap_target.json</code>

# <code>cleaninty ctr CheckReg -C soap_donor.json</code>

# <code>cleaninty ctr CheckReg -C ~~soapee~~.json</code>

# <code>cleaninty ctr CheckReg -C soap_target.json</code>

# <code>cleaninty ctr EShopRegionChange -C soapee.json -r (new eShop region - required) -c (~~valid~~ country in chosen region - ~~might be optional~~) -l (~~valid~~ language in chosen region - optional)</code>

#* The CheckReg commands are not necessary if you are already certain the donor and target are in the same region.

#* If this succeeds, '''stop here'''. The next two commands are only needed if this fails.

# <code>cleaninty ctr EShopRegionChange -C soapee.json -r (new eShop region - required) -c (country in chosen region - usually required) -l (language in chosen region/country - optional)</code>

# <code>cleaninty ctr SysTransfer -s ~~soapee~~.json -t soap_donor.json</code>

#* If this succeeds, '''stop here'''. The next two commands are only needed if this one fails.

# <code>cleaninty ctr EShopRegionChange -C ~~soapee~~.json -r (new eShop region - required) -c (~~valid~~ country in chosen region - ~~might be optional~~) -l (~~valid~~ language in chosen region - optional)</code>

# <code>cleaninty ctr SysTransfer -s soap_target.json -t soap_donor.json</code>

# <code>cleaninty ctr EShopRegionChange -C soap_target.json -r (new eShop region - required) -c (country in chosen region - usually required) -l (language in chosen region/country - optional)</code>

@@ Line 14: / Line 14: @@
 == Features ==
-When given the unique data (<code>otp.bin</code> and either <code>SecureInfo.bin</code> or the serial number & eShop region) of a console and the required basic constants, cleaninty can act as the console it's given and do the following:
+When given the unique data (<code>otp.bin</code> and either <code>SecureInfo.bin</code> or the serial number & eShop region data) of a console and the required basic constants, cleaninty can act as the console it's given and do the following:
-* <code>GenJson</code>: Compiles the console's data into a single JSON file. This JSON is required for almost all other commands.
+* <code>GenJson</code>: Compiles the console's data into a single JSON file. This JSON is required for all other commands except <code>RecoverIVS</code>.
 * <code>CheckReg</code>: Obtains the console's eShop status and any titles attached to its eShop account, then updates the JSON file if any differences in the data are found.
-* <code>SysTransfer</code>: Moves the eShop titles of the source console to the target console. This is the main part of what is known informally as a "SOAP Transfer".
+* <code>SysTransfer</code>: Moves the eShop titles of the source console to the target console. This is the secondary part of what is known informally as a "SOAP Transfer".
 ** Using this command will trigger a 7-day cooldown on system transfers for both consoles, the same as a 'regular' transfer.
-* <code>NNIDTransfer</code>: <u>(Still experimental. Use with caution.)</u> Moves only the NNIDs of the source console to the target console. This is not affected by cooldowns and does not trigger one.
+* <code>NNIDTransfer</code>: <u>(Still experimental. Use with caution.)</u> Moves only the NNIDs of the source console to the target console. This is not affected by transfer cooldowns and does not trigger one.
-* <code>LastTransfer</code>: Provides the date&time of the given console's last system transfer, the number of transfers it has ever done, and the time at which the current cooldown will expire.
+* <code>LastTransfer</code>: Provides the date&time of the given console's last system transfer, the number of transfers it has ever done, and the time at which the current transfer cooldown will expire if there is one.
 * <code>GetIVS</code>: Obtains the console's <code>movable.sed</code> from the SOAP servers, if the servers have a stored copy.
 * <code>SetIVS</code>: Uploads the JSON's stored <code>movable.sed</code> to the SOAP servers. This will overwrite the current stored movable.
-* <code>RecoverIVS</code>: Tries to recover a console's <code>movable.sed</code> from only its raw <code>otp.bin</code>, serial number, and eShop region data.
+* <code>RecoverIVS</code>: Tries to recover a console's <code>movable.sed</code> from only its raw <code>otp.bin</code> and eShop region data.
 * <code>EShopDelete</code>: Deletes the target console's eShop account.
-* <code>EShopRegionChange</code>: Deletes the target console's eShop account and attempts to create a new one in the entered region. This is the other part of a "SOAP Transfer" and is what grants eShop access again.
+* <code>EShopRegionChange</code>: Deletes the target console's eShop account and attempts to create a new one in the entered region. This is the main part of a "SOAP Transfer" and is what grants eShop access again.
 ** If this fails, <code>SysTransfer</code> any conflicting titles off of the target console first.
 * <code>ETickets</code>/<code>ETicketDownload</code>/<code>ETikTitleDownload</code>: Lists all owned eShop tickets / downloads all tickets / downloads the titles attached to all tickets, respectively, from the given console's eShop account.
@@ Line 68: / Line 68: @@
 The commands are the same on all operating systems. Run <code>cleaninty ctr (command) --help</code> for information on an individual command's syntax.
-As an example, the list of commands needed to set up two consoles' data and perform a SOAP transfer between them would be as follows:
+As an example, the minimum list of commands needed to set up two consoles' data and perform a SOAP transfer between them would be as follows:
 # <code>cleaninty ctr GenJson --otp otp.bin --secureinfo secinfo.bin --out soap_donor.json</code>
-# <code>cleaninty ctr GenJson --otp otp1.bin --secureinfo secinfo1.bin --out soapee.json</code>
+# <code>cleaninty ctr GenJson --otp otp1.bin --secureinfo secinfo1.bin --out soap_target.json</code>
 # <code>cleaninty ctr CheckReg -C soap_donor.json</code>
-# <code>cleaninty ctr CheckReg -C soapee.json</code>
+# <code>cleaninty ctr CheckReg -C soap_target.json</code>
-# <code>cleaninty ctr EShopRegionChange -C soapee.json -r (new eShop region - required) -c (valid country in chosen region - might be optional) -l (valid language in chosen region - optional)</code>
+#* The CheckReg commands are not necessary if you are already certain the donor and target are in the same region.
-#* If this succeeds, '''stop here'''. The next two commands are only needed if this fails.
+# <code>cleaninty ctr EShopRegionChange -C soapee.json -r (new eShop region - required) -c  (country in chosen region - usually required) -l (language in chosen region/country - optional)</code>
-# <code>cleaninty ctr SysTransfer -s soapee.json -t soap_donor.json</code>
+#* If this succeeds, '''stop here'''. The next two commands are only needed if this one fails.
-# <code>cleaninty ctr EShopRegionChange -C soapee.json -r (new eShop region - required) -c (valid country in chosen region - might be optional) -l (valid language in chosen region - optional)</code>
+# <code>cleaninty ctr SysTransfer -s soap_target.json -t soap_donor.json</code>
+# <code>cleaninty ctr EShopRegionChange -C soap_target.json -r (new eShop region - required) -c (country in chosen region - usually required) -l (language in chosen region/country - optional)</code>