Hacking What is wrong with my 2ds, it can't boot to home menu?

SirNapkin1334 · Jun 14, 2018

@TurdPooCharger suicide method perhaps?

--------------------- MERGED ---------------------------

Actually, before you try that, try downgrading via CTRtransfer or update pack (ideally first one), and see if it works. Then update, with System Settings if it works or Recovery Mode of it doesn’t.

TurdPooCharger · Jun 14, 2018

SirNapkin1334 said:
@TurdPooCharger suicide method perhaps?

For anyone reading this and going WTF in what @SirNapkin1334 means by "suicide method", no, he's not telling OP to go off himself or his 3DS. You can refer to this earlier thread when he first asked what that idea was here. "Suicidal method" is a better descriptor in that intention is good, but the procedure is super risky.

There was a proposed idea discussed between him and I through PM, the details I rather not publicly divulge as it's untested, foolish to pull off under normal circumstances, and has a probably conclusion of leading to a super brick. I have (reluctant) plans to try purposely BSoD bricking my N3DSXL some day with...

all my NAND files backed up in every GodMode9 directory (hash and hex cross comparison for what went wrong)
EmuNAND already setup on a spare SD card with known working NAND setup (Horcrux theory)
ntrboot card & soldering iron for hardmod on the ready (what is dead, may never die)
funds saved up for a working replacement N3DSXL for motherboard swapping (body swap, hardware failure theory)
lastly, after every other options else has been exhausted, Suicide Method

To @SirNapkin1334, I want to help those who come across this brick save their 3DS'es but can't in good conscience tell them to do the electronic equivalent of "jumping off a water bridge to jolt momentary realization your life doesn't suck, there's more worth living for, you don goof cuz you 'bout die fool, and best pray to God your sorry arse lives through tis" to their systems [that's another way of looking at it versus the Samurai Champloo's Jin fight reference I told you about, lol).

If you intend to share this radical approach to willing participants who understand what they're getting themselves into, all I ask is you guys keep it to PM. This is considered dangerous knowledge as not only is it unproven, readers who comes across it and attempt the approach will almost certainly lead to the other Blue Screen of Death* brick (or worse nothing, nada screens).

* The acronym BSoD can refer to several different types of bricks where the B stands for black, blank, or blue. The one that is not recoverable to date is the black/blank one that (usually) has working sound in HOME Menu and working LCD screens in Recovery Mode.

SteelBANANA · Jun 16, 2018

TurdPooCharger said:
For anyone reading this and going WTF in what @SirNapkin1334 means by "suicide method", no, he's not telling OP to go off himself or his 3DS. You can refer to this earlier thread when he first asked what that idea was here. "Suicidal method" is a better descriptor in that intention is good, but the procedure is super risky.

There was a proposed idea discussed between him and I through PM, the details I rather not publicly divulge as it's untested, foolish to pull off under normal circumstances, and has a probably conclusion of leading to a super brick. I have (reluctant) plans to try purposely BSoD bricking my N3DSXL some day with...

all my NAND files backed up in every GodMode9 directory (hash and hex cross comparison for what went wrong)

EmuNAND already setup on a spare SD card with known working NAND setup (Horcrux theory)

ntrboot card & soldering iron for hardmod on the ready (what is dead, may never die)

funds saved up for a working replacement N3DSXL for motherboard swapping (body swap, hardware failure theory)

lastly, after every other options else has been exhausted, Suicide Method

To @SirNapkin1334, I want to help those who come across this brick save their 3DS'es but can't in good conscience tell them to do the electronic equivalent of "jumping off a water bridge to jolt momentary realization your life doesn't suck, there's more worth living for, you don goof cuz you 'bout die fool, and best pray to God your sorry arse lives through tis" to their systems [that's another way of looking at it versus the Samurai Champloo's Jin fight reference I told you about, lol).

If you intend to share this radical approach to willing participants who understand what they're getting themselves into, all I ask is you guys keep it to PM. This is considered dangerous knowledge as not only is it unproven, readers who comes across it and attempt the approach will almost certainly lead to the other Blue Screen of Death* brick (or worse nothing, nada screens).

