Hacking I think my n3ds is bricked

bandar

Well-Known Member
OP
Newcomer
Joined
Jan 27, 2017
Messages
85
Trophies
0
Age
29
XP
281
Country
Saudi Arabia
So, I have this problem. The device is New 3ds xl USA This is my 3rd 3ds to hack and everything was going well until step 10 I find out that the nand backup was corrupt! So I decided to restore it to 9.2.0 but I keep getting auto ctrnand transfer failed at step 3. I'm sure that I picked up the correct version but no luck. tried to restore the old 3ds version and the installation is successful but when I start the 3ds I get failed to mount CTRNAND error. Tried to google it but every solution I found was with the nand pack up which is unfortunately corrupt. Help :(
Forgot to say I have full acess to Decrypt9WIP and Hourglass9 in the device
 
Last edited by bandar,

HyperT

Well-Known Member
Member
Joined
Jun 4, 2016
Messages
674
Trophies
0
XP
232
Country
Is there a decrypt9.log in files9 folder that you can post?

You didn't flash a o3ds nand [as mentioned above]; just the o3ds 2.1 ctrnand again right?
 

bandar

Well-Known Member
OP
Newcomer
Joined
Jan 27, 2017
Messages
85
Trophies
0
Age
29
XP
281
Country
Saudi Arabia
Is there a decrypt9.log in files9 folder that you can post?

You didn't flash a o3ds nand [as mentioned above]; just the o3ds 2.1 ctrnand again right?


Selected: [Auto CTRNAND Transfer]
Select CTRNAND transfer image
Use arrow keys and <A> to choose a file
9.2.0-20U_ctrtransfer_n3ds.bin
Image size is: 1106051072 byte

Step #0: Optional NAND backup
Press <B> to skip and continue without backup
Dumping SysNAND. Size (MB): 1240
Use arrow keys and <A> to choose a name
(cancelled by user)

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 0B9D0000, size 273b
Creating A4AF62C8_SecureInfo_A ...
Searching for movable.sed...
Found at 0B9BC000, size 320b
Creating A4AF62C8_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9CC000, size 272b
Creating A4AF62C8_LocalFriendCodeSeed_B ...
Searching for configsave.bin...
Found at 0E2B8000, size 256kB
Creating A4AF62C8_configsave.bin ...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Switching out NAND header first...
NAND header is corrupt or from another 3DS
Genuine header backup not found
Auto CTRNAND Transfer: failed!

Press B to return, START to reboot.


Try using a different SD card and do another 9.2 ctr transfer, maybe your SD is corrupted or faulty

I'm now downloading it again and will see if it will work with a different sd card
 

ItsKipz

l33t hax0r
Member
Joined
Sep 9, 2016
Messages
1,930
Trophies
0
Location
The C: drive
XP
1,625
Country
United States
Selected: [Auto CTRNAND Transfer]
Select CTRNAND transfer image
Use arrow keys and <A> to choose a file
9.2.0-20U_ctrtransfer_n3ds.bin
Image size is: 1106051072 byte

Step #0: Optional NAND backup
Press <B> to skip and continue without backup
Dumping SysNAND. Size (MB): 1240
Use arrow keys and <A> to choose a name
(cancelled by user)

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 0B9D0000, size 273b
Creating A4AF62C8_SecureInfo_A ...
Searching for movable.sed...
Found at 0B9BC000, size 320b
Creating A4AF62C8_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9CC000, size 272b
Creating A4AF62C8_LocalFriendCodeSeed_B ...
Searching for configsave.bin...
Found at 0E2B8000, size 256kB
Creating A4AF62C8_configsave.bin ...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Switching out NAND header first...
NAND header is corrupt or from another 3DS
Genuine header backup not found
Auto CTRNAND Transfer: failed!

Press B to return, START to reboot.




I'm now downloading it again and will see if it will work with a different sd card
did you follow ALL of https://3ds.guide/9.2.0-ctrtransfer?
 

HyperT

Well-Known Member
Member
Joined
Jun 4, 2016
Messages
674
Trophies
0
XP
232
Country
Selected: [Auto CTRNAND Transfer]
Select CTRNAND transfer image
Use arrow keys and <A> to choose a file
9.2.0-20U_ctrtransfer_n3ds.bin
Image size is: 1106051072 byte

Step #0: Optional NAND backup
Press <B> to skip and continue without backup
Dumping SysNAND. Size (MB): 1240
Use arrow keys and <A> to choose a name
(cancelled by user)

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 0B9D0000, size 273b
Creating A4AF62C8_SecureInfo_A ...
Searching for movable.sed...
Found at 0B9BC000, size 320b
Creating A4AF62C8_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9CC000, size 272b
Creating A4AF62C8_LocalFriendCodeSeed_B ...
Searching for configsave.bin...
Found at 0E2B8000, size 256kB
Creating A4AF62C8_configsave.bin ...
Step #2 success!

Step #3: Injecting CTRNAND transfer image
Switching out NAND header first...
NAND header is corrupt or from another 3DS
Genuine header backup not found
Auto CTRNAND Transfer: failed!

