Hacking Decrypt9 brick NANDmin.bin sysNAND question

Starzcream

Well-Known Member
OP
Newcomer
Joined
Feb 22, 2017
Messages
84
Trophies
0
Age
37
XP
93
Country
United States
I ran decrypt9 auto ctrnand twice and accidently overwrote my first sysand backup. I ignorantly hit a to reboot without restoring. Question is now, I have a hardmod it works sometimes lol. Before i restore the sysnand dump, is it still valid since i overwrote it after a failed decrypt9 downgrade?

Initializing SD card... success
Build: Decrypt9WIP (2017/01/15)
Work directory:

/files9
Game directory: /files9
sector0x96 Key: otp.bin not found
0x03 KeyX & KeyY:

already set up
0x25 KeyX: already set up
0x18 KeyX: not found
0x1B KeyX: not found
0x24 KeyY: not found
Finalizing Initialization...

Initialization: partially failed

Unmounting SD card...

You selected [Auto CTRNAND Transfer].

This feature writes to

the SysNAND.
This may overwrite important data!

If you wish to proceed, enter:
<Left>, <Up>, <Right>, <Up>, <A>

(B to return, START to reboot)

Selected: [Auto

CTRNAND Transfer]
A9LH not detected, checking FIRM0...
Select CTRNAND transfer

image
Use arrow keys and <A> to choose a file
2.1.0-4U_ctrtransfer_o3ds.bin
Image

size is: 794624000 byte

Step #0: Optional NAND backup
Press <B> to skip and

continue without backup
Dumping SysNAND. Size (MB): 943
Use arrow keys and <A> to

choose a name
NANDmin.bin
Creating NANDmin.bin ...
NAND dump SHA256: BDBF5E72...
Store to NANDmin.bin.sha: ok

Step #1: .SHA verification of CTRNAND image...
Checking hash from .SHA file...
Step #1 success!

Step #2: Dumping transfer files
Searching for SecureInfo_A...
Found at 0E35C000, size 273b
Creating

7A6CD9F5_SecureInfo_A ...
Searching for movable.sed...
Found at 0E300000, size

320b
Creating 7A6CD9F5_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found

at 0E2E4000, size 272b
Creating 7A6CD9F5_LocalFriendCodeSeed_B ...
Searching for

configsave.bin...
Found at 0F3B0000, size 256kB
Creating 7A6CD9F5_configsave.bin

...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Injecting 2.1.0-

4U_ctrtransfer_o3ds.bin (757 MB)...
Opening 2.1.0-4U_ctrtransfer_o3ds.bin ...
Step

#3 success!

Step #4: Injecting transfer files
Searching for SecureInfo_A...
Found at

0B9CC000, size 273b
Opening 7A6CD9F5_SecureInfo_A ...
Fixing file CMAC for

console...
Searching for SecureInfo_A...
Found at 0B9CC000, size 273b
File has no

fixable CMAC
Searching for movable.sed...
Found at 13A14000, size 320b
Opening

7A6CD9F5_movable.sed ...
Fixing file CMAC for console...
Searching for

movable.sed...
Found at 13A14000, size 320b
CMAC mismatch -> fixed CMAC
Searching

for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening

7A6CD9F5_LocalFriendCodeSeed_B ...
Fixing file CMAC for console...
Searching for

LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
File has no fixable CMAC
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Opening

7A6CD9F5_configsave.bin ...
Fixing file CMAC for console...
Searching for

configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
movable.sed is

corrupt!
Step #4 success!

Step #5: Fixing CMACs and paths
Checking and fixing <id0>

folder
/DATA/<ID0>: renamed to match
Fixing essential system file CMACs
Searching

for ticket.db...
Found at 17158000, size 35MB
CMAC id: 0
CMAC mismatch -> fixed

CMAC
Searching for certs.db...
Found at 0B9C4000, size 24kB
CMAC id: 1
CMAC mismatch

-> fixed CMAC
Searching for title.db...
Found at 0DD80000, size 403kB
CMAC id: 2
CMAC

mismatch -> fixed CMAC
Searching for import.db...
Found at 0DD4C000, size 203kB
CMAC

id: 3
CMAC mismatch -> fixed CMAC
Searching for movable.sed...
Found at 13A14000,

size 320b
Validated CMAC okay
Fixing other system file CMACs
Searching for

