No, it's up to date. Just checked.Just to see if I got this right, the link at the top on the first page is (latest firmware) outdated right?
The site I'm getting it from says it will update it themselves though, so I'm covered there at least.
No, it's up to date. Just checked.Just to see if I got this right, the link at the top on the first page is (latest firmware) outdated right?
The site I'm getting it from says it will update it themselves though, so I'm covered there at least.
Isn't it depressing how people still don't get this after how many years flash carts have come into existence?Never update the 3DS first! Updating the 3DS first is what CAUSES the cart to be blocked.
ALWAYS update the flash cart first.
Those using BAGplug UI and wanting to update:
1) Copy update to root of sdcard
2) In "/_dstwo" rename "dstwo.nds" and "boot.ini"
3) Copy "dstwo.nds" from original dstwo EOS download to "/_dstwo"
4) Put sdcard into DSTwo then into handheld system of choice(hopefully one that is updateable)
5) Run update after EOS prompts you
6) Work backwards, undoing steps 4 to 1
7) Good to go!
You should probably post that in the BAGPlug thread as well.Not sure where to put this, but this seemed logical. I just got BAGplug working on my new dstwo and with the new patch that was released today(to cover 3ds 4.5) I didn't want to start over. I replaced the BAGplug "dstwo.nds" with the original and also renamed "boot.ini" to negate it. The dstwo then booted fine into the EOS system and updated.
This is probably normal for most but I couldn't find anything regarding this and I'm sure someone else might want to know. Thanks for reading.
Code:Those using BAGplug UI and wanting to update: 1) Copy update to root of sdcard 2) In "/_dstwo" rename "dstwo.nds" and "boot.ini" 3) Copy "dstwo.nds" from original dstwo EOS download to "/_dstwo" 4) Put sdcard into DSTwo then into handheld system of choice(hopefully one that is updateable) 5) Run update after EOS prompts you 6) Work backwards, undoing steps 4 to 1 7) Good to go!
If you just rename the original dstwo.nds to something else, you can keep it on your card and just run it in BAGPlug to start the update without shifting files around.Not sure where to put this, but this seemed logical. I just got BAGplug working on my new dstwo and with the new patch that was released today(to cover 3ds 4.5) I didn't want to start over. I replaced the BAGplug "dstwo.nds" with the original and also renamed "boot.ini" to negate it. The dstwo then booted fine into the EOS system and updated.
This is probably normal for most but I couldn't find anything regarding this and I'm sure someone else might want to know. Thanks for reading.
Code:Those using BAGplug UI and wanting to update: 1) Copy update to root of sdcard 2) In "/_dstwo" rename "dstwo.nds" and "boot.ini" 3) Copy "dstwo.nds" from original dstwo EOS download to "/_dstwo" 4) Put sdcard into DSTwo then into handheld system of choice(hopefully one that is updateable) 5) Run update after EOS prompts you 6) Work backwards, undoing steps 4 to 1 7) Good to go!
If you just rename the original dstwo.nds to something else, you can keep it on your card and just run it in BAGPlug to start the update without shifting files around.