Homebrew DSi Homebrew Channel (IDEA)

  • Thread starter Thread starter desumodnoc
  • Start date Start date
  • Views Views 222,152
  • Replies Replies 735
Status
Not open for further replies.
king i read ur explanation.
I don't agree with you in that, sure a DS game needs to save to a DS cart, but the SD can take its place.
GB games and SNES games are not Slot-1 games but since they are being run from Slot-1 they will save there. Just hope the DSi scene goes as great as the PSP's, custom firmwares and all.
 
Uruha said:
king i read ur explanation.
I don't agree with you in that, sure a DS game needs to save to a DS cart, but the SD can take its place.
GB games and SNES games are not Slot-1 games but since they are being run from Slot-1 they will save there. Just hope the DSi scene goes as great as the PSP's, custom firmwares and all.

Thats realy a dumbed down explanation, if you think about it. If the DSi isn't coded to be able to read .nds roms off the SD card, then without severe modification (someone hard-coding it in), it wouldn't work. It wouldn't be something simple like the PSP which was originally already able to play games off the Pro Duo.
 
Kingfield said:
Uruha said:
king i read ur explanation.
I don't agree with you in that, sure a DS game needs to save to a DS cart, but the SD can take its place.
GB games and SNES games are not Slot-1 games but since they are being run from Slot-1 they will save there. Just hope the DSi scene goes as great as the PSP's, custom firmwares and all.

Thats realy a dumbed down explanation, if you think about it. If the DSi isn't coded to be able to read .nds roms off the SD card, then without severe modification (someone hard-coding it in), it wouldn't work. It wouldn't be something simple like the PSP which was originally already able to play games off the Pro Duo.

The DSi can read whatever data is on the SD card, but the trick is telling the DSi what to do with it. For example, if I put a .iso file containing the image for Phantasy Star Portable on the SD in a DSi, it'll look at the data and not tell the user about it, because its told to ignore such data when telling the user about what is on the card. If the software on the DSi is modified to interpret the data (i.e. custom firmware, loader, etc.), the DSi will process the data and return meaningful output. The DSi can't be hard-coded to ignore files of certain extension type, because it has no understanding of extension without software. Thus, by totally replacing the software, we can use the hardware known as the DSi to do whatever we want with whatever data we want, once we find out how to use the software currently installed on the hardware to gain direct access to the hardware.

This is how the PSP cfw deal works - by finding a kernel-level exploit, we can tell the software currently installed to do certain things that result in a new software being installed. This new software, which happens to retain all the functionality and looks of the old software, can do things like display information for binary data in an .iso wrapper, and interpret data found within those .isos.
 
omatic said:
Kingfield said:
Uruha said:
king i read ur explanation.
I don't agree with you in that, sure a DS game needs to save to a DS cart, but the SD can take its place.
GB games and SNES games are not Slot-1 games but since they are being run from Slot-1 they will save there. Just hope the DSi scene goes as great as the PSP's, custom firmwares and all.

Thats realy a dumbed down explanation, if you think about it. If the DSi isn't coded to be able to read .nds roms off the SD card, then without severe modification (someone hard-coding it in), it wouldn't work. It wouldn't be something simple like the PSP which was originally already able to play games off the Pro Duo.

The DSi can read whatever data is on the SD card, but the trick is telling the DSi what to do with it. For example, if I put a .iso file containing the image for Phantasy Star Portable on the SD in a DSi, it'll look at the data and not tell the user about it, because its told to ignore such data when telling the user about what is on the card. If the software on the DSi is modified to interpret the data (i.e. custom firmware, loader, etc.), the DSi will process the data and return meaningful output. The DSi can't be hard-coded to ignore files of certain extension type, because it has no understanding of extension without software. Thus, by totally replacing the software, we can use the hardware known as the DSi to do whatever we want with whatever data we want, once we find out how to use the software currently installed on the hardware to gain direct access to the hardware.

This is how the PSP cfw deal works - by finding a kernel-level exploit, we can tell the software currently installed to do certain things that result in a new software being installed. This new software, which happens to retain all the functionality and looks of the old software, can do things like display information for binary data in an .iso wrapper, and interpret data found within those .isos.

you're practically expanding on what i said, I think you didnt read what I said clearly.
 
Can't just Yasu write here and proudly say that he's hacked it...
And ofcourse a download link to his homebrew channel..
Huhmmm...... Dreams....
sleep.gif
 
Yasu didn't make a homebrew channel, he found an exploit in the dsi that he has yet to share, and can likely only run in compatibility mode
 
its funny how this is the first nintendo device where we cant access naitve mode(dsi), but can full access the "older" version (ds)
 
jan777 said:
its funny how this is the first nintendo device where we cant access naitve mode(dsi), but can full access the "older" version (ds)

When the Wii was first hacked only Gamecube mode was available, it took a while before there was full access to all the Wii hardware.
 
darkriku2000 said:
Yasu didn't make a homebrew channel, he found an exploit in the dsi that he has yet to share, and can likely only run in compatibility mode

therefore making the exploit almost useless (unless from the exploit he can manage to get the DSi to reboot into DSi mode or something).

anyways afaik, someone has already found the common key and is now studying what he can find.
 
Well, Anything new? Or did you just drop the whole project.
 
TrolleyDave said:
jan777 said:
its funny how this is the first nintendo device where we cant access naitve mode(dsi), but can full access the "older" version (ds)

When the Wii was first hacked only Gamecube mode was available, it took a while before there was full access to all the Wii hardware.
And when the DS first came out, we had full access to GBA mode but no way to boot homebrew code in DS mode until the PassMe was created. And when the GBA first came out, the existing GB/GBC flash carts worked fine but it took a while for GBA-specific flash carts to come out.
 
DanTheManMS said:
TrolleyDave said:
jan777 said:
its funny how this is the first nintendo device where we cant access naitve mode(dsi), but can full access the "older" version (ds)

When the Wii was first hacked only Gamecube mode was available, it took a while before there was full access to all the Wii hardware.
And when the DS first came out, we had full access to GBA mode but no way to boot homebrew code in DS mode until the PassMe was created. And when the GBA first came out, the existing GB/GBC flash carts worked fine but it took a while for GBA-specific flash carts to come out.

lol of course!
 
oh yeah i forgot..

well i stand corrected

i only though about the current situation..and not the early days..

figures.. i started here a gbatemp when the r4 was the best and the twilight hack was new
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum