Search results

  1. T

    Homebrew [indev] TreeHome - custom home menu template

    Would it be possible to create a home menu that automatically launches NTR? That might be interesting. Though BootNTR seems to rely on the home menu version/data to launch it, so I'm not sure. Another thought, could custom home menus could be installed as the test menu, so as to retain the...
  2. T

    Homebrew BASICsploit not running properly

    You probably missed typing one or more of the DATA numbers.
  3. T

    Tutorial Play with your Gamecube Controller in your 3DS (without hardmod)

    I'd suggest using the NTR version, as the cia you have to install for that has a different unique id that doesn't conflict with Persona Q.
  4. T

    Tutorial Play with your Gamecube Controller in your 3DS (without hardmod)

    Because smash reboots o3DSs, it won't work with smash on an o3DS.
  5. T

    Homebrew Basicsploit doesn't work

    Well, it is called "Petit Modem." It transfers the data over sound waves.
  6. T

    Homebrew [Release] BASICSploit - Primary homebrew exploit for SmileBASIC

    "Syntax error in 0:8" means that you typed something wrong on line 8. In this case you typed an O(letter) instead of a zero. Notice how every number in the DATA is highlighted except where you typed O?
  7. T

    Homebrew SmashHax ssb4 v 1.1.6

    You don't even have an option to delete the save as far as I know; the options when using an older version of smash than your save are to continue without saving or exit the game.
  8. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    Oh, sorry, I thought you meant Smash v1.1.3.
  9. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    You could just rename the update data on your SD card. But I'm not sure if that works on the digital version.
  10. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    Don't forget about Smashhax! I'm pretty sure it's still a thing.
  11. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    BGSCREEN isn't at all what can attack TWL_FIRM because it simply doesn't exist in Petit Computer.
  12. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    Before getting horribly off-topic, keep in mind that nobody has actually found an exploit in Petit Computer.
  13. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    I don't think there's any possibility of Petit Computer being similarly exploitable. It doesn't have resizable background layers like SmileBASIC does, and so BGSREEN doesn't even exist there.
  14. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    Yep. Those are some of the function names. I also linked an editor on the first page; if you want to use it, inject the file into your extdata.
  15. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    It did work, but you can't see what it did because you didn't offset the layer. Try these inputs: XSCREEN 2 BGSCREEN 0,134217728,16 BGOFS 0,6400*16,0 That sets the screen up, sets the glitch up, and then shows you an interesting bit. You can try other offsets in the third command if you want to...
  16. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    The only interesting portion that I know of starts at 0x08812FEC. This is where all the functions, variables, labels, and string values seem to be stored, along with any information associated with them, like lengths and what I assume are pointers. Both pointers and lengths are signed 32-bit...
  17. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    Using NTR Debugger, I found that the accessible memory with this glitch extends from 0x087E8CEC to 0x0CAF8D20 in process 0x29. Does that help in any way?
  18. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    I see no reason it wouldn't be, but I'm not sure as I don't own the Japanese version. It would be simple to try, though.
  19. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    The glitch makes the background layer data extend into the rest of the RAM, so simply triggering it and offsetting the background layer is enough to view the RAM. The data can also be retrieved with the BGGET command.
  20. T

    Homebrew RAM editing glitch on any 3DS, might lead to an exploit?

    BGGET can be used to get the two bytes at each tile and BGPUT can be used to write a new value. RAM editors have already been made, but aren't on the SmileBASIC servers for secrecy. One can be downloaded here and injected into your extdata to be used.