Hacking Baffled, pristine 3DS XL got bootrom 8046 screen.

[Nikotchi]

I don't know what's going on, my friend's 3DS XL just bricked.

The events were as follows:

-He updated his console from 7.1.0-14 to 7.1.0-15
-Not too long after that, the console froze, so he turned it off
-Then, when he pressed the power button, he got the bootrom 8046 BSOD.

Now, as far as we know, no flash card (DS or 3DS) has touched his console, ever. Let alone mod or exploit files. So, assuming the facts I just stated are true, (None of us have a reason to lie at all, but you never know.) my question is: What could have caused this?

Also, a little difference I've noticed from what I've read about the other bricks, is that some times the blue screen does not appear immediately, the screen remains black for a while before showing it, or even stays black for good.

Thank you

 

[gamesquest1]

BSOD can be a general hardware fault, unfortunatly with all the recent flash card BSOD's it will be hard to find out any info......look at the whole code the 0000000000000 000000000000 parts, i think the gateway bricks are always something like 00000000008 000000000 on the first line, only thing you can do is send it off to ninty

 

[Xzi]

With hardware/software, there's always a slight chance that something can go catastrophically wrong, even when it's a company like Nintendo designing it. There are just too many possible factors to make anything 100% fool-proof.

Your friend's issue is a known one for Nintendo, and it has happened to other non-cart owning 3DS users. See here: http://en-americas-support.nintendo.com/app/answers/detail/a_id/532/p/430/c/181

That's also where he can begin the repair process.

 

[Wisenheimer]

Sounds like the update was not flashed right (maybe a power loss, stray high energy photon, or bad NAND sector) and it got corrupted.

 

[inuyasha555]

Isn't the last number only like the eshop version? I thought those didn't require real updates, they just happened when you connect online or something.

You said it just froze but froze doing what? Game, system settings?

 

[kyogre123]

This is the second case of bricks reported due to this 7.1-15 update in this forum. You need to contact Nintendo, there's no other solution.

 

[Huntereb]

This is the second case of bricks reported due to this 7.1-15 update in this forum. You need to contact Nintendo, there's no other solution.

As he said, If you didn't use any type of unlicensed software on it, you should talk to Nintendo.

 

[Nikotchi]

BSOD can be a general hardware fault, unfortunatly with all the recent flash card BSOD's it will be hard to find out any info......look at the whole code the 0000000000000 000000000000 parts, i think the gateway bricks are always something like 00000000008 000000000 on the first line, only thing you can do is send it off to ninty

With hardware/software, there's always a slight chance that something can go catastrophically wrong, even when it's a company like Nintendo designing it. There are just too many possible factors to make anything 100% fool-proof.

Your friend's issue is a known one for Nintendo, and it has happened to other non-cart owning 3DS users. See here: http://en-americas-support.nintendo.com/app/answers/detail/a_id/532/p/430/c/181

That's also where he can begin the repair process.

Thanks guys, just checked. Both rows end in 0. We were a bit worried he would be denied assistance from Nintendo because of the Gateway fuss.

Isn't the last number only like the eshop version? I thought those didn't require real updates, they just happened when you connect online or something.

You said it just froze but froze doing what? Game, system settings?

It was while browsing the home menu.


Welp, it seems it was just a case of extreme bad luck.
Thank you all.

 

[Msparky83]

Man that sucks. I'm sorry that you have encountered the BSOD. I did read somewhere on this forum (and if I can find that thread I will update my post with the details) that if the eMMC encounters more than three bad blocks in a row that it will lock itself as a protection measure. So, if you do have a RasPi and the unbricking files (with proper hardware mods in place) you could test to see if the eMMC in fact did lock itself. Though I doubt this is the case. Cheers, and if you do decide to try this method to see if this is in fact the case let us know on the forums what you come up with.

 

[kyogre123]

Man that sucks. I'm sorry that you have encountered the BSOD. I did read somewhere on this forum (and if I can find that thread I will update my post with the details) that if the eMMC encounters more than three bad blocks in a row that it will lock itself as a protection measure. So, if you do have a RasPi and the unbricking files (with proper hardware mods in place) you could test to see if the eMMC in fact did lock itself. Though I doubt this is the case. Cheers, and if you do decide to try this method to see if this is in fact the case let us know on the forums what you come up with.

WTF? Don't do this or Nintendo will refuse to repair your system.

 

[qUaK3R]

Where are the guys who are in charge of blaming GW for this?

 

[Msparky83]

WTF? Don't do this or Nintendo will refuse to repair your system.

Im not saying its a good idea, but he would definitely know if the eMMC was locked by updating the firmware and shortly thereafter encountering the glitch that caused his friends console to BSOD. But kyogre is right, you shouldnt do this "if" you plan on Nintendo fixing this console at all as doing so will indefinitely void your warranty.

 

[kyogre123]

Im not saying its a good idea, but he would definitely know if the eMMC was locked by updating the firmware and shortly thereafter encountering the glitch that caused his friends console to BSOD. But kyogre is right, you shouldnt do this "if" you plan on Nintendo fixing this console at all as doing so will indefinitely void your warranty.

To be frank, having an eMMC lock as part of the official firmware functions doesn't make any sense to me; it's most likely that the firmware just got corrupted in the update process and could be fixed by flashing a NAND backup through the regular method if it was made beforehand.

 

[Msparky83]

To be frank, having an eMMC lock as part of the official firmware functions doesn't make any sense to me; it's most likely that the firmware just got corrupted in the update process and could be fixed by flashing a NAND backup through the regular method if it was made beforehand.

Notice the part where I said "Glitch", that very well could have caused a corruption if something was writing to the nand at the time. But if he was just "browsing" then I doubt that was the case either.

 

[kyogre123]

Notice the part where I said "Glitch".

Sorry, I completely ignored that because at first you said:

I did read somewhere on this forum (and if I can find that thread I will update my post with the details) that if the eMMC encounters more than three bad blocks in a row that it will lock itself as a protection measure.

Which doesn't make sense to me.

And about the OP, given that the error code is the same as the one that shows after the bricking code triggers, probably this code is not strictly indicating that the NAND is locked; however, Nintendo could act reluctant due to the amount of bricked systems that are being reported with the same code.

 

[Msparky83]

Sorry, I completely ignored that because at first you said:


Which doesn't make sense to me.

And about the OP, given that the error code is the same as the one that shows after the bricking code triggers, probably this code is not strictly indicating that the NAND is locked; however, Nintendo could act reluctant due to the amount of bricked systems that are being reported with the same code.

Yeah, lol. I'm sure Nintendo is having a field day with all of this.

 

[Soul_Alchemist]

Common guys, we all know Nintendo's Firmware is flawless. GW strikes again! Should've used 2.0b1 / 1.2!!! </GWHaterLogic>

 

[Huntereb]

Common guys, we all know Nintendo's Firmware is flawless. GW strikes again! Should've used 2.0b1 / 1.2!!! </GWHaterLogic>

The bricking code works so well, it effects consoles of people who only think of clone cartridges!

 

[Nikotchi]

In an unexpected turn of events my friend's 3DS came back to life. He left the console on all night so the battery would run dry. This morning when he plugged it in and turned it on... BAM! good as new.

On El Otro Lado (Spanish Tech & brew Forum) a similar case was reported with the very same solution.

 

[n1ghty]

Why are so many people waiting until the battery is empty? Just remove the damn screw on the back of the 3DS XL and pull the battery out. This does not void the waranty...