Press B to return, START to reboot.




I'm now downloading it again and will see if it will work with a different sd card
Well at least you know the issue is with rhe nand header - see if there's a nandhead.bin [or similar] in files9 folder if not look in decrypt9 for the dump nand header option.
From there you probably need a dev's input to figure out what went wrong and if/how to proceed.

Reflashing 2.1 ctrnand doesn't error out right? Can you post its log
 

bandar

Well-Known Member
OP
Newcomer
Joined
Jan 27, 2017
Messages
85
Trophies
0
Age
29
XP
281
Country
Saudi Arabia
Well at least you know the issue is with rhe nand header - see if there's a nandhead.bin [or similar] in files9 folder if not look in decrypt9 for the dump nand header option.
From there you probably need a dev's input to figure out what went wrong and if/how to proceed.

Reflashing 2.1 ctrnand doesn't error out right? Can you post its log

There is no nandhead.bin but I just dumped it from decrypt9 and it's named NAND_hdr.bin

and how to do the dev's input?

and yeah whenever I do 2.1 it's successful.

Here's the log for 2.1

Selected: [Auto CTRNAND Transfer]
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): 1240
Use arrow keys and <A> to choose a name
(cancelled by user)

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 A4AF62C8_SecureInfo_A ...
Searching for movable.sed...
Found at 13A14000, size 320b
Creating A4AF62C8_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Creating A4AF62C8_LocalFriendCodeSeed_B ...
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Creating A4AF62C8_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 A4AF62C8_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 A4AF62C8_movable.sed ...
Fixing file CMAC for console...
Searching for movable.sed...
Found at 13A14000, size 320b
Validated CMAC okay
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening A4AF62C8_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 A4AF62C8_configsave.bin ...
Fixing file CMAC for console...
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
0x30 KeyY: set up from NAND
Validated CMAC okay
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
0x30 KeyY: set up from NAND
Validated CMAC okay
Step #5 success!

Auto CTRNAND Transfer: succeeded!
 
Last edited by bandar,

HyperT

Well-Known Member
Member
Joined
Jun 4, 2016
Messages
674
Trophies
0
XP
232
Country
There is no nandhead.bin but I just dumped it from decrypt9 and it's named NAND_hdr.bin

and how to do the dev's input?

and yeah whenever I do 2.1 it's successful.

Here's the log for 2.1

Selected: [Auto CTRNAND Transfer]
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): 1240
Use arrow keys and <A> to choose a name
(cancelled by user)

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 A4AF62C8_SecureInfo_A ...
Searching for movable.sed...
Found at 13A14000, size 320b
Creating A4AF62C8_movable.sed ...
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Creating A4AF62C8_LocalFriendCodeSeed_B ...
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
Creating A4AF62C8_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 A4AF62C8_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 A4AF62C8_movable.sed ...
Fixing file CMAC for console...
Searching for movable.sed...
Found at 13A14000, size 320b
Validated CMAC okay
Searching for LocalFriendCodeSeed_B...
Found at 0B9BC000, size 272b
Opening A4AF62C8_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 A4AF62C8_configsave.bin ...
Fixing file CMAC for console...
Searching for configsave.bin...
Found at 0E1C0000, size 256kB
CMAC id: 00010017
0x30 KeyY: set up from NAND
Validated CMAC okay
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
0x30 KeyY: set up from NAND
Validated CMAC okay
Step #5 success!

Auto CTRNAND Transfer: succeeded!
Have you tried with both decrypt9 and hg9?

Not sure if this is relevent: https://github.com/d0k3/Decrypt9WIP/issues/94
 
Last edited by HyperT,

bandar

Well-Known Member
OP
Newcomer
Joined
Jan 27, 2017
Messages
85
Trophies
0
Age
29
XP
281
Country
Saudi Arabia
Have you tried with both decrypt9 and hg9?

Not sure if this is relevent: https://github.com/d0k3/Decrypt9WIP/issues/94

I saw this earlier and it sounds like the same issue I have except he has it with the 2.1.0

Is it possible to do Auto CTRNAND Transfer with hq9? because as I said earlier nand back up is corrupt and tried it with both and they have the same error with the nand back up.

Now I'm stuck with the device and it has A9LH but no nand back up and 9.2.0-20U_ctrtransfer_n3ds.bin not working at all (see above)

And btw I tried 9.2.0-20E_ctrtransfer_n3ds.bin just to see if this will help but nope I'm still getting the same error

And btw is trying a nand back up from a differant 3ds going to make a problem or should I give it a shot?
 
Last edited by bandar,

Distrance

矢澤にこ
Member
Joined
Nov 23, 2008
Messages
1,151
Trophies
1
XP
800
Country
Finland
If restoring a backup from a different 3DS was possible do you really think anyone would ever be bricked if they had A9LH installed? Why would you even think that doing such a thing is okay? NAND is console specific .. Do that and you have a paperweight and nothing more.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Psionic Roshambo @ Psionic Roshambo: In the end that call ended up costing Dell millions in lost contracts with Raytheon, and really...