It can yes, with a NAND backup or a CTRNAND transfer from GodMode9.Hello everyone
Sorry for my poor english, I've a Old3DSXL with a BSOD. I wanted to know if with NTRBoot I can fix this brick.
Thanks for help
Depends on how it was bricked, but probably.Hello everyone
Sorry for my poor english, I've a Old3DSXL with a BSOD. I wanted to know if with NTRBoot I can fix this brick.
Thanks for help
About booting straight into an emuNAND - how would the emuNAND be created? Wouldn't it normally be a copy of sysNAND? But if there's no sysNAND....?Depends on how it was bricked, but probably.
Even if the NAND is faulty, you can technically boot Luma3DS from ntrboot and have it boot right into an emuNAND, you don't even need a NAND chip installed in the 3DS.
Of course, that's not recommended. You'd have to use the magnet trick every time you turn on the 3DS.
If the NAND chip itself is not faulty you should be able to install B9S on it using ntrboot.
If there's no sysNAND, then you have to ctrtransfer.About booting straight into an emuNAND - how would the emuNAND be created? Wouldn't it normally be a copy of sysNAND? But if there's no sysNAND....?
But returning back to the question. How can one do a ctrtransfer in a faulty nand? This question has also bugged me ever since I read one like this.If there's no sysNAND, then you have to ctrtransfer.
But some things would probably have to be obtained from another console to have online access, like LocalFriendCodeSeed_B and SecureInfo_A.
I've been wondering this too. It doesn't make all too much sense. If it's faulty, why can you fix it by reflashing sysnand? Or same with a removed nand?But returning back to the question. How can one do a ctrtransfer in a faulty nand? This question has also bugged me ever since I read one like this.
Sent from my SM-G950F using Tapatalk
But returning back to the question. How can one do a ctrtransfer in a faulty nand? This question has also bugged me ever since I read one like this.
Sent from my SM-G950F using Tapatalk
I meant ctrtransfer to emuNAND.I've been wondering this too. It doesn't make all too much sense. If it's faulty, why can you fix it by reflashing sysnand? Or same with a removed nand?
But how can you create the emuNAND partition to begin with, with no working sysNAND?I meant ctrtransfer to emuNAND.
That's the easy part. Really all you should need is unpartitioned space at the beginning of the card that's of the right size. If that's not enough for GM9 or similar to recognize it, then a new tool might need to be written. One will be written if needed.But how can you create the emuNAND partition to begin with, with no working sysNAND?
So then GM9 creates a NAND partition on the card with a CTRNAND transfer? So is it not a full NAND then?That's the easy part. Really all you should need is unpartitioned space at the beginning of the card that's of the right size. If that's not enough for GM9 or similar to recognize it, then a new tool might need to be written. One will be written if needed.
Hmm, I didn't consider that. You probably do need a partition table for GM9 to know where to write the ctrnand backup.So then GM9 creates a NAND partition on the card with a CTRNAND transfer? So is it not a full NAND then?