Hacking [ideas?] Bricked n3DS XL

  • Thread starter Thread starter remix2k
  • Start date Start date
  • Views Views 9,842
  • Replies Replies 48

remix2k

Well-Known Member
Newcomer
Joined
Mar 24, 2016
Messages
52
Reaction score
9
Trophies
0
Age
47
XP
154
Country
United States
I purchased an already bricked New 3DS XL (I have no history on how it was bricked).
I wasn't sure if it was soft or hard bricked.
I also don't know what version firmware it was on when bricked.

When I power it on normally the top screen stays black and the bottom screen show the error message: "An Error Has Occurred. Hold Down the POWER Button..."

If I try recovery mode, I get the blue and amber lights but both screens remain black.

I don't have a NAND backup but was wondering...
What if I hardmod and dump the currently bricked NAND, then inject the 10.4 native_firm into the NAND dump and flash it back. (using the old 10.7 hardmod downgrade method).

Any thoughts on if this would work or not?
Can I do anything else to the bricked NAND dump then flash it back using a hardmod to recover this thing?

Thanks for any input or ideas.

Updates:
I tried using a card reader that works on my o3DS but this n3DS didn't seem to like it.
Ordered on of these: http://www.amazon.com/Anker®-Reader-RS-MMC-Support-Warranty/dp/B006T9B6R2

Here is the error I get when powering on without any hardmod (BRICKED):
26929999146_1b5f9a5c6c_b.jpg


Here is a picture of the setup that works with my o3DS but not this n3DS:
26958068016_49ebd2c8ce_b.jpg


Here's what I get when powered on with this setup 00000400 error code:
26958079246_203ee36f6c_b.jpg


Here's my new setup but I'll have to order a compatible SD reader as the 2 I have don't work :(
26958067266_890efbbd72_b.jpg

Here is what I see when powered on with the new setup and SD readers (error code is now 00000200 instead of the 00000400 I got with the old setup:
26958077376_4f41f21521_b.jpg
 
Last edited by remix2k,
Take it back to where you got it, not sure why'd you want to spend money on an already bricked 3ds unit when you can buy a fresh stock one? Money for the ds its self and then commission work to get it hardmodded seems pointless to me, personally.
 
The board itself would be useless. Seeing as it's a N3DSXL, and you probably have no NAND backups for it, it's useless from any perspective. (Assuming someone sold for parts after they botched OTP)

Edit: That and you have no xorpads either, so decryption isn't really possible. Plus if it botched OTP, your NAND dump would be all sorts of f'ed up anyways to inject anything.
 
Last edited by ,
The board itself would be useless. Seeing as it's a N3DSXL, and you probably have no NAND backups for it, it's useless from any perspective. (Assuming someone sold for parts after they botched OTP)

Edit: That and you have no xorpads either, so decryption isn't really possible. Plus if it botched OTP, your NAND dump would be all sorts of f'ed up anyways to inject anything.
botched otp wouldnt turn on at all. this sounds like the person had tried to downgrade and failed
 
i would just take it back. i knew someone who bricked there 2DS literally like hours after he bought it lmfao and took it back said nothing worked so they just grabbed him a new one.
 
i would just take it back. i knew someone who bricked there 2DS literally like hours after he bought it lmfao and took it back said nothing worked so they just grabbed him a new one.
he bought it already bricked. he prob got it from ebay or someone off criagslist so he wont be able to return it
 
he bought it already bricked. he prob got it from ebay or someone off criagslist so he wont be able to return it

Ahh ok, well screw it go buy whatever DS it is, buy insurance and say it doesnt work then just get a refund but keep the good one and give back the bricked one lol.
 
I purchased the bricked unit for really cheap just for the top screen.
I swapped the bricked board with my other system that has a cracked top screen (but is still totally usable).

Figured it would be a fun experiment to try and fix even in a system with a cracked screen.

Thanks for all the "GREAT" advise but it's not something that I can or want to return :)
 
So back to my original question:

What if I hardmod and dump the currently bricked NAND, then inject the 10.4 native_firm into the NAND dump and flash it back. (using the old 10.7 hardmod downgrade method).
Can I do anything else to the bricked NAND dump then flash it back using a hardmod to recover this thing?

I am totally capeable of hardmodding this unit.
I've done it on a few other units in the past for downgrades without any problems.

And I'm not desperate to fix this thing, it was just an idea :)

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

I appreciate all the replies about returning it or swapping it out but I'm really looking for is someone with knowledge on how the native_firm offline NAND patching works and if it would be worth a try.
Maybe I should change the title of my post?
 
So back to my original question:

What if I hardmod and dump the currently bricked NAND, then inject the 10.4 native_firm into the NAND dump and flash it back. (using the old 10.7 hardmod downgrade method).
Can I do anything else to the bricked NAND dump then flash it back using a hardmod to recover this thing?

I am totally capeable of hardmodding this unit.
I've done it on a few other units in the past for downgrades without any problems.

And I'm not desperate to fix this thing, it was just an idea :)

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

I appreciate all the replies about returning it or swapping it out but I'm really looking for is someone with knowledge on how the native_firm offline NAND patching works and if it would be worth a try.
Maybe I should change the title of my post?
If it was that easy and doable it would have been done ages ago
 
If it was that easy and doable it would have been done ages ago
It probably is and probably has: The reason why may be so obscure is the fact one must hardmod their system in order to test such a method.

However, I wouldn't take my input as a "Yes, this works," because I can't confirm it myself either. (I think I remember asking about this in the original 10.4 thread revealing the hardmod downgrade method, but I can't remember their reply. If you sift through that large thread, you might find your answer!)
 
Guess I'll do a little more digging and give it a shot this weekend.

If I understand it correctly the hardmod downgrade injects a couple titles into your native_firm but doesn't touch the recovery_firm.
My thought here was if it can inject titles into the native_firm, why can't we inject all the titles needed to get native_firm booting again...
 
Guess I'll do a little more digging and give it a shot this weekend.

If I understand it correctly the hardmod downgrade injects a couple titles into your native_firm but doesn't touch the recovery_firm.
My thought here was if it can inject titles into the native_firm, why can't we inject all the titles needed to get native_firm booting again...
Oh, that is actually because we don't publicly have all of the keys to fully decrypt a NAND (unless you ask the 3DS for the passwords/xorpads directly via Decrypt9, after it's hacked&before it's bricked). We only know enough info to replace NATIVE_FIRM (possibly more, but definitely not all)
 
Oh, that is actually because we don't publicly have all of the keys to fully decrypt a NAND (unless you ask the 3DS for the passwords/xorpads directly via Decrypt9, after it's hacked&before it's bricked). We only know enough info to replace NATIVE_FIRM (possibly more, but definitely not all)


Isn't a busted native_firm what usually causes the brick?
 

Site & Scene News

Popular threads in this forum