"Less than or equal 9.2", so which one minimum?--------------------- MERGED ---------------------------
it's will not work. you need FW <=9.2.
"Less than or equal 9.2", so which one minimum?--------------------- MERGED ---------------------------
it's will not work. you need FW <=9.2.
That depends on which CFW you are using to launch SysNAND.Does Decrypt9 not work if you try to launch it after accessing your homebrew channel using Yellow8's hblauncher loader? It never works for me if I use Yellow8's hblauncher loader through my sysnand and then try to boot Decrypt9. It cycles through a red screen. If I access it via my homebrew channel using CTRBootManager, it will load though.
Can't give you a definite answer on this, but most people would say it would work. If your EmuNAND is not heavily modified (f.e. by installing stuff to the system or modifying system apps), I think it should work.So what would happen if I were to use this tool to copy my 9.2 emunand over to my sysnand that is on 4.2? Would it brick it or be on 9.2 with no problems? Only asking because I have no way to update to 9.0-9.2 as sliderhax does not work on 4.X which means I can't use sysupdater..
Most likely you have reboot patches enabled, if you turn those off it should work fineDoes Decrypt9 not work if you try to launch it after accessing your homebrew channel using Yellow8's hblauncher loader? It never works for me if I use Yellow8's hblauncher loader through my sysnand and then try to boot Decrypt9. It cycles through a red screen. If I access it via my homebrew channel using CTRBootManager, it will load though.
Yes, you can make emuNAND and sysNAND backups no matter where you launch d9 fromDoes it matter if I don't load my sysnand first and then access Decrypt9? As long as Decrypt9 is loaded, I can make a sysnand/emunand backup right?

I can confirm launching from ctr9 works nowFixed test release (the screenshot is the old one cause nothing much changed interface wise):
![]()
This should be fixed (again, this stays dangerous, so have a NANDmod!):
Looking forward to your feedback!
- The .bin should work on A9LH now (I at least hope it does)
- You can also access the CTRNAND on A9LH, but not TWLN / TWLP and not EmuNAND - full access only via the more 'traditional' entrypoints
- NAND writing should be fixed now (have a NANDmod if you try it!)
Thank @cpasjuste for that, not meI can confirm launching from ctr9 works now![]()

Yes, sysnand ctrnand and sdThank @cpasjuste for that, not me. You only have access to CTRNAND and SD, right?

Yes, sysnand ctrnand and sd
@Svaethier what console are you using this on? O3DS or N3DS?I only see sd card available upon startup. Am i missing something? (from a9lh).

http://i.imgur.com/9b5KWbC.jpg@Svaethier what console are you using this on? O3DS or N3DS?
And, @Shadowtrance, if the CTRNAND doesn't show up... this uses a new method of NAND CTR calculation, which should in theory work anywhere. The routines were provided by Normatt. There are two things that you can try... (1) compile Decrypt9WIP from current source, run from A9LH (you need to change the framebuffer offsets first, sorry) and try dumping FIRM0 / FIRM1 or CTRNAND. Does it work? (2) try running GodMode9 via another entrypoint. Still the same problem?
SD card only, again? :/ I'll need to ask Normatt...it's works on my mew 3ds too. Through Ctr Boot Manager9
![]()


n3ds 10.6 sysnand a9lh.@Svaethier what console are you using this on? O3DS or N3DS?
And, @Shadowtrance, if the CTRNAND doesn't show up... this uses a new method of NAND CTR calculation, which should in theory work anywhere. The routines were provided by Normatt. There are two things that you can try... (1) compile Decrypt9WIP from current source, run from A9LH (you need to change the framebuffer offsets first, sorry) and try dumping FIRM0 / FIRM1 or CTRNAND. Does it work? (2) try running GodMode9 via another entrypoint. Still the same problem?
EDit: Shadowtrance, wait, what FW are you on and what console type is this?
