Hacking fixing bricked 3ds with ntrboothax

[Deleted User]

So I need to know a couple of things. First off, I got the worst type brick which is the bootrom error. (I was restoring a backup which must of got corrupted or the storage device and it managed to kill it. aka brick 3ds) So, If I use ntrboothax it should fix the boots. And then restore using a backup with a good storage device should fix it entirely right? (i'm assuming that bootrap9 only fixes boots, and doesn't fix file errors. which is why I would need to restore a good backup for the files)

EDIT: apparently I didn't give enough info... which is silly because I was rather quite specific on how the brick happened. Restored a backup on a bad storage device. Which then killed 3ds. But if I REALLY have to go deeper then ok. Its a n3ds firmware was 11.5 and I was going back to 11.4 via a backup and not a ctr transfer. bootrom error as follows
BOOTROM 8046
00F800EE
FFFFFFFF FFFFFFFF
00000000 00000000

 

[wolfmankurd]

I don't think there is anywhere enough information for anyone to give you specific advice.

But the general idea of ntrboot fixing a brick is to use ntrboot to install boot9strap.

Then use boot9strap and luma3ds. Then get a godmode9 firm payload and the relevant CTRtransfer file and use decrypt9 to do the CTRtransfer.

What you do from there is up to you.


Here is a guide on doing a region change and keeping tickets https://3ds.guide/9.2.0-ctrtransfer.html that's basically the same procedure.

 

[DocKlokMan]

So I need to know a couple of things. First off, I got the worst type brick which is the bootrom error. (I was restoring a backup which must of got corrupted or the storage device and it managed to kill it. aka brick 3ds) So, If I use ntrboothax it should fix the boots. And then restore using a backup with a good storage device should fix it entirely right? (i'm assuming that bootrap9 only fixes boots, and doesn't fix file errors. which is why I would need to restore a good backup for the files)

Yes, I have researched this extensively and am in the process of making a revival script that works in GodMode9 to automate it all. However, to answer your questions in more detail:

NTRBootHax will get you past the BootROM error and let you into ARM9 payloads like GodMode9, Decrypt9, SafeB9SInstaller, etc. The BootROM error won't be fixed though until you restore the NAND into working order, even if you try to install Boot9Strap to the console. Restoring your NAND depends on if you have a backup from when it was working. If you have a backup, you can try restoring that backup using GodMode9. If you don't, you can attempt a CTRNAND transfer using Decrypt9 and using either the 9.2 or 11.3 images floating around. If that fails to revive the console then I may have something released by then to help. It's currently in testing.

 

[Deleted User]

Yes, I have researched this extensively and am in the process of making a revival script that works in GodMode9 to automate it all. However, to answer your questions in more detail:

NTRBootHax will get you past the BootROM error and let you into ARM9 payloads like GodMode9, Decrypt9, SafeB9SInstaller, etc. The BootROM error won't be fixed though until you restore the NAND into working order, even if you try to install Boot9Strap to the console. Restoring your NAND depends on if you have a backup from when it was working. If you have a backup, you can try restoring that backup using GodMode9. If you don't, you can attempt a CTRNAND transfer using Decrypt9 and using either the 9.2 or 11.3 images floating around. If that fails to revive the console then I may have something released by then to help. It's currently in testing.

ok coolo. Its good that I do have a backup from 11.2 Which would be a good backup. Thanks for the info.