tmp_t.db...
Found at 0DDEC000, size 54kB
CMAC id: 4
CMAC mismatch -> fixed CMAC
Searching for tmp_i.db...
Found at 0DDE8000, size 10kB
CMAC id: 5
CMAC mismatch ->

fixed CMAC
Searching for seedsave.bin...
Failed!
Searching for nagsave.bin...
Failed!
Searching for nnidsave.bin...
Failed!
Searching for friendsave.bin...
Failed!
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id:

00010017
movable.sed is corrupt!
Step #5 success!

Step #6: Dumping and injecting

NATIVE_FIRM
Searching title "NATIVE_FIRM"...
Trying title ID 0004013800000002

(region 0)
Method 1: Search in title.db...
Found title ID 0004013800000002
TMD0

found at 137EC000, size 2868b
APP0 found at 11B04000, size 879kB
Dumping &

decrypting NATIVE_FIRM.app...
Creating NATIVE_FIRM.app ...
Not a NCCH container
NATIVE_FIRM not found, failure!
Auto CTRNAND Transfer: failed!

Press B to return,

START to reboot.

You selected [Auto CTRNAND Transfer].

This feature writes to the

SysNAND.
This may overwrite important data!

If you wish to proceed, enter:
<Left>,

<Up>, <Right>, <Up>, <A>

(B to return, START to reboot)

Selected: [Auto CTRNAND

Transfer]
A9LH not detected, checking FIRM0...
Select CTRNAND transfer image
Use

arrow keys and <A> to choose a file
2.1.0-4U_ctrtransfer_o3ds.bin
Image size is:

794624000 byte
Region does not match
Using SecureInfo_A from image

Step #0: Optional

NAND backup
Press <B> to skip and continue without backup
Dumping SysNAND. Size

(MB): 943
Use arrow keys and <A> to choose a name
NANDmin.bin (!)
Press <A> to

overwrite existing file
Creating NANDmin.bin ...
NAND dump SHA256: AA0BC6EF...
Store

to NANDmin.bin.sha: ok

Step #1: .SHA verification of CTRNAND image...
Checking hash

from .SHA file...
Step #1 success!

Step #2: Dumping transfer files
Searching for

SecureInfo_A...
Found at 0B9CC000, size 273b
Creating 7A6CD9F5_SecureInfo_A ...
Searching for movable.sed...
Found at 13A14000, size 320b
Creating

7A6CD9F5_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000,

size 272b
Creating 7A6CD9F5_LocalFriendCodeSeed_B ...
Searching for

configsave.bin...
Found at 0E1C0000, size 256kB
Creating 7A6CD9F5_configsave.bin

...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Injecting 2.1.0-

4U_ctrtransfer_o3ds.bin (757 MB)...
Opening 2.1.0-4U_ctrtransfer_o3ds.bin ...
Step

#3 success!

Step #4: Injecting transfer files
Searching for movable.sed...
Found at

13A14000, size 320b
Opening 7A6CD9F5_movable.sed ...
Fixing file CMAC for

console...
Searching for movable.sed...
Found at 13A14000, size 320b
CMAC mismatch

-> fixed CMAC
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening 7A6CD9F5_LocalFriendCodeSeed_B ...
Fixing file CMAC for console...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
File has no

fixable CMAC
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Opening

7A6CD9F5_configsave.bin ...
Fixing file CMAC for console...
Searching for

configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
movable.sed is

corrupt!
Step #4 success!

Step #5: Fixing CMACs and paths
Checking and fixing <id0>

folder
/DATA/<ID0>: renamed to match
Fixing essential system file CMACs
Searching

for ticket.db...
Found at 17158000, size 35MB
CMAC id: 0
CMAC mismatch -> fixed

CMAC
Searching for certs.db...
Found at 0B9C4000, size 24kB
CMAC id: 1
CMAC mismatch

-> fixed CMAC
Searching for title.db...
Found at 0DD80000, size 403kB
CMAC id: 2
CMAC

mismatch -> fixed CMAC
Searching for import.db...
Found at 0DD4C000, size 203kB
CMAC

id: 3
CMAC mismatch -> fixed CMAC
Searching for movable.sed...
Found at 13A14000,

size 320b
Validated CMAC okay
Fixing other system file CMACs
Searching for

