Hacking DSBricker and 4.0.0-7U update

  • Thread starter Thread starter Sicklyboy
  • Start date Start date
  • Views Views 13,984
  • Replies Replies 52
Not experienced in any form of hacking/coding, but if a bricker can write 0 over everything, why can't it write something else?

Because to the best of everyone's understanding, the DS Bios is sandboxed. So you might -potentially- be able to do something in DS mode, but that would probably be of little use in 3DS mode.
No, but that seems like it would help us dump DSiWare or something. DS st00f without the need for a flashcart..
After the first time, anyway.

But IIRC, DS mode and DSi mode are sandboxed seperately, unless I'm missing something.

Still, with something like an iEvo (LOLOLOL) or a DSi-only/enhanced game... Who knows?
Then using a DS mode bricker shouldn't be able to stop DSiWare, no?
 
Not experienced in any form of hacking/coding, but if a bricker can write 0 over everything, why can't it write something else?

Because to the best of everyone's understanding, the DS Bios is sandboxed. So you might -potentially- be able to do something in DS mode, but that would probably be of little use in 3DS mode.
No, but that seems like it would help us dump DSiWare or something. DS st00f without the need for a flashcart..
After the first time, anyway.

But IIRC, DS mode and DSi mode are sandboxed seperately, unless I'm missing something.

Still, with something like an iEvo (LOLOLOL) or a DSi-only/enhanced game... Who knows?
Then using a DS mode bricker shouldn't be able to stop DSiWare, no?
DS Mode brickers have no effect whatsover on a DSi, and I doubt it would on a 3DS.
 
Not experienced in any form of hacking/coding, but if a bricker can write 0 over everything, why can't it write something else?

Because to the best of everyone's understanding, the DS Bios is sandboxed. So you might -potentially- be able to do something in DS mode, but that would probably be of little use in 3DS mode.
No, but that seems like it would help us dump DSiWare or something. DS st00f without the need for a flashcart..
After the first time, anyway.

But IIRC, DS mode and DSi mode are sandboxed seperately, unless I'm missing something.

Still, with something like an iEvo (LOLOLOL) or a DSi-only/enhanced game... Who knows?
Then using a DS mode bricker shouldn't be able to stop DSiWare, no?
DS Mode brickers have no effect whatsover on a DSi, and I doubt it would on a 3DS.
I think you are misunderstanding the entire thread. If you use a DS mode bricker on a 3DS, it bricks DS mode.
That includes DSiWare.
 
  • Like
Reactions: 2 people
Not experienced in any form of hacking/coding, but if a bricker can write 0 over everything, why can't it write something else?

Because to the best of everyone's understanding, the DS Bios is sandboxed. So you might -potentially- be able to do something in DS mode, but that would probably be of little use in 3DS mode.
No, but that seems like it would help us dump DSiWare or something. DS st00f without the need for a flashcart..
After the first time, anyway.

But IIRC, DS mode and DSi mode are sandboxed seperately, unless I'm missing something.

Still, with something like an iEvo (LOLOLOL) or a DSi-only/enhanced game... Who knows?
Then using a DS mode bricker shouldn't be able to stop DSiWare, no?
DS Mode brickers have no effect whatsover on a DSi, and I doubt it would on a 3DS.
I think you are misunderstanding the entire thread. If you use a DS mode bricker on a 3DS, it bricks DS mode.
That includes DSiWare.

but unless it's running in DSi mode, it doesn't have any effect on DSiware, does it?
 
Not experienced in any form of hacking/coding, but if a bricker can write 0 over everything, why can't it write something else?

Because to the best of everyone's understanding, the DS Bios is sandboxed. So you might -potentially- be able to do something in DS mode, but that would probably be of little use in 3DS mode.
No, but that seems like it would help us dump DSiWare or something. DS st00f without the need for a flashcart..
After the first time, anyway.

But IIRC, DS mode and DSi mode are sandboxed seperately, unless I'm missing something.

Still, with something like an iEvo (LOLOLOL) or a DSi-only/enhanced game... Who knows?
Then using a DS mode bricker shouldn't be able to stop DSiWare, no?
DS Mode brickers have no effect whatsover on a DSi, and I doubt it would on a 3DS.
I think you are misunderstanding the entire thread. If you use a DS mode bricker on a 3DS, it bricks DS mode.
That includes DSiWare.

but unless it's running in DSi mode, it doesn't have any effect on DSiware, does it?

That's the point. On a 3DS, DSBricker also bricks DSi-Mode it seems.
 
  • Like
Reactions: ableto288
but unless it's running in DSi mode, it doesn't have any effect on DSiware, does it?
>_>
That's what this entire thread is about. It's about DSBricker. It bricks. DSi. Mode.
WHY EVEN FREAKING POST IF YOU'RE NOT READING ANY FREAKING THING RAAAARGH
this has been a sortofish hidden rage by janthran. If you're a smartass black-theme user then gtfo
 
  • Like
Reactions: 1 person
Guys, watch my original videos on the subject, they're in the spoiler at the bottom of the first post.

This bricker bricks DS AND DSi functionality on the 3DS system. If someone really, REALLY wants me to, I'll download another DSiware game off of the eShop (I have a bunch) and make a quick video showing it also bricks that functionality. I don't have any retail DSi exclusive cartridges, so I can't test that, but logic denotes that DSi mode is DSi mode, whether it's loading DSiware or a cart.

Old flashcarts won't launch from this because the carts need to pass the 3DS's header checks. After that, everything seems like it should be fair game just like the old systems, but you can't hot swap anything in either because of how the 3DS works, so that's still out of the question.

----------------------------------------

I see three interesting points out of my testing:

1) that BOTH DS and DSi mode brick.

2) DS settings are likely corrupted, and as you see, corrupted to the extent that it makes the SM hang in 3DS mode when you try to access them.

3) Settings (some) can be uncorrupted/reset by changing your 3DS name/birthday, which then allows you access to your DS Message and Color. Upon attempting to launch anything that runs on DS or DSi mode, the settings recorrupt, and we're back at point 2, above.

--Changing settings doesn't unbrick

--Updating the firmware doesn't unbrick
 
Guys, watch my original videos on the subject, they're in the spoiler at the bottom of the first post.

This bricker bricks DS AND DSi functionality on the 3DS system. If someone really, REALLY wants me to, I'll download another DSiware game off of the eShop (I have a bunch) and make a quick video showing it also bricks that functionality. I don't have any retail DSi exclusive cartridges, so I can't test that, but logic denotes that DSi mode is DSi mode, whether it's loading DSiware or a cart.

Old flashcarts won't launch from this because the carts need to pass the 3DS's header checks. After that, everything seems like it should be fair game just like the old systems, but you can't hot swap anything in either because of how the 3DS works, so that's still out of the question.

----------------------------------------

I see three interesting points out of my testing:

1) that BOTH DS and DSi mode brick.

2) DS settings are likely corrupted, and as you see, corrupted to the extent that it makes the SM hang in 3DS mode when you try to access them.

3) Settings (some) can be uncorrupted/reset by changing your 3DS name/birthday, which then allows you access to your DS Message and Color. Upon attempting to launch anything that runs on DS or DSi mode, the settings recorrupt, and we're back at point 2, above.

--Changing settings doesn't unbrick

--Updating the firmware doesn't unbrick
OK, so what about carts that have retail headers?? Would they still work if we were to remove the flashcart/fake-cart checks?
 
So what we're trying to do is use some kind of DS writer thingy to change it so it reads fake headers.

What if the header check stored on 3DS frimware though? Though it is unlikely...

Also, what can we do with 13 O's? How is that significant?
 
