This should be in big, font 60, red colors. Thanks for sharing
already front page'd
This should be in big, font 60, red colors. Thanks for sharing
already front page'd
yes
BOOTROM 8046
ERRORCODE 00F800FE
00000000 00000000
00000400 00000000
DANGER
STAY AWAY FROM
R4i Deluxe Edition firmware 4.0B2
It can brick your device!
(just got it bricked)
already front page'd
Where is it? I don't see it on the front page
you only need to unbrick if you have the blue screen of death, you can upgrade and downgrade at will with a hardware mod and SD readerQuestion, I've made a NAND backup with my SD Card reader, if I were to write it back, would my 3DS (Not XL) brick without this "Unlock"?
Thanks!
Question, I've made a NAND backup with my SD Card reader, if I were to write it back, would my 3DS (Not XL) brick without this "Unlock"?
Thanks!
pretty sure it will work, i *believe* this issue is down to some sort of firmware corruption, reverting to a backup before this happened should fix it.....i have actually wondered about this as it happened to one of my emunand setups and restoring a emunand backup worked fine...there was no SD card faults so i assume its just a software related error and not a hardware error....i would say it would definalty be worth a shot and feel it would virtually definaltly work out for youHi first time poster but long time visitor of gbatemp.
I wanted to know if this would work with a 3ds XL that has the black screen of death. I was using my gateway on Animal Crossing and put it to sleep but it now stuck in a black screen when I turn it on. When I hold the power button it shows the sleep mode screen but it still had access to the update menu via L+R+Up+A . I even updated it thinking it was a firmware issue so that I could downgrade it later and I still have a black screen. I have tried the WI-FI card trick and it did not work. I don't know why but I feel its a nand issue.
Has anyone had this problem and/or found a fix? I have heard that hundshamer is an excellent 3DS XL nand mod for the US but I would like to know if this is fixable or do I need a new unit altogether so I don't waste their time.
(I have my dumped 4.5 nand if its needed for a diagnostic)
pretty sure it will work, i *believe* this issue is down to some sort of firmware corruption, reverting to a backup before this happened should fix it.....i have actually wondered about this as it happened to one of my emunand setups and restoring a emunand backup worked fine...there was no SD card faults so i assume its just a software related error and not a hardware error....i would say it would definalty be worth a shot and feel it would virtually definaltly work out for you
if you want, im sure you could send the backup to hundshamer with the console and he can restore the console before he starts doing the work with the usb port.....if it doesnt work he *might* be able to charge less as it would be less work for him than adding all the usb port etc(this is actually the longest part of the process, so if you just throw the adpter in and flash the old nand dump to test before you do the rest you save your self a lot of time if it wasnt going to work anyway).......i know i wouldnt mind offering it at a discount for someone if they wanted me to try this out, but im uk based so wouldnt really be an option
.....hope you dont mind me making this suggestion hundshamer but i would say it will more than likely work anyway
nope, they are only needed if you get the console bricked via the brick code, which results in the blue screen of death.....for this job, just win32diskimager would be neededThanks I'll PM hundshamer right away, however for future reference do you actually need an Arduino or Raspberry Pi to rewrite your nand from backups? I have seen YouTube videos where people just hooked the 3DS XL to their computer and uses Win32 Diskimager to write the nand. I just want confirmation in case this happens again I could fix it myself.
you don't actually need to do a force erase no more, just do the unlock command and it should be unbrickedI'm trying to unbrick a 3ds using force erase then reflash it.
When I try to do a force erase I get status 0x02000900 before it tries to send the force erase.
After sending the force erase it gets back status 0x03000900 which is still locked.