tmp_t.db...
Found at 0DDEC000, size 54kB
CMAC id: 4
CMAC mismatch -> fixed CMAC
Searching for tmp_i.db...
Found at 0DDE8000, size 10kB
CMAC id: 5
CMAC mismatch ->

fixed CMAC
Searching for seedsave.bin...
Failed!
Searching for nagsave.bin...
Failed!
Searching for nnidsave.bin...
Failed!
Searching for friendsave.bin...
Failed!
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id:

00010017
movable.sed is corrupt!
Step #5 success!

Step #6: Dumping and injecting

NATIVE_FIRM
Searching title "NATIVE_FIRM"...
Trying title ID 0004013800000002

(region 1)
Method 1: Search in title.db...
Found title ID 0004013800000002
TMD0

found at 137EC000, size 2868b
APP0 found at 11B04000, size 879kB
Dumping &

decrypting NATIVE_FIRM.app...
Creating NATIVE_FIRM.app ...
Not a NCCH container
NATIVE_FIRM not found, failure!
Auto CTRNAND Transfer: failed!

Press B to return,

START to reboot.

Unmounting SD card...
 
Last edited by Starzcream,

munchy_cool

Well-Known Member
Member
Joined
Dec 15, 2016
Messages
641
Trophies
0
XP
313
Country
United States
When did you restart? While it was backing up existing sysnand or while it was writing 2.1.
What size is your nand backup? what console do you have? mind posting a screenshot of your files9 folder.
 

CrispyCola

zero-two
Member
Joined
Feb 8, 2017
Messages
320
Trophies
0
Location
the stars
XP
261
Country
United States
I ran decrypt9 auto ctrnand twice and accidently overwrote my first sysand backup. I ignorantly hit a to reboot without restoring. Question is now, I have a hardmod it works sometimes lol. Before i restore the sysnand dump, is it still valid since i overwrote it after a failed decrypt9 downgrade?

Initializing SD card... success
Build: Decrypt9WIP (2017/01/15)
Work directory:

/files9
Game directory: /files9
sector0x96 Key: otp.bin not found
0x03 KeyX & KeyY:

already set up
0x25 KeyX: already set up
0x18 KeyX: not found
0x1B KeyX: not found
0x24 KeyY: not found
Finalizing Initialization...

Initialization: partially failed

Unmounting SD card...

You selected [Auto CTRNAND Transfer].

This feature writes to

the SysNAND.
This may overwrite important data!

If you wish to proceed, enter:
<Left>, <Up>, <Right>, <Up>, <A>

(B to return, START to reboot)

Selected: [Auto

CTRNAND Transfer]
A9LH not detected, checking FIRM0...
Select CTRNAND transfer

image
Use arrow keys and <A> to choose a file
2.1.0-4U_ctrtransfer_o3ds.bin
Image

size is: 794624000 byte

Step #0: Optional NAND backup
Press <B> to skip and

continue without backup
Dumping SysNAND. Size (MB): 943
Use arrow keys and <A> to

choose a name
NANDmin.bin
Creating NANDmin.bin ...
NAND dump SHA256: BDBF5E72...
Store to NANDmin.bin.sha: ok

Step #1: .SHA verification of CTRNAND image...
Checking hash from .SHA file...
Step #1 success!

Step #2: Dumping transfer files
Searching for SecureInfo_A...
Found at 0E35C000, size 273b
Creating

7A6CD9F5_SecureInfo_A ...
Searching for movable.sed...
Found at 0E300000, size

320b
Creating 7A6CD9F5_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found

at 0E2E4000, size 272b
Creating 7A6CD9F5_LocalFriendCodeSeed_B ...
Searching for

configsave.bin...
Found at 0F3B0000, size 256kB
Creating 7A6CD9F5_configsave.bin

...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Injecting 2.1.0-

4U_ctrtransfer_o3ds.bin (757 MB)...
Opening 2.1.0-4U_ctrtransfer_o3ds.bin ...
Step

#3 success!

Step #4: Injecting transfer files
Searching for SecureInfo_A...
Found at

0B9CC000, size 273b
Opening 7A6CD9F5_SecureInfo_A ...
Fixing file CMAC for

console...
Searching for SecureInfo_A...
Found at 0B9CC000, size 273b
File has no

fixable CMAC
Searching for movable.sed...
Found at 13A14000, size 320b
Opening

