Homebrew Official [Download] Decrypt9 - Open Source Decryption Tools (WIP)

[Shadowtrance]

Well you're welcome to make your own custom build, i don't see why you're asking here. Just go and do it for yourself if you're deadset on no screen init a9lh.

 

[Sniffynose]

Well you're welcome to make your own custom build, i don't see why you're asking here. Just go and do it for yourself if you're deadset on no screen init a9lh.

lol no worries, I was just wondering if anyone had made one up publicly before. I admit it's a rather backwards way of doing it haha but eh, I've made pretty much everything a bit unique so far might as well keep at it

 

[tivu100]

Run Decrypt9WIP-20160309-160637.zip build (bin for a9lh) and can't use restore NAND feature (both EMUNAND & NAND) on a9lh sysnand 9.2.

"Not a proper NAND backup for this 3DS!" , even with the the NAND.bin/EMUNAND.bin I just dump before I try to restore!

Boot using arm9select. Aureinand cfw 3.8.1 updatedsysnand mode

***Log: (I copied this before I tried back up sysNAND & tried restore the same sysNAND.bin, which gave the same error as those in this log) (Another note: EMUNAND is currently the unbricked EMUNAND 2.1 version)

Spoiler

"You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
NAND.bin
Opening NAND.bin ...
NAND CID: 3234C9CB8C0030454732303000011100
TWL Customer ID: 0167281B00000002
0x03 KeyX: B48E3FB24E494E54454E444FB567C208
0x03 KeyY: 76DCB90AD3C44DBD1DDD2D200500A0E1
0x05 KeyY: not set, slot0x05KeyY.bin not found
Not a proper NAND backup for this 3DS!
NAND Restore: failed!

Press B to return, START to reboot.

You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
NAND.bin
Opening NAND.bin ...
Not a proper NAND backup for this 3DS!
NAND Restore: failed!

Press B to return, START to reboot.

Unmounting SD card...

You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
NAND.bin
Opening NAND.bin ...
Not a proper NAND backup for this 3DS!
NAND Restore: failed!

Press B to return, START to reboot.

Using EmuNAND @ 3B0000/000000
Dumping EmuNAND. Size (MB): 1888
Use arrow keys and <A> to choose a name
emuNAND.bin
Creating emuNAND.bin ...
EmuNAND Backup: succeeded!

Press B to return, START to reboot.

You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
emuNAND.bin
Opening emuNAND.bin ...
NAND CID: 3234C9CB8C0030454732303000011100
TWL Customer ID: 0167281B00000002
0x03 KeyX: B48E3FB24E494E54454E444FB567C208
0x03 KeyY: 76DCB90AD3C44DBD1DDD2D200500A0E1
0x05 KeyY: not set, slot0x05KeyY.bin not found
Not a proper NAND backup for this 3DS!
NAND Restore: failed!

Press B to return, START to reboot.

You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
NAND.bin
Opening NAND.bin ...
Not a proper NAND backup for this 3DS!
NAND Restore: failed!

Press B to return, START to reboot.

You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
NAND.bin
Opening NAND.bin ...
NAND CID: 3234C9CB8C0030454732303000011100
TWL Customer ID: 0167281B00000002
0x03 KeyX: B48E3FB24E494E54454E444FB567C208
0x03 KeyY: 76DCB90AD3C44DBD1DDD2D200500A0E1
0x05 KeyY: not set, slot0x05KeyY.bin not found
Not a proper NAND backup for this 3DS!
NAND Restore: failed!

Press B to return, START to reboot.

You selected "EmuNAND Restore".
This feature writes to the EmuNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Using EmuNAND @ 3B0000/000000
Use arrow keys and <A> to choose a file
emuNAND.bin
Opening emuNAND.bin ...
Not a proper NAND backup for this 3DS!
EmuNAND Restore: failed!

Press B to return, START to reboot.

 

[Sniffynose]

I'll think about that (I even already have the code to do it), but to be honest, rather not.

It's all good, it would make everything redundant having to add the screen init sequence and it definitely makes sense why it's now included with the A9HL natively.

Keep up the good work!

 

[tivu100]

Please let me have a build with working restore NAND feature for a9lh, so I can restore my normal 9.2 NAND! I have some urgent thing to do!

Try this unofficial build

https://gbatemp.net/threads/downloa...yption-tools-wip.388831/page-132#post-6148899

Error: file too small!

***Log:

Spoiler

You selected "NAND Restore".
This feature writes to the SysNAND.
Doing this is potentially dangerous!

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

(B to return, START to reboot)

Use arrow keys and <A> to choose a file
NAND.bin
Opening NAND.bin ...
NAND CID: 3234C9CB8C0030454732303000011100
TWL Customer ID: 0167281B00000002
0x03 KeyX: B48E3FB24E494E54454E444FB567C208
0x03 KeyY: 76DCB90AD3C44DBD1DDD2D200500A0E1
0x05 KeyY: not set, slot0x05KeyY.bin not found
ERROR, file is too small!
NAND Restore: failed!

Press B to return, START to reboot.

 

[Nephiel]

