Homebrew O3DSXL turns off after a second & O3DS Write-Protect

[MochaMilk]

O3ds XL was working just fine about 2 hours ago. I wasn't doing anything other than playing games as normal. Now when I turn it on, the blue light indicator comes on then instantly fades to black again.
Same thing for o3ds, only it powers on, but says its write protected no matter which way my slider is.

Help?

Edit: Fixed o3dsxl. Idiotically inserted wrong SD. o3ds problem still stands though.

 

[Quantumcat]

You can fix the write protect issue by putting some sticky tape over the switch so it has an unbroken flat edge.

 

[Giodude]

Even if you did fix the problem, it is highly recommend you copy boot.firm to your ctrnand to allow your 3ds to boot up without the sd card. For some reason everybody skips this step in 3ds.guide.

 

[Majickhat55]

Even if you did fix the problem, it is highly recommend you copy boot.firm to your ctrnand to allow your 3ds to boot up without the sd card. For some reason everybody skips this step in 3ds.guide.

I never put it in CTRNAND. I don't advise noobs to either because when/if there are updates to boot9strap/Luma sometimes they don't realize they need to update boot9strap to update Luma and end up with two different versions, one in the NAND and the other on the SD. Since I doubt their using a nightly that tells them where they are running Luma from, they have no idea why their console won't turn on. I see it constantly, or when their SD card corrupts but they never used Luma Updater and it won't boot because they have incompatible versions there still.

It's only useful for turning the console on if your SD dies. Even then what can you do with your console without an SD card? PLay some DSi Games if you had any and that's about it. The whole argument about the console turning on without the SD is a moot point in my opinion and only necessary for hiding the existence of CFW. For the average user, it causes more problems than it solves in the long run.

 

[wormdood]

Same thing for o3ds, only it powers on, but says its write protected no matter which way my slider is.

you (or someone?) inserted the sd card upside-down bending the write protect mechanism in your 3ds you have two choices. you can either replace the broken sd slot or do what @Quantumcat said and put tape around the sd card covering the write protect switch

 

[Majickhat55]

you (or someone?) inserted the sd card upside-down bending the write protect mechanism in your 3ds you have two choices. you can either replace the broken sd slot or do what @Quantumcat said and put tape around the sd card covering the write protect switch

This reminds me of doing the same to the missing "block" on VHS tapes to turn them into "blank tapes" you can record with Lol. Sorry Bambi.

 

[Quantumcat]

I never put it in CTRNAND. I don't advise noobs to either because when/if there are updates to boot9strap/Luma sometimes they don't realize they need to update boot9strap to update Luma and end up with two different versions, one in the NAND and the other on the SD. Since I doubt their using a nightly that tells them where they are running Luma from, they have no idea why their console won't turn on. I see it constantly, or when their SD card corrupts but they never used Luma Updater and it won't boot because they have incompatible versions there still.

It's only useful for turning the console on if your SD dies. Even then what can you do with your console without an SD card? PLay some DSi Games if you had any and that's about it. The whole argument about the console turning on without the SD is a moot point in my opinion and only necessary for hiding the existence of CFW. For the average user, it causes more problems than it solves in the long run.

If the SD card reader in your 3DS dies it is pretty much a brick unless you put Luma on CTR-NAND. Also, Luma now tells you where it has been loaded from.

 

[Majickhat55]

If the SD card reader in your 3DS dies it is pretty much a brick unless you put Luma on CTR-NAND. Also, Luma now tells you where it has been loaded from.

Only if you're using nightlies unless there has been a release after 8.1.1 I haven't seen yet. If their SD reader dies, what do you purpose they do with their console while booting from CTRNAND? The only useful thing I can see is playing cartridges, dumping their tickets, or unbanned certs to use later; but those aren't absolutely necessary since they'd most likely buy a new console if theirs is out of warranty vs having it repaired for almost the same price.

You're right though. I was just putting in my opinion on the matter. If they want to be able to use the broken console to play their carts in the meantime that's definite a plus. I just think there are more cons to pros when it comes to having it in CTRNAND. How often does the SD reader actually stop working in comparison to the SD cards themselves?

 

[Quantumcat]

The con for Luma in CTR-NAND is only for noobs, and mitigated by Luma saying where it was loaded from, and fixable. In converse, the con for no Luma in CTR-NAND is an actual loss of functionality.
The relative likelihoods of each of these cons occurring versus the badness of each could mean you'd rather have the worse con with the less chance of happening, and that's fair enough. For me though the loss of the console is worth preventing even though the chance is low. For example, say you could roll a one thousand sided dice and if it lands on "1" you die, but on all other sides you get $1. I wouldn't roll that dice. If the amount was, say, $1 million I would give it a go, maybe even roll it twice. If the amount is, say, $1000 I would probably not roll it, but might think about it. Perhaps you would roll it. The reward vs risk is valued by different people in different ways, so some might roll and some won't