I decided to redo section three of plailect's guide. When I try to launch Steel Diver Sub Wars to the exploit on my hacked 2DS, the game had an error as it sent me back to the home menu. Should I delete it, redownload it, and try again?
Should be FAT32 but I'm not sure about the cluster size.wow, it seems i came in when someone was asking the same question as i was.
but i still want to ask it to confirm, i have a 128GB Mirco SD Card, what format should it be, and what cluster should it be? thanks. this is for installing cias and what not on a cfw 3ds.
If your 2DS is already hacked you don't need Steelhax to access homebrew, just install the homebrew launcher cia.I decided to redo section three of plailect's guide. When I try to launch Steel Diver Sub Wars to the exploit on my hacked 2DS, the game had an error as it sent me back to the home menu. Should I delete it, redownload it, and try again?
cool it already is, lets see if this no brand cheap Micro SD Card can store atleast 100GB, of dummy files, it also appears you can't go past 3.99GB on Fat32, so that should mean no 3DS game should be higher then 3.99GB.Should be FAT32 but I'm not sure about the cluster size.
If your 2DS is already hacked you don't need Steelhax to access homebrew, just install the homebrew launcher cia.
Also why do you want to redo it? Some things are dangerous to do on a console that already has a9lh.
You'll need an entrypoint different from browserhax with the proper *hax for your 9.2 system to be able to run the downgrader again
should i keep putting dummy files (3.99GB size) until the card is full or should i stop at some point, at 47GB right now, this is going to take awhile.Should be FAT32 but I'm not sure about the cluster size.
You can use emuNAND9Hi guys, I need to install emunand on my o3ds (which I don't know how to) can someone help me with that? I want to try it for the 3 SD card trick.
I think it's only devMenu / BigBlueMenu that have a problem when there's a large amount of free space. Probably don't worry about it unless you have a problem installing cia files, then you can try it as part of your troubleshooting.should i keep putting dummy files (3.99GB size) until the card is full or should i stop at some point, at 47GB right now, this is going to take awhile.
You can't use emuNAND9 from homebrew when you are over 9.2. Use it as a Luma payload just like all the other tools ending in "9".I tried launching it via homebrew but all I get it either a red or a black bottom screen and nothing happens... I placed the .3dsx and .smh on /3ds/emunand9 in case that helps.
im just doing this to see if it's truly 128GB (124GB) or if it's a defective/fake Micro SD Card, since it has no brand, and came from Ebay. the write speed is decent it's (8MB)I think it's only devMenu / BigBlueMenu that have a problem when there's a large amount of free space. Probably don't worry about it unless you have a problem installing cia files, then you can try it as part of your troubleshooting.
Do you have a9lh? Put the bin file in luma/payloads and rename it say up_emunand9.bin, then you can hold Up when booting and it will launch.I am on sysnand 9.2 and it still doesn't work. How do i do that with luma payload?
Use H2testw to test if it's genuine.im just doing this to see if it's truly 128GB (124GB) or if it's a defective/fake Micro SD Card, since it has no brand, and came from Ebay. the write speed is decent it's (8MB)
Do you have a9lh? Put the bin file in luma/payloads and rename it say up_emunand9.bin, then you can hold Up when booting and it will launch.
If you don't have a9lh then you should get it: https://3ds.guide/get-started/
Also are you certain you even want an emuNAND? There's no use for them nowadays. Maybe ask about the problem you actually want to solve that you think having an emuNAND will solve. Maybe you won't need one after all.
that's the problem, my PC i guess, has problems writing stuff to SD Card, idk if it's my PC or the SD Card reader. i tried using H2testw, and it always errors out, because my PC or SD Card Reader sucks? while using a program called Dummy File Creator it seems to put the dummy files on the Micro Sd Card just fine, only error i get is when it goes past 3.99GB and it says disk out of space, probably because it's on Fat32.Use H2testw to test if it's genuine.
Ah ok. I don't think you'll be able to system transfer still. But if anyone knows how it will be @RonheroI recently region changed my o3ds from US to JPN just so that I can downgrade my n3dsxl. The guide said that all o3ds should work but mine didn't. I keep getting the error code 005-5602, which means that I am in the incorrect region. So I did a little research in gbatemp and found that someone made it work. The person said that I need to do the 3 SD card trick (which works for emuNAND but not sysNAND? IDK) to change the eshop region from US to JPN. I know that emuNAND is redundant but I only plan on using it to downgrade my n3ds xl. After the dsiware downgrade process, I'll immediately remove emuNAND. Oh and I have al9h already.
Ah ok. I don't think you'll be able to system transfer still. But if anyone knows how it will be @Ronhero
That should only be a problem if a single file is over 4GB. You would be super unlucky if you bought a fake 128GB card and it was only 4GB, usually they'd be at least 32GB :-( Maybe format it as exFAT then test, and if all good then format as FAT32 again ready for your console.that's the problem, my PC i guess, has problems writing stuff to SD Card, idk if it's my PC or the SD Card reader. i tried using H2testw, and it always errors out, because my PC or SD Card Reader sucks? while using a program called Dummy File Creator it seems to put the dummy files on the Micro Sd Card just fine, only error i get is when it goes past 3.99GB and it says disk out of space, probably because it's on Fat32.
it's on Fat32, and i have fitted a total of 75GB worth of dummy files on it.That should only be a problem if a single file is over 4GB. You would be super unlucky if you bought a fake 128GB card and it was only 4GB, usually they'd be at least 32GB :-( Maybe format it as exFAT then test, and if all good then format as FAT32 again ready for your console.