7A6CD9F5_movable.sed ...
Fixing file CMAC for console...
Searching for

movable.sed...
Found at 13A14000, size 320b
CMAC mismatch -> fixed CMAC
Searching

for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening

7A6CD9F5_LocalFriendCodeSeed_B ...
Fixing file CMAC for console...
Searching for

LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
File has no fixable CMAC
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Opening

7A6CD9F5_configsave.bin ...
Fixing file CMAC for console...
Searching for

configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
movable.sed is

corrupt!
Step #4 success!

Step #5: Fixing CMACs and paths
Checking and fixing <id0>

folder
/DATA/<ID0>: renamed to match
Fixing essential system file CMACs
Searching

for ticket.db...
Found at 17158000, size 35MB
CMAC id: 0
CMAC mismatch -> fixed

CMAC
Searching for certs.db...
Found at 0B9C4000, size 24kB
CMAC id: 1
CMAC mismatch

-> fixed CMAC
Searching for title.db...
Found at 0DD80000, size 403kB
CMAC id: 2
CMAC

mismatch -> fixed CMAC
Searching for import.db...
Found at 0DD4C000, size 203kB
CMAC

id: 3
CMAC mismatch -> fixed CMAC
Searching for movable.sed...
Found at 13A14000,

size 320b
Validated CMAC okay
Fixing other system file CMACs
Searching for

tmp_t.db...
Found at 0DDEC000, size 54kB
CMAC id: 4
CMAC mismatch -> fixed CMAC
Searching for tmp_i.db...
Found at 0DDE8000, size 10kB
CMAC id: 5
CMAC mismatch ->

fixed CMAC
Searching for seedsave.bin...
Failed!
Searching for nagsave.bin...
Failed!
Searching for nnidsave.bin...
Failed!
Searching for friendsave.bin...
Failed!
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id:

00010017
movable.sed is corrupt!
Step #5 success!

Step #6: Dumping and injecting

NATIVE_FIRM
Searching title "NATIVE_FIRM"...
Trying title ID 0004013800000002

(region 0)
Method 1: Search in title.db...
Found title ID 0004013800000002
TMD0

found at 137EC000, size 2868b
APP0 found at 11B04000, size 879kB
Dumping &

decrypting NATIVE_FIRM.app...
Creating NATIVE_FIRM.app ...
Not a NCCH container
NATIVE_FIRM not found, failure!
Auto CTRNAND Transfer: failed!

Press B to return,

START to reboot.

You selected [Auto CTRNAND Transfer].

This feature writes to the

SysNAND.
This may overwrite important data!

If you wish to proceed, enter:
<Left>,

<Up>, <Right>, <Up>, <A>

(B to return, START to reboot)

Selected: [Auto CTRNAND

Transfer]
A9LH not detected, checking FIRM0...
Select CTRNAND transfer image
Use

arrow keys and <A> to choose a file
2.1.0-4U_ctrtransfer_o3ds.bin
Image size is:

794624000 byte
Region does not match
Using SecureInfo_A from image

Step #0: Optional

NAND backup
Press <B> to skip and continue without backup
Dumping SysNAND. Size

(MB): 943
Use arrow keys and <A> to choose a name
NANDmin.bin (!)
Press <A> to

overwrite existing file
Creating NANDmin.bin ...
NAND dump SHA256: AA0BC6EF...
Store

to NANDmin.bin.sha: ok

Step #1: .SHA verification of CTRNAND image...
Checking hash

from .SHA file...
Step #1 success!

Step #2: Dumping transfer files
Searching for

SecureInfo_A...
Found at 0B9CC000, size 273b
Creating 7A6CD9F5_SecureInfo_A ...
Searching for movable.sed...
Found at 13A14000, size 320b
Creating

7A6CD9F5_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000,

size 272b
Creating 7A6CD9F5_LocalFriendCodeSeed_B ...
Searching for

configsave.bin...
Found at 0E1C0000, size 256kB
Creating 7A6CD9F5_configsave.bin

...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Injecting 2.1.0-

4U_ctrtransfer_o3ds.bin (757 MB)...
Opening 2.1.0-4U_ctrtransfer_o3ds.bin ...
Step

#3 success!

Step #4: Injecting transfer files
Searching for movable.sed...
Found at

13A14000, size 320b
Opening 7A6CD9F5_movable.sed ...
Fixing file CMAC for

