Hacking Old 3ds device Demo

[CrispyYoshi]

guys working dec9 working

what's next ?

what are we doing ?

Fantastic! (Can I ask how you got it working?)

Now, you should select SysNand Options->Sysnand Backup/Restore->Back up SysNand to SysNand.bin
Additionally, you should try to dump your Xorpads. Try to dump all of them!

 

[enes eyibil]

Fantastic! (Can I ask how you got it working?)

Now, you should select SysNand Options->Sysnand Backup/Restore->Back up SysNand to SysNand.bin
Additionally, you should try to dump your Xorpads. Try to dump all of them!

bo usable file found

nand restore failed

 

[CrispyYoshi]

bo usable file found

nand restore failed

WAIT WAIT YOU NAND RESTORED? NO NO, NAND BACKUP....

Absolutely do not reboot right now. Back up your XORPADs.

 

[enes eyibil]

WAIT WAIT YOU NAND RESTORED? NO NO, NAND BACKUP....

Absolutely do not reboot right now. Back up your XORPADs.

oeky sysnand bin ok

what's next ?

what are we doing ?

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

sysnand 976 mb

 

[CrispyYoshi]

oeky sysnand bin ok

what's next ?

what are we doing ?

On the main menu of Decrypt9WIP, select XORpad Generator Options. Then, select "CTRPADGen" and let it dump nand.fat16.xorpad

sysnand 976 mb <- It is possible your 6.x update gave you a valid NAND dump. However, I do not know if I trust it just yet. Do not reboot or you may brick your system. Keep your system powered on, dump your nand.fat16.xorpad, and send me both files:

SysNand.bin
nand.fat16.xorpad

After you dump the files, you can press Select to Unmount the SD card. However, do not turn off the system.

 

[enes eyibil]

ok nand.fat16.xorpad 750 mb

next ?

On the main menu of Decrypt9WIP, select XORpad Generator Options. Then, select "CTRPADGen" and let it dump nand.fat16.xorpad

sysnand 976 mb <- It is possible your 6.x update gave you a valid NAND dump. However, I do not know if I trust it just yet. Do not reboot or you may brick your system. Keep your system powered on, dump your nand.fat16.xorpad, and send me both files:

SysNand.bin
nand.fat16.xorpad

After you dump the files, you can press Select to Unmount the SD card. However, do not turn off the system.

 

[CrispyYoshi]

ok nand.fat16.xorpad 750 mb

next ?

Perfect! Keep your system on, press B, then Select to unmount your SD card. Then, upload the two files (nand.fat16.xorpad and SysNand.bin) and share them with me in a private conversation.

While they are uploading, can you try to dump these too?
- TWLNAND Padgen
- FIRM0FIRM1 Padgen

That will give you:
- twlnand.fat16.xorpad
- firm0firm1.xorpad

 

[Zenior_X]

So we've lost a 1.0 o3ds demo? Is there a way to get it back to the originl version?

 

[CrispyYoshi]

So we've lost a 1.0 o3ds demo? Is there a way to get it back to the originl version?

It's possible and we're about to attempt to recover it. We have a NAND.img from before updating the system to 6.x as well as a nand.fat16.xorpad (basically, the console-specific password to unzip/Decrypt the NAND.img archive)

However, the NAND.img dump from 1.0 is a rather interesting filesize of 792,606,208 bytes. It might or might not be a valid dump, but as soon as I get ahold of nand.fat16.xorpad from this user I can take a look at the 1.0 and 6.x NAND dump internals, based off information d0k3 gave me earlier in this thread.

We haven't bricked yet, but we're treading on a thin line right now. We could probably easily get out of this situation with a hardmod, though.

 

[enes eyibil]

It's possible and we're about to attempt to recover it. We have a NAND.img from before updating the system to 6.x as well as a nand.fat16.xorpad (basically, the console-specific password to unzip/Decrypt the NAND.img archive)

However, the NAND.img dump from 1.0 is a rather interesting filesize of 792,606,208 bytes. It might or might not be a valid dump, but as soon as I get ahold of nand.fat16.xorpad from this user I can take a look at the 1.0 and 6.x NAND dump internals, based off information d0k3 gave me earlier in this thread.

We haven't bricked yet, but we're treading on a thin line right now. We could probably easily get out of this situation with a hardmod, though.

what is the next step?

 

[Zenior_X]

It's possible and we're about to attempt to recover it. We have a NAND.img from before updating the system to 6.x as well as a nand.fat16.xorpad (basically, the console-specific password to unzip the NAND.img archive)

However, the NAND.img dump from 1.0 is a rather interesting filesize of 792,606,208 bytes. It might or might not be a valid dump, but as soon as I get ahold of nand.fat16.xorpad from this user I can take a look at the 1.0 and 6.x NAND dump internals, based off information d0k3 gave me earlier in this thread.

We haven't bricked yet, but we're treading on a thin line right now. We could probably easily get out of this situation with a hardmod, though.

A harmod would be ideal if he had the right skills tought the true problem it is langauge, which is a pity.

 