Could this bit have something to do with that? (note: I honestly have no idea if that's the case)

0x05 KeyY: not set, slot0x05KeyY.bin not found

 

[tivu100]

Could this bit have something to do with that? (note: I honestly have no idea if that's the case)

I don't know what that is neither. I restored this same normal 9.2 NAND.bin just fine an hour ago using the OTPhelper NAND restore feature after dumping otp.bin. After installing a9lh, I can't go back to normal NAND

 

[Shadowtrance]

Yeah that key is NEEDED on n3ds from a9lh (not sure if o3ds needs it or not?).
As for the "file too small" i have no idea.

 

[tivu100]

Yeah that key is NEEDED on n3ds from a9lh (not sure if o3ds needs it or not?).
As for the "file too small" i have no idea.

Can you me info how to obtain that key( in case it helps solving this)?

Funny how I just dumped the sysNAND.bin, and restore it giving "file too small" error

 

[Shadowtrance]

google " sheets 3DS AES Keys " then look for the 0x05 one and copy/paste that into a new file in a hex editor and save it as slot0x05KeyY.bin

 

[d0k3]

Can you me info how to obtain that key( in case it helps solving this)?

Funny how I just dumped the sysNAND.bin, and restore it giving "file too small" error

The file too small error was a known bug before my last release. And Shadowtrance is right - that file is needed for a safety check of you NAND backup.

--------------------- MERGED ---------------------------

Ewww but it's so much nicer just leaving the screen blank until it loads into the CFW, it's pretty much true to the original like that >.<

I'll think about that (I even alreade have the code to do it), but to be honest, rather not.

 

[tivu100]

google " sheets 3DS AES Keys " then look for the 0x05 one and copy/paste that into a new file in a hex editor and save it as slot0x05KeyY.bin

The file too small error was a known bug before my last release. And Shadowtrance is right - that file is needed for a safety check of you NAND backup.

--------------------- MERGED ---------------------------


I'll think about that (I even alreade have the code to do it), but to be honest, rather not.

Okay getting slot0x05KeyY.bin let me restore the a9lh NAND.bin. Will wait for this to complete then try with the normal NAND.bin.

Can't this key not be able to be hardcoded into the app? (root of SD is kinda messy with all kind of files and folders)

 

[d0k3]

Okay getting slot0x05KeyY.bin let me restore the a9lh NAND.bin. Will wait for this to complete then try with the normal NAND.bin.

Can't this key not be able to be hardcoded into the app?

Keys are considered copyrighted stuff, so I'd rather not endanger the project with that. There are considerations to let the key initialization be handled by future versions of A9LH, though, so that would solve the problem as well.

 

[Shadowtrance]

Okay getting slot0x05KeyY.bin let me restore the a9lh NAND.bin. Will wait for this to complete then try with the normal NAND.bin.

Can't this key not be able to be hardcoded into the app? (root of SD is kinda messy with all kind of files and folders)

No, it can't. Because illegal. (apparently)

 

[tivu100]

Okay getting slot0x05KeyY.bin let me restore the a9lh NAND.bin. Will wait for this to complete then try with the normal NAND.bin.

Can't this key not be able to be hardcoded into the app? (root of SD is kinda messy with all kind of files and folders)

Being able to flashing regular NAND.bin now.

Keys are considered copyrighted stuff, so I'd rather not endanger the project with that. There are considerations to let the key initialization be handled by future versions of A9LH, though, so that would solve the problem as well.

No, it can't. Because illegal. (apparently)

Cheers for the info.

@d0k3 Getting lazy again to go to the OTPHELPER thread, so gonna ask here anyways. Can you consider adding flashing unbricked 2.1 EMUNAND straight into SYSNAND feature for private/testing version?

This is my 2nd OTP extracted attempt. First one using OTPhelper. After the success today. I would expect to have 3-6 3DS from friends lined up for the test. So that would save me a lot of time skipping the back up unbricked EMUNAND before flashing it to SYSNAND.

 

[d0k3]

Being able to flashing regular NAND.bin now.


Cheers for the info.

@d0k3 Getting lazy again to go to the OTPHELPER thread, so gonna ask here anyways. Can you consider adding flashing unbricked 2.1 EMUNAND straight into SYSNAND feature for private/testing version?

This is my 2nd OTP extracted attempt. First one using OTPhelper. After the success today. I would expect to have 3-6 3DS lined up for the test. So that would save me a lot of time skipping the back up unbricked EMUNAND before flashing it to SYSNAND.

If you are willing to test and investigate the reason behind those bricks, I'd be willing to do that. Won't work from A9LH, though. So...?

 

[tivu100]

If you are willing to test and investigate the reason behind those bricks, I'd be willing to do that. Won't work from A9LH, though. So...?

https://gbatemp.net/threads/am-i-screwed-black-screen-after-otp-on-n3ds.418106/page-4#post-6153834

I posted in that thread too. The suspect lies with the using of CakeCFW, where due to different of Cakes version (?), when the guide followers can't find the patches mentioned in the guide, they enabled different patches (!), which later led to different result than the guide expectation.

https://gbatemp.net/threads/am-i-screwed-black-screen-after-otp-on-n3ds.418106/page-3#post-6152277

I think going from Reinand cfw would be more simpler and safer. After getting on A9LH, then choosing between CFW flavour is no trouble.

Edit; Okay back to normal 9.2 SYSNAND safely.

Side Note: Spring break coming so I will have time to a9lhax my friend's 3DS. So definitely have to test with at least (3) 3DS. Another 3 are depended whether my friends vacation trip.

 

[jackb994]

Keys are considered copyrighted stuff, so I'd rather not endanger the project with that. There are considerations to let the key initialization be handled by future versions of A9LH, though, so that would solve the problem as well.

Couldn't you encrypt and hardcode them in like ReiNand did with the 9.6 keys

 

[Nephiel]

Can't this key not be able to be hardcoded into the app? (root of SD is kinda messy with all kind of files and folders)

I put all my slot***Key*.bin files inside a folder named Decrypt9. Should they be in the root?

 

[tivu100]

I put all my slot***Key*.bin files inside a folder named Decrypt9. Should they be in the root?

Not sure myself, so I just put it on root.