* The acronym BSoD can refer to several different types of bricks where the B stands for black, blank, or blue. The one that is not recoverable to date is the black/blank one that (usually) has working sound in HOME Menu and working LCD screens in Recovery Mode.

So, I shouldn't do this.

TurdPooCharger · Jun 16, 2018

SteelBANANA said:
So, I shouldn't do this.

First, we haven't established for certain if your brick is the same one as @smallmedicap's brick.

His is definitely that exact BSoD type with HOME Menu BGM and working screens in Recovery Mode, as can be seen in his thread.
Yours exhibits most symptoms minus the BGM part. You never stated if your Recovery Mode works or not, so we're going with the assumption you've tried that already.

Another question that wasn't answered is if your O2DS is on a arm9loaderhax (A9LH) based CFW. This might be why those recovery methods haven't worked for you. If that's the case, you should try upgrading to B9S and redo CTRtransfer / Lazarus3DS / SysNAND restore (if you still have your original NAND dump somewhere). Until then, I can't conclude your brick is that one yet.

***

Without a ntrboothax flashcart (or hard mod) and a clean NAND image dumped when your 3DS/2DS was in a last known working state, the suicide method trades you one brick for a different brick. You will be no better off where you last started (perhaps worse!). Those prerequisites are needed as a followup to (hopefully) get out of that secondary brick where as you couldn't in the primary brick; this is all untested theory. I probably spilled enough details that some of you out there have a clue figuring out what this method entails and why it's bad because it's counter intuitive & should be avoided at all cost under normal circumstances.

So to answer your question @SteelBANANA: no, this method is not for you. The only person who should attempt this understands he or she is basically a guinea pig willing to do so in the name of science and further the 3DS homebrew cause, even if the outcome results in failure.

SteelBANANA · Jun 17, 2018

TurdPooCharger said:
First, we haven't established for certain if your brick is the same one as @smallmedicap's brick.

His is definitely that exact BSoD type with HOME Menu BGM and working screens in Recovery Mode, as can be seen in his thread.

Yours exhibits most symptoms minus the BGM part. You never stated if your Recovery Mode works or not, so we're going with the assumption you've tried that already.

Another question that wasn't answered is if your O2DS is on a arm9loaderhax (A9LH) based CFW. This might be why those recovery methods haven't worked for you. If that's the case, you should try upgrading to B9S and redo CTRtransfer / Lazarus3DS / SysNAND restore (if you still have your original NAND dump somewhere). Until then, I can't conclude your brick is that one yet.

***

Without a ntrboothax flashcart (or hard mod) and a clean NAND image dumped when your 3DS/2DS was in a last known working state, the suicide method trades you one brick for a different brick. You will be no better off where you last started (perhaps worse!). Those prerequisites are needed as a followup to (hopefully) get out of that secondary brick where as you couldn't in the primary brick; this is all untested theory. I probably spilled enough details that some of you out there have a clue figuring out what this method entails and why it's bad because it's counter intuitive & should be avoided at all cost under normal circumstances.

So to answer your question @SteelBANANA: no, this method is not for you. The only person who should attempt this understands he or she is basically a guinea pig willing to do so in the name of science and further the 3DS homebrew cause, even if the outcome results in failure.

Just for clarification, when I got into this situation by trying to install CFW when A9LH was the norm, but I bricked it. Years after, my friend unbricked it with ntrboot and installed b9s.

SirNapkin1334 · Jun 17, 2018

SteelBANANA said:
Just for clarification, when I got into this situation by trying to install CFW when A9LH was the norm, but I bricked it. Years after, my friend unbricked it with ntrboot and installed b9s.

Does GM9 work for you?

TurdPooCharger · Jun 17, 2018

SteelBANANA said:
Just for clarification, when I got into this situation by trying to install CFW when A9LH was the norm, but I bricked it. Years after, my friend unbricked it with ntrboot and installed b9s.

Did he install the latest B9S v1.3 ? Run SafeB9SInstaller and update it yourself just to make sure.
https://3ds.hacks.guide/updating-b9s

SirNapkin1334 said:
Does GM9 work for you?

He has GodMode9 up and running in post #29.

