Nope. I can't guarantee the same safety from Brahma that I can guarantee from a9lh.No .3dsx Brahma-based loader?
Also, at first I thought you put one of Ridley's sprites from Super Metriod as the bottom-screen dragon.
That makes sense.Nope. I can't guarantee the same safety from Brahma that I can guarantee from a9lh.
That's not as simple as you may think (I'd almost say, impossible). 3DS type (N3DS / O3DS) can be recognized by the backup size (only N3DS is > 1GB). FW can only be recognized with a database of FIRM hash, and region needs to decrypt and extract a file from NAND. BUT: you can't look into NANDs that are not dumped from the console you are running Hourglass9 from, so identifying a different consoles NAND backup is out of question. So, that's that.
Honestly with a tool like this, im pretty sure the only way to brick is by installing a wrong nand dump. Even with a9lh this isnt possible though because you can always reinstall a valid dump. Unless theres something wrong with the program though, its pretty noob-proof.Oooooo I wanna test it out. I Want to see if I can find a way to brick. I gots a9lh so its ok.
I can believeHonestly with a tool like this, im pretty sure the only way to brick is by installing a wrong nand dump. Even with a9lh this isnt possible though because you can always reinstall a valid dump. Unless theres something wrong with the program though, its pretty noob-proof.
Well, and just try to flash a wrong / corrupted NAND dump. You will have a hard time, guaranteed. And you can recover from it via a9lh, even if you manage to do it.Honestly with a tool like this, im pretty sure the only way to brick is by installing a wrong nand dump. Even with a9lh this isnt possible though because you can always reinstall a valid dump. Unless theres something wrong with the program though, its pretty noob-proof.
Not possible, has already been brought up. We have no access to the real time clock.@d0k3 It would be cool to have an option to have the backup named with date.
- sysnand_20160525.bin
- emunand_20160525.bin
I put my backups straight in a folder named with date:
- \2016-05-25\sysnand.bin
- \2016-05-25\emunand.bin
But i can imagine some ppl just copy them in folders like \01\sysnand.bin \02\sysnand.bin etc...
Well...it's not that hard to find out..btw, on a non-a9lh console, it's two.Not possible, has already been brought up. We have no access to the real time clock.
--------------------- MERGED ---------------------------
By the way, to be fair, there is one way you can brick (irreparably that means) even with this. You'd need a pristine, uncorrupted, unchanged NAND dump (from your console, of course), and you'd need to use a hex editor to change something in one very specific place. Won't put this out, though, but anyone with a hardmod and some knowledge about the NAND structure can go figure.