*_*_*_*_*_*_*_*_*_*_*_*_*_*_*

[trilleplay]

[kade-robertson]

[bad instructions removed]

[d0k3]

@kade-robertson - what you just suggested would lead to a brick. Be careful with such instructions.

@trilleplay - what legit reason is there to restore these backups other than a brick? Restoring these will be coming, via .gm9 script, and until then you'll have to wait. I could provide the instructions, but it's much too easy to do something wrong, so it's better to wait for a bit.

[kade-robertson]

@d0k3 So if you back up firm0 and immediately restore it you brick? Even if the files are identical? Why?

(Didn't mean to provide bad instruction, I did leave warnings in it though)

[james-d-elliott]

Pretty sure the backups are raw, GM9 expects them to be decrypted, so it encrypts them, meaning already encrypted data is encrypted again.

[kade-robertson]

Ah, OK. So if you were to copy over a decrypted firm0 it would have been fine? Since you can dump the .xorpads I imagine it's feasible the OP has a decrypted firm0.

[d0k3]

@kade-robertson - yes, that's the problem. The backups SafeB9SINstaller does are encrypted, while the access in GM9 is decrypted. These backups are encrypted for a reason, cause, if something actually goes wrong, these backups can easily be restored to the places they belong to (f.e. with a hardmod) and don't need to be reencrypted.

@trilleplay - look here. The hardmod GM9 scripts pack contains a revert_sb9si script (one for SB9SI pre 0.0.7, one for current). It is not recommended you use this if you made any bigger modifications to your system since you installed or if you even changed something about these backups in the meantime.

Other than this, this should work. I recommend you do a full NAND backup in GM9 before you run the script and verify (in the A button menu...) S:/firm0.bin before rebooting. Problems are highly unlikely, but if the verification fails, you can still restore that NAND backup.

Are you reverting to stock, A9LH or an earlier version of b9s? Cause, in the case of an earlier b9s version it is recommended to use SafeB9SInstaller instead. In the case of stock AND N3DS, you should also check sector0x96.bin. The correct SHA for that is:
82F2730D2C2DA3F30165F987FDCCAC5CBAB24B4E5F65C981CD7BE6F438E6D9D3
(enough if you check the first few numbers/letters)

Follow these instructions, if anything goes wrong restore the NAND backup you did earlier, and nothing can go wrong.

[d0k3]

These scripts restore FIRM0 / FIRM1 or revert to stock. Closing this now