console...
Searching for movable.sed...
Found at 13A14000, size 320b
CMAC mismatch

-> fixed CMAC
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening 7A6CD9F5_LocalFriendCodeSeed_B ...
Fixing file CMAC for console...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
File has no

fixable CMAC
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Opening

7A6CD9F5_configsave.bin ...
Fixing file CMAC for console...
Searching for

configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
movable.sed is

corrupt!
Step #4 success!

Step #5: Fixing CMACs and paths
Checking and fixing <id0>

folder
/DATA/<ID0>: renamed to match
Fixing essential system file CMACs
Searching

for ticket.db...
Found at 17158000, size 35MB
CMAC id: 0
CMAC mismatch -> fixed

CMAC
Searching for certs.db...
Found at 0B9C4000, size 24kB
CMAC id: 1
CMAC mismatch

-> fixed CMAC
Searching for title.db...
Found at 0DD80000, size 403kB
CMAC id: 2
CMAC

mismatch -> fixed CMAC
Searching for import.db...
Found at 0DD4C000, size 203kB
CMAC

id: 3
CMAC mismatch -> fixed CMAC
Searching for movable.sed...
Found at 13A14000,

size 320b
Validated CMAC okay
Fixing other system file CMACs
Searching for

tmp_t.db...
Found at 0DDEC000, size 54kB
CMAC id: 4
CMAC mismatch -> fixed CMAC
Searching for tmp_i.db...
Found at 0DDE8000, size 10kB
CMAC id: 5
CMAC mismatch ->

fixed CMAC
Searching for seedsave.bin...
Failed!
Searching for nagsave.bin...
Failed!
Searching for nnidsave.bin...
Failed!
Searching for friendsave.bin...
Failed!
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id:

00010017
movable.sed is corrupt!
Step #5 success!

Step #6: Dumping and injecting

NATIVE_FIRM
Searching title "NATIVE_FIRM"...
Trying title ID 0004013800000002

(region 1)
Method 1: Search in title.db...
Found title ID 0004013800000002
TMD0

found at 137EC000, size 2868b
APP0 found at 11B04000, size 879kB
Dumping &

decrypting NATIVE_FIRM.app...
Creating NATIVE_FIRM.app ...
Not a NCCH container
NATIVE_FIRM not found, failure!
Auto CTRNAND Transfer: failed!

Press B to return,

START to reboot.

Unmounting SD card...

Can you access hourglass9/decrypt9?


Sent from my iPhone using Tapatalk
 

Starzcream

Well-Known Member
OP
Newcomer
Joined
Feb 22, 2017
Messages
84
Trophies
0
Age
37
XP
93
Country
United States
Can you access hourglass9/decrypt9?


Sent from my iPhone using Tapatalk

No hourglass it never completed Ctr transfer. Question is does decrypt9 dump a nand backup before it modifies anything when auto ctr nand is ran twice? Or is it still a good nand backup if it fails to auto ctr?
 

Dimensional

Well-Known Member
Member
Joined
Dec 7, 2008
Messages
1,008
Trophies
1
Age
34
Location
Texas
XP
2,794
Country
United States
No hourglass it never completed Ctr transfer. Question is does decrypt9 dump a nand backup before it modifies anything when auto ctr nand is ran twice? Or is it still a good nand backup if it fails to auto ctr?
If things were done properly, and there was no hasty button press, it would have backed up your NAND first before injecting the 2.1.0 CTR file. With the backup corrupted, you're out of luck. You need a valid, uncorrupted backup unique to your console for the hardmod to work.
 
Last edited by Dimensional,

Starzcream

Well-Known Member
OP
Newcomer
Joined
Feb 22, 2017
Messages
84
Trophies
0
Age
37
XP
93
Country
United States
When did you restart? While it was backing up existing sysnand or while it was writing 2.1.
What size is your nand backup? what console do you have? mind posting a screenshot of your files9 folder.
It was after a failed auto ctr transfer I also used a 128gb ad don't know if that matters. Backed up nand twice over wrote the second time after failed ctr transfer so I think it's stuck at 2.1 brick. It never completed successfully before I reboot. Nand size checks out. It's a o3ds.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • BakerMan
    I rather enjoy a life of taking it easy. I haven't reached that life yet though.
    cearp @ cearp: and Psi - I had a cd player / radio that played mp3 cds once, very cool