Blue screen, unaccesible GM9

[KeeperCP1]

I MADE A HUGE MISTAKE! I hexedited a byte of my nand to see if i can still use godmode9, and my New3DS XL from Europe got bricked with a bluescreen! What is worse is that GM9 won't boot at all!!!
What should i do?

 

[jeffyTheHomebrewer]

Okay, I now GM9 is, literally, named GODMODE9 because of how powerful it can be, but why not ALWAYS restrict SysNAND Virtual to read-only?
(It's been a while since I've used GM9, can't remember if there's an actual nand drive you put luma on that's different or if I'm misremembering. If I am, disreguard what I said)

 

[KleinesSinchen]

Okay, I now GM9 is, literally, named GODMODE9 because of how powerful it can be, but why not ALWAYS restrict SysNAND Virtual to read-only?
(It's been a while since I've used GM9, can't remember if there's an actual nand drive you put luma on that's different or if I'm misremembering. If I am, disreguard what I said)

The equivalent on Unix-like systems would be block devices for accessing disks and partitions /dev/sda, /dev/sdb1 and such.

Partitioning software does – to my knowledge – nothing else than directly read/write on a block device. There are indeed reasons for writing into a RAW block device¹, and that includes GodMode9 on the 3DS. The first thing that comes to my mind is forced NAND restore², which is overwriting the complete NAND while not protecting crucial sectors. Even the normal restore option injects into virtual, not overwriting NAND.bin, but ctrnand, twln and twlp separately (open the megascript file on your computer)

We must face the truth here, although mentioning this could potentially give a..holes ideas (but I guess, sociopaths will be sociopaths anyway): Its not hard to develop malware trashing the content of the NAND. How should we repair this without injecting data into virtual "files" (CTRTransfer Type D9 does this)?

I don't see a way around having the option to directly write on NAND. In my opinion GodMode9 does a great job protecting the user from accidental³ modification of crucial parts. Serious question: What could be done more than this?

The lower screen is fully red – nature made us perceive red as a warning/danger by instinct – and it clearly says that proceeding can lead to bricking.


As a child of seven years, suddenly seeing this screen, I would have screamed: "Mom, Dad, please have look! What is this?!"



_________________________
¹ Yes, I know, things like Android phones have this option missing by default for "security reasons" (every limitation always has security reasons). My personal opinion on this is, that such phones are toy computers therefore.
² Don't do that without a good reason! It is very dangerous as well.
³ The amount of "I accidentally…"-threads is stunning.

 

[jeffyTheHomebrewer]

I see. Though honestly if I were the guy behind GM9, I guess I would've required more codes to be input for higher access levels for NAND writing for extra dumbass-proofing. (e.g. one on-screen code for level one, 3 codes for level 3)
Sure, it's unnecessary, but to be honest putting the codes in makes it a bit more fun too, but also ensures you know what you're doing in case the OTHER warnings weren't enough.

 

[KleinesSinchen]

Instead of your topic about getting an R4, you maybe should have posted this:

The wait is over guys, MY 3DS IS FINALLY UNBRICKED!!!
Here is everything for the unbricking of my 3ds, including the position of the magnet
The delivery took like 20 days

here, where your problem started.

Nice to see your N3DSXL is finally back from the dead. Please never use the hex-editor on SysNAND Virtual again.

 

[FoxPodZ]

So, I acually did the same thing for the reason that i was curious what would happen and i got the same blue screen but even worse, i forgot where i edited a hex value. I got my flashcard today in the mail and had no backup and all that stuff. Long Story short, i discovered the nand_hdr.bin file sitting there, when pressing A it revealed an option to Rebuild the NAND Header, which i tried after making a backup of the broken NAND. And it just worked. I'll hope someone will find what i wrote here useful.

 

[That1LoserGuy]

Oh my gosh...... This is why some people need an emunand for trying things.....

 

[Hayato213]

Oh my gosh...... This is why some people need an emunand for trying things.....

Well people doesn't really use an emunand for 3ds anymore.

 

[KeeperCP1]

Alright everybody, stop necrobumping.

 

[That1LoserGuy]

Well people doesn't really use an emunand for 3ds anymore.

But still, if your gonna experiment, do not risk your own console, why not choose to use, hmm... perhaps maybe a virtual version of your console, loaded from your SD card

 

[KeeperCP1]

Excuse me, haven't you heard of necrobumping?

 

[That1LoserGuy]

Excuse me, haven't you heard of necrobumping?

Sorry I'll stop now

 

[CoolMe]

Alright everybody, stop necrobumping.

Excuse me, haven't you heard of necrobumping?

It's not necrobumping. If you don't want people to post "derail" your thread, or simply post in here, then you could've just said closed it instead.

Sorry I'll stop now

No need. Unless you want to make your own thread?

 

[KeeperCP1]

It's not necrobumping.

If it's not necrobumping, then explain how there's replies from April 2023 while the last reply before those was from December 2022
There's a 4-MONTH GAP between the December one and the April one

 

[CoolMe]

If it's not necrobumping, then explain how there's replies from April 2023 while the last reply before those was from December 2022
There's a 4-MONTH GAP between the December one and the April one

That's exactly why it's not.

 

[AmandaRose]

Alright everybody, stop necrobumping.

Excuse me, haven't you heard of necrobumping?

If it's not necrobumping, then explain how there's replies from April 2023 while the last reply before those was from December 2022
There's a 4-MONTH GAP between the December one and the April one

Bumping old threads is allowed if new information is given. Which is what @FoxPodZ did.

Also it's only really gets classed as a necro if over 6 months old anyhow.

What is not allowed is backseat moderating which is exactly what you are doing by telling people to stop necro bumping.

 

[KeeperCP1]

SOMEBODY PLEASE LOCK THIS POST BEFORE EVERYBODY IS ENCOURAGING US TO NECROBUMP A 2022 POST AND ACCUSING ME OF BEING A NECROBUMPING IDIOT

 

[KleinesSinchen]

SOMEBODY PLEASE LOCK THIS POST BEFORE EVERYBODY IS ENCOURAGING US TO NECROBUMP A 2022 POST AND ACCUSING ME OF BEING A NECROBUMPING IDIOT

No need to shout.
Why not report your own thread and nicely ask for it to be locked?
==========

It is indirectly my responsibility that this topic got bumped since I linked to it as a warning to not make something similar.

There is some additional information worth noting here though:

Obviously hex-editing EmuNAND virtual will -- at worst -- brick EmuNAND. However, the particular example might even cause a wrong feeling of safety, since the NSCD header on EmuNAND is not used in the boot process, so damaging it has no effect whatsoever.