[d0k3]

Perfect! Keep your system on, press B, then Select to unmount your SD card. Then, upload the two files (nand.fat16.xorpad and SysNand.bin) and share them with me in a private conversation.

While they are uploading, can you try to dump these too?
- TWLNAND Padgen
- FIRM0FIRM1 Padgen

That will give you:
- twlnand.fat16.xorpad
- firm0firm1.xorpad

Maybe it would be a good idea to also put the system on a charger. @CrispyYoshi - if 3DSFAT16tool (mine, not Cearps) does not work on the first try, try padding the NAND image before using it. The correct size is the one of enes eybils last NAND backup.

 

[CrispyYoshi]

what is the next step?

I've sent you a private message, but at this point all we can do is dump those files, keep the system on, and you should send those 4 files to me so I can look at the internals of your two NAND dumps. Once I know a bit more about your NAND, we can (loosely) predict what will happen if you flash the NAND back onto the system. This might or might not brick you, but at this point I don't think we can try anything else: We have a potentially-valid/invalid 1.0.0U Demo dump, a (probably) valid 6.x NAND dump, and your Xorpads in case we need to do further testing. If you brick, you will need a hardmod, though, and I think we'll have to find you someone who can help you with that if it comes to that. (I certainly hope we don't have to do that, but as long as that 1.0.0 NAND dump is valid, I don't think we've lost anything permanently.)

A harmod would be ideal if he had the right skills tought the true problem it is langauge, which is a pity.

That's true, although I am more concerned about the fact they updated their system to 6.x using Pokemon Y: If that 1.0.0U NAND dump is invalid, we may have lost some valuable information for good...

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

Maybe it would be a good idea to also put the system on a charger. @CrispyYoshi - if 3DSFAT16tool (mine, not Cearps) does not work on the first try, try padding the NAND image before using it. The correct size is the one of enes eybils last NAND backup.

I'll give it a shot, then. However, if you're referring to the 6.x dump, take note that they dumped that after they posted "nand restore failed"

 

[Zenior_X]

I've sent you a private message, but at this point all we can do is dump those files, keep the system on, and you should send those 4 files to me so I can look at the internals of your two NAND dumps. Once I know a bit more about your NAND, we can (loosely) predict what will happen if you flash the NAND back onto the system. This might or might not brick you, but at this point I don't think we can try anything else: We have a potentially-valid/invalid 1.0.0U Demo dump, a (probably) valid 6.x NAND dump, and your Xorpads in case we need to do further testing. If you brick, you will need a hardmod, though, and I think we'll have to find you someone who can help you with that if it comes to that. (I certainly hope we don't have to do that, but as long as that 1.0.0 NAND dump is valid, I don't think we've lost anything permanently.)


That's true, although I am more concerned about the fact they updated their system to 6.x using Pokemon Y: If that 1.0.0U NAND dump is invalid, we may have lost some valuable information for good...

I know, when I saw the thread I couldn't believed but the shit happened...

 

[Urbanshadow]

That's true, although I am more concerned about the fact they updated their system to 6.x using Pokemon Y: If that 1.0.0U NAND dump is invalid, we may have lost some valuable information for good...

Care to pass on the fat16 xorpads once done? Already grabbed the 1.0 image. Let's see where this leads to.

 

[CrispyYoshi]

Care to pass on the fat16 xorpads once done? Already grabbed the 1.0 image. Let's see where this leads to.

I think it would be good to get more people to verify this, so sure. I'll share it as soon as I get ahold of it. You don't mind me sharing these files, do you @enes eyibil?

At this rate, it seems the 2GB of information might take a very long time to upload (I guess they just have really slow internet speed). I'll message you if everything goes as planned, but I would estimate another 8 hours before we can get it.

 

[enes eyibil]

2GB file ends in 8 hours

it's loading so slow

damn

I think it would be good to get more people to verify this, so sure. I'll share it as soon as I get ahold of it. You don't mind me sharing these files, do you @enes eyibil?

At this rate, it seems the 2GB of information might take a very long time to upload (I guess they just have really slow internet speed). I'll message you if everything goes as planned, but I would estimate another 8 hours before we can get it.

after you install the files, want to share it with everyone ?

 

[CrispyYoshi]

after you install the files, want to share it with everyone ?

Yes, I want to share the information on that demo unit with some experienced folks. I do not think we should post it publicly, though, because it probably contains sensitive information we do not want Nintendo to see.

Is that okay with you? Do not post it in this public thread, though!

 

[Urbanshadow]

Yes, I want to share the information on that demo unit with some experienced folks. I do not think we should post it publicly, though, because it probably contains sensitive information we do not want Nintendo to see.

Is that okay with you? Do not post it in this public thread, though!

Ofc, I always meant by private message. I would be very surprised if it is a valid image after all.

 

[enes eyibil]

Yes, I want to share the information on that demo unit with some experienced folks. I do not think we should post it publicly, though, because it probably contains sensitive information we do not want Nintendo to see.

Is that okay with you? Do not post it in this public thread, though!

will they arrest me ? ))