Homebrew Interesting...

[Unoalpho]

Either that or thats the ID keeping it from being played on another DSi
If it is couldn't we just take that code from one of our games copy it and paste it onto someone else's dsiware app to get it free?

But i doubt Nintendo would be so stupid.

I found that code thing a while ago tho but i assumed people already knew about it so i didn't do anything about it lol


Last time i looked at mine it was a couple of letter now its huge

EABKE6PKEQDKEUGKEFWKTFMKEYMKEGNHEMAKED4KEWUK
If you notice it says key right there QUOTE

EABKE6PKEQDKEUGKEFWKTFM(KEY)MKEGNHEMAKED4KEWUK

if you want to check yours open up in title from your SD Card HNB_.lst

what would happen if you deleted that code

 

[Supersonicmonk]

ZOMG USE FOND DA COMON KEY !!!

nah sorry to be the one to say this but if it was this easy to get free DSi Ware titles then some of the hacking teams would have done it ages ago. Still it looks interesting and maybe it could be usefull

 

[House Spider]

If they're Title IDs couldn't we hex edit the DSiWare we download to work on our DSi. [/sarcasm]

 

[Dead End]

I have a question i may aswell ask it here...

can we find anything in DSi Taken Pics???
use hex editor and explore them

This kinda ties in with another idea i had...
"""Use a DSi Taken picture and then make a copy/clone it and then edit the cloned one then undo then compare the cloned and original then change the necisarry Hex to get normal PC pics to work on the DSi...
(ill try it out next month when i get a DSi)"""

back on topic...

 

[Unoalpho]

Does the code get longer for every dsiware you download?

Edit:136 posts

 

[Hatsu]

Last time i looked at mine it was a couple of letter now its huge

EABKE6PKEQDKEUGKEFWKTFMKEYMKEGNHEMAKED4KEWUK
If you notice it says key right there QUOTEEABKE6PKEQDKEUGKEFWKTFM(KEY)MKEGNHEMAKED4KEWUK

if you want to check yours open up in title from your SD Card HNB_.lst

what would happen if you deleted that code? Nothing. The DSi would make another one.

That code is just something the DSi compiles every time you download some new DSiWare.
It is the DSi Title list. It has the title ID of every DSiWare on your DSi.


EDIT: 1550 posts.

 

[Van_Xan]

Ok me and my dad took a 45min drive to the Apple store to so I could clear my head, but all I could think about was the stupid DSi, so I told my dad the problem and he made some interesting points about what the big N could be doing to stop DSi from being hacked so I thought hard, took some pics for you guys and came to a conclusion...

Ok the top one is my bros Mario Calc DSiWare(the actual app, not the HNB_.lst), and the bottom is my Mario Calc DSiWare(the actual app, not the HNB_.lst), I have come to the conclusion that the DSi ether;

1) Encodes each file when it downloads it or
2) The server encodes each file right before you download it

If 1 is correct it meens it could encrypt each file using an algorithm(like DSi serial * predefined character set(1234567890ABCDEFG and so on) ÷ DSi freind code).
If 2 is correct it could be the same idea as 1.
Ether way its gonna be a uphill battle for DSi homebrew.

 

[Hatsu]

I would say the DSi encodes it right after download.

 

[Technik]

So does this man Van_Xan found something?

 

[Hatsu]

So does this man Van_Xan found something?

Not really. Most of us had known this already.

 

[stinkoman]

It's undoubtedly encrypted/hashed, possibly both, if it is anything at all. I'd look through it, and try switching the two files (The different DSis) and see if it still works. If it is, then it may just be checking for something in the DSi's memory, and matching the IDs to see if they line up, or it could use a different method of encryption every time, and checking to see if the encryption method matches. I don't know much about hacking, just a bit about how things on computers work, but I suppose anything could help.

 

[Hatsu]

chao1212's idea won't work.

What if we get the same DSiWare from two different DSi's, and change the Hex in one of them to the same as the other, and transfer to the DSi from where that Hex code came from.

As in:

1. Get the same DSiWare from two different DSi's. For this purpose, call one 1.bin and the other 2.bin (remembering the original names, they are needed later

)
2. Copy and paste all of the Hex from 1.bin to 2.bin
3. Rename 2.bin back to the original name, and put it on the DSi that 1.bin came from.

This might work.

 

[Van_Xan]

It would not work, but I tried it just in case(even tho it wouldn't work) and it didn't work.
Its's the same as copying the file from 1 DSi to the other without changing anything, sry.

 

[SifJar]

chao1212's idea won't work.

What if we get the same DSiWare from two different DSi's, and change the Hex in one of them to the same as the other, and transfer to the DSi from where that Hex code came from.

As in:

1. Get the same DSiWare from two different DSi's. For this purpose, call one 1.bin and the other 2.bin (remembering the original names, they are needed later

)
2. Copy and paste all of the Hex from 1.bin to 2.bin
3. Rename 2.bin back to the original name, and put it on the DSi that 1.bin came from.

This might work.

That's just putting 1.bin back on the original DSi it came from.

Anyway, I'm pretty sure that all content is signed with the DSi's individual key as it is installed, so will only work with one particular DSi. AFAIK, this is what happens on Wii.

 

[Demonbart]

Anyway, I'm pretty sure that all content is signed with the DSi's individual key as it is installed, so will only work with one particular DSi. AFAIK, this is what happens on Wii.

Well they got it to work on the wii, so it should be possible to pull it off on the dsi if it works the same way.

 

[House Spider]

If they worked the same way, the DSi would be HBC'd by now.

 

[azure0wind]

hmm...
so it doesn't work?

 

[Destructobot]

Every DS has a unique ID of some sort. That's how it generates a unique friend code for the games that use them. I'm almost certain that the DSi has expanded this to include a unique public key (remember, every DS has the RSA SECURED logo on it) that lets the server (and more importantly, not the DS) encrypt the DSiware data before it sends it to you.

The DSi will have to be cracked and the encryption broken before you can transfer DSiware from one system to another or run homebrew as DSiware.

 

[starfighter1]

so really what have we even acomplished it seems like we have not even gotten from square one yet.

 

[Van_Xan]

so really what have we even acomplished it seems like we have not even gotten from square one yet.
Why dont you read this first before you post;
QUOTE(Van_Xan @ Jan 16 2010, 09:09 PM) Ok me and my dad took a 45min drive to the Apple store to so I could clear my head, but all I could think about was the stupid DSi, so I told my dad the problem and he made some interesting points about what the big N could be doing to stop DSi from being hacked so I thought hard, took some pics for you guys and came to a conclusion...

Ok the top one is my bros Mario Calc DSiWare(the actual app, not the HNB_.lst), and the bottom is my Mario Calc DSiWare(the actual app, not the HNB_.lst), I have come to the conclusion that the DSi ether;

1) Encodes each file when it downloads it or
2) The server encodes each file right before you download it

If 1 is correct it meens it could encrypt each file using an algorithm(like DSi serial * predefined character set(1234567890ABCDEFG and so on) ÷ DSi freind code).
If 2 is correct it could be the same idea as 1.
Ether way its gonna be a uphill battle for DSi homebrew.