OK, so from what I understand, I think there may be a ton of potential from this. None for 3DS hacking, but, if possible, could make the DSi hacking community blow up. What I'm thinking is that since we can assume that the DSi partition of the flash is indeed writable, then, assuming there are valid headers are intact, would allow homebrew (DSi, mind you) to be loaded from the 3DS SM. In addition, DSiWare would be pirated. In terms of homebrew however, think of the possibilities?! I would love to see Sega MD and SuperNES emulators with front SD loading support. This is all just theory, but I can dream :D Then again, this is all assuming that we can find a way to write .app (or .wad files, if we can pack them) files to the flash, and that it is indeed possible to write files to the flash. What do you guys think??
 
--Updating the firmware doesn't unbrick
Wow, that's kinda weird. I guess they only update the needed stuff, and obviously they won't need to update the DS/DSi stuff any time soon, or ever. It kinda stinks for you though. Is this your main 3DS?!
He can just format and that fixes it, so he's fine.
 
  • Like
Reactions: 2 people
--Updating the firmware doesn't unbrick
Wow, that's kinda weird. I guess they only update the needed stuff, and obviously they won't need to update the DS/DSi stuff any time soon, or ever. It kinda stinks for you though. Is this your main 3DS?!

I'm assuming since nothing changes in the DS/i software interface on this system, they don't bother updating it since stuff like I did isn't supposed to happen. I'm curious if an official update has the ability to actually update that stuff though, should they find something that needs fixing in the future.

It's my main (and only) 3DS. A format through the system settings fixed it, as I still had access to 3DS functionality. Only negatives about it were having to set it up again, losing any play coins I had (I did't even have any since the last time I did this), and losing my gold pants Reggie. I'm not too concerned about any of those, lol.
 
  • Like
Reactions: 1 person
DSi 'community' haha. Anyway i think the reason this can't work is because of the hardware. I saw a comment by a knowledgable dev that said the registers are blocked by hardware from being able to write at all when in a different mode.

There's a set of limited set of functions that allow the modes to communicate with the higher level, it would only need to cause a crash to that to have this as the result, and likely impossible to leverage.
 
DSi 'community' haha. Anyway i think the reason this can't work is because of the hardware. I saw a comment by a knowledgable dev that said the registers are blocked by hardware from being able to write at all when in a different mode.

There's a set of limited set of functions that allow the modes to communicate with the higher level, it would only need to cause a crash to that to have this as the result, and likely impossible to leverage.
Then how is it able to erase??
EDIT: Or brick DSi mode??
 
DSi 'community' haha. Anyway i think the reason this can't work is because of the hardware. I saw a comment by a knowledgable dev that said the registers are blocked by hardware from being able to write at all when in a different mode.

There's a set of limited set of functions that allow the modes to communicate with the higher level, it would only need to cause a crash to that to have this as the result, and likely impossible to leverage.
Then how is it able to erase??
EDIT: Or brick DSi mode??

The DS settings. It corrupts the DS settings, which would be why DS mode doesn't work; DSi mode must pull some/all of those settings, so that wouldn't work. 3DS has its own settings, though crashes when it tries to read the corrupted ones. The DS/i firmware isn't shouldn't be being overwritten, though, like I've said - I am no master on the subject.
 
DSi 'community' haha. Anyway i think the reason this can't work is because of the hardware. I saw a comment by a knowledgable dev that said the registers are blocked by hardware from being able to write at all when in a different mode.

There's a set of limited set of functions that allow the modes to communicate with the higher level, it would only need to cause a crash to that to have this as the result, and likely impossible to leverage.
Then how is it able to erase??
EDIT: Or brick DSi mode??

The DS settings. It corrupts the DS settings, which would be why DS mode doesn't work; DSi mode must pull some/all of those settings, so that wouldn't work. 3DS has its own settings, though crashes when it tries to read the corrupted ones. The DS/i firmware isn't shouldn't be being overwritten, though, like I've said - I am no master on the subject.
We need @ichichfly to provide some insight on this
 

Site & Scene News

Popular threads in this forum