Btw, what version of GM9 are you using @SteelBANANA? Drag and drop the v1.6.3 GodMode9.firm in luma/payloads folder if you need to update it.

***

If your Recovery Mode never showed up, ~~try taking a strong magnet and messing with the sleep mode area around the (X)-(Y)-(B)-(A) from both the top and back sides of the 3DS bottom half.~~

Edit - Forgot, O2DS do not have magnet switch for sleep mode.

SirNapkin1334 · Jun 17, 2018

@SteelBANANA boot into GM9, then go to the S:/ drive, and enter the menu for firm0.bin. Go to FIRM Image Options... -> Verify File. Tell me what it says. Do the same for firm1.bin, located in the S:/ drive as well.

SteelBANANA · Jun 18, 2018

SirNapkin1334 said:
Does GM9 work for you?

yes

--------------------- MERGED ---------------------------

SirNapkin1334 said:
@SteelBANANA boot into GM9, then go to the S:/ drive, and enter the menu for firm0.bin. Go to FIRM Image Options... -> Verify File. Tell me what it says. Do the same for firm1.bin, located in the S:/ drive as well.

For both, it says, Verification success

--------------------- MERGED ---------------------------

U

TurdPooCharger said:
Did he install the latest B9S v1.3 ? Run SafeB9SInstaller and update it yourself just to make sure.
https://3ds.hacks.guide/updating-b9s

He has GodMode9 up and running in post #29.

Btw, what version of GM9 are you using @SteelBANANA? Drag and drop the v1.6.3 GodMode9.firm in luma/payloads folder if you need to update it.

***

If your Recovery Mode never showed up, ~~try taking a strong magnet and messing with the sleep mode area around the (X)-(Y)-(B)-(A) from both the top and back sides of the 3DS bottom half.~~

Edit - Forgot, O2DS do not have magnet switch for sleep mode.

Updated and recovery mode does boot, but recovery mode doesn't do anything.

SirNapkin1334 · Jun 19, 2018

I am at a total loss...
Last idea: do you have aflashcart?

TurdPooCharger · Jun 19, 2018

SteelBANANA said:
Updated and recovery mode does boot, but recovery mode doesn't do anything.

The community can't help you. We don't know what's the underlying cause to this brick nor a (proven) solution to fix it at hand. The only one who knows how to unbrick this BSoD is... Nintendo. You'll have to send in your system to them for repair work if they're still servicing old type systems.

Case #11 of BSoD for tracking and research purposes.

Shorthanded Foot Notes:

Brick stemmed from failed A9LH install.
First known recorded O2DS to be affected.
Has all signs of BSoD brick, except the BGM is not present in HOME Menu.
Tried CTRtransfer, downgrade + upgrade, Lazarus3DS, etc. Original NAND backup was not available.

10 - New 3DS XL - Black Screens & No Input on Home Menu - BSOD Brick?

09 - CFW 3DS - Black Screens

08 ??? - New 3DS brick after installing a bad CIA file

07 - Luma3DS Noob Question + Bricked?

06 - Help my 3ds boots with black screens

05 - Black Screens, Everything works in system update mode, Error when camera disconnected

04 - N3DS XL Black Screen of Death

03 - 3ds bricked itself, can't figure out why or how to fix.

02 - Big Problem with a possible Brick on New 3ds XL

01 - Black screens on n3ds xl

***

Post Update
On August 22, 2018, gisel213 solved and provided the solution in fixing this BSoD brick.

New 3DS XL Screens only display recovery mode

SteelBANANA · Jun 20, 2018

SirNapkin1334 said:
I am at a total loss...
Last idea: do you have aflashcart?

I know someone.

--------------------- MERGED ---------------------------

TurdPooCharger said:
The community can't help you. We don't know what's the underlying cause to this brick nor a (proven) solution to fix it at hand. The only one who knows how to unbrick this BSoD is... Nintendo. You'll have to send in your system to them for repair work if they're still servicing old type systems.

Case #11 of BSoD for tracking and research purposes.

Shorthanded Foot Notes:

Brick stemmed from failed A9LH install.

First known recorded O2DS to be affected.

