link?
Backing up the emunand if it is corrupted and restoring as sysnand aint gonna solve it if it corrupted.
link?
I thought he already had a rednand or EMUnand beforehandBacking up the emunand if it is corrupted and restoring as sysnand aint gonna solve it if it corrupted.
In the links I provided tracking and keeping count those previous users who bricked their 3DS with this exact BSoD,Not even ntrboothax can fix it?
A brick that ntrboothax can't fix is scary shit.In the links I provided tracking and keeping count those previous users who bricked their 3DS with this exact BSoD,
No. NTRboot or ntrboothax did not fix their bricks. It is bad shit of the highest degree in software bricking.
Working but not working. 3DS purgatory.
Yep from what I've seen it's unfixable atm.But because I cannot do some of the solutions listed I cannot tell whether or not they'd work.A brick that ntrboothax can't fix is scary shit.
Yep from what I've seen it's unfixable atm.But because I cannot do some of the solutions listed I cannot tell whether or not they'd work.
uhh, YEAH, I totally have a console with ALL those problems...Did you brick your console from the SecureInfo_C you mentioned in the AIO megascript thread?
I was helping out the OP of this thread through PM chat but have ceased due to running out of ideas. I am willing to PM you my idea only if you're console is experiencing the described BSoD brick and you have attempted all these options. The thing is, the idea was tested by LogicIsHansom but was found not to work.
(see https://3ds.hacks.guide/troubleshooting)
- battery & SD card removal and reinsert
- SysNAND restore (full & safe)
- CTRtransfer
- CTRtransfer with lower firmware > attempt firmware updating through Recovery Mode
- remove_ext_data.gm9
- Lazarus3DS
- @NicknameGoesHere solution
Yeah, since NTRBoot is the earliest possible code execution, Nintendo's own recovery tool, anything that it can't fix is....bad...A brick that ntrboothax can't fix is scary shit.
I will not post and share the idea here because the steps involve could end up bricking the 3DS further. If such a day comes where my own N3DSXL catches and experiences this BSoD brick, i will attempt the idea on my own system and share the information in case it does work.uhh, YEAH, I totally have a console with ALL those problems...
Okay, no, I don't, but I'm interested as to what the idea is.
hmm, so this is a random one off thing? can/how do we avoid it if we don't have issues now with latest updates to cfw b9s in future etc?
1. Never allow your 3DS to remain in sleep mode. It is either turned on or turned off. Some have reported bricking while their 3DS were in long duration of sleep. Others bricked while playing during a game. You can't prevent the latter from happening, but you can stop the former.
4. Last but not least, I recommend that you have a spare 4 GB SD card with EmuNAND installed for safe keeping and in case of emergency.
How did you get a blue screen from that? Makes me worry for my brothrr's 3DS. What error code did you get?If i have a new card (eg. 64G) for creating emunand, is it possible to first use godmode9 to generate a new emunand to the card, then copy all files from the old card (currently being used within the 3ds) to the new card, then swap cards so that new card is now inserted into console while keeping the original card somewhere safe as backup card?
i once have an old 3ds (U) running a game cart put in sleep mode for 3 days then, blue screen rip. The shop guy simply replaced its motherboard with a (J) one lol
How did you get a blue screen from that? Makes me worry for my brothrr's 3DS. What error code did you get?
Before I found out about this issue, I had put my new 3ds running Pokemon sun off a cart in sleep mode for a whole week.bsod shd be bootrom problem, dunno why and forgot error code
That 3ds was sleeping by closing the lids when a card game in the console was running.
Wait, so this causes BSoD bricks or bootrom errors?Before I found out about this issue, I had put my new 3ds running Pokemon sun off a cart in sleep mode for a whole week.
BSoD. Bootrom errors would be much different.Wait, so this causes BSoD bricks or bootrom errors?
Oh, because he said he got a blue screen.BSoD. Bootrom errors would be much different.
That's a different error. Leaving any system on for too long can mess up files. Some people have even reported that they got a bootrom error in the middle of playing a zelda game, turned it off, and the system booted back up just fine.Oh, because he said he got a blue screen.
If i have a new card (eg. 64G) for creating emunand, is it possible to first use godmode9 to generate a new emunand to the card, then copy all files from the old card (currently being used within the 3ds) to the new card, then swap cards so that new card is now inserted into console while keeping the original card somewhere safe as backup card?
i once have an old 3ds (U) running a game cart put in sleep mode for 3 days then, blue screen rip. The shop guy simply replaced its motherboard with a (J) one lol