Has all signs of BSoD brick, except the BGM is not present in HOME Menu.

Tried CTRtransfer, downgrade + upgrade, Lazarus3DS, etc. Original NAND backup was not available.

10 - New 3DS XL - Black Screens & No Input on Home Menu - BSOD Brick?

09 - CFW 3DS - Black Screens

08 ??? - New 3DS brick after installing a bad CIA file

07 - Luma3DS Noob Question + Bricked?

06 - Help my 3ds boots with black screens

05 - Black Screens, Everything works in system update mode, Error when camera disconnected

04 - N3DS XL Black Screen of Death

03 - 3ds bricked itself, can't figure out why or how to fix.

02 - Big Problem with a possible Brick on New 3ds XL

01 - Black screens on n3ds xl

Would Nintendo take it and fix it? What's a Bsod, just clarification.

SirNapkin1334 · Jun 20, 2018

SteelBANANA said:
I know someone.

--------------------- MERGED ---------------------------

Would Nintendo take it and fix it? What's a Bsod, just clarification.

Okay, so you don’t have a flashcart. I was wondering because sometimes booting with a flashcart jnserted, especially if flashed with ntrboot, you’ll just have a black screen. And BSoD means “Black Screen of Death”

TurdPooCharger · Jun 20, 2018

SteelBANANA said:
Would Nintendo take it and fix it? What's a Bsod, just clarification.

You'll have to get in contact with a Nintendo representative to see if they're servicing O2DS these days. Make sure you remove all traces of CFW and make no mention you've hacked it.

Not on that numbered list, here's probably the first person, TheSpaceKing12, who documented this particular brick:

Here are some of his comments:

***

Marcel oinonen said:
did you update with menuhax installed? If yes, then boot up without the sd card, and change theme, and insert sd card.

TheSpaceKing12 said:
No hacks were on the system at the time of the video. I had owned it for like a week then.

***

RICKnMORTY said:
how did you fix it?

TheSpaceKing12 said:
+Tristan I sent it in to get repairs.

***

Hipeopeo YT said:
Where did you send it into?

TheSpaceKing12 said:
+Hipeopeo Nintendo

***

Fk said:
i have the exact same problem.... please help

TheSpaceKing12 said:
Ask Nintendo. I never did figure it out. They told me water caused it.

TheSpaceKing12 said:
Dude. I can't help. My system was repaired ages ago. The best advice I could give would be to go to nintendo's tech support. And file a repair. When I did mine they claimed it was water damage(even though I knew for a fact it wasn't)

SteelBANANA · Oct 31, 2018

I sent it to Nintendo, say they fix it, should I put CFW it with my R4 when I get it?

SteelBANANA · Oct 31, 2018

Sorry, repeated messages, my computer was being slow.

TurdPooCharger · Oct 31, 2018

SteelBANANA said:
I sent it to Nintendo, say they fix it, should I put CFW it with my R4 when I get it?

If you're ultimate goal is to acquire custom firmware on your 2DS, then yah use your R4 flashcart to try hacking it again with NTRboot. If you don't like this method (perhaps to avoid bad luck in a repeat failure), there's also Frogminer you can try.

***

By the way
I don't know if you ever got the memo, but Gisel213 shared his solution fixing that BSoD from this thread here.

SteelBANANA · Nov 1, 2018

TurdPooCharger said:
If you're ultimate goal is to acquire custom firmware on your 2DS, then yah use your R4 flashcart to try hacking it again with NTRboot. If you don't like this method (perhaps to avoid bad luck in a repeat failure), there's also Frogminer you can try.

***

By the way
I don't know if you ever got the memo, but Gisel213 shared his solution fixing that BSoD from this thread here.

The solution went out after I sent the 2DS, they are having delays in the repairs.

Hacking What is wrong with my 2ds, it can't boot to home menu?

Renound Aritst

Meh.

Well-Known Member

Meh.

Well-Known Member

Renound Aritst

Meh.

Renound Aritst

Well-Known Member

Renound Aritst

Meh.

Well-Known Member

Renound Aritst

Meh.

Well-Known Member

Well-Known Member

Meh.

Well-Known Member

Similar threads

Popular threads in this forum