Thanks
Thanks
With "CIA Decryptor (CXI only)", Import succeeded in BBMFor CIAs to work on GW, you need to process them with "CIA Decryptor (CXI only)" instead of "CIA Decryptor (deep)", though.
Me? I haven't gotten any problems. The guy I responded to was trying to run from emunand. D9 doesn't work from emunand. Was trying to convince the person to just launch A9LH sysnand with L so that it boots 9.2 firm and to install Homebrew Launcher Loader to access Homebrew so that they didn't have to use browserhax. That way they didn't have to have internet each time they wanted to use Homebrew.Maybe. It was never designed to work from there. Can you tell me what issues you encountered?
Fw spoofing is not possible with this, sorry.With "CIA Decryptor (CXI only)", Import succeeded in BBMCan you add a firmware spoofing to this option?
The CIA file works on emuNAND 10.6.0 but not on emuNAND 9.2.0 (blocked on logo nintendo3DS).
Hahaay a wild @d0k3 appears! catch him!
Anyways, don't know if you already know or not buuuuuuuuuut.... we have some bad news.
With the latest test build, TWL stuff works, but CTR stuff is broken. As in can't dump files from sysnand etc etc.
Also, an update for the readme is needed for references to dukesrg.no-ip.org which should be changed to dukesrg.github.io
lol yeah on n3ds for me (and others), not sure if anyone tried o3ds. Might do that now actually.Haha.
Dammit, i broke CTR stuff on N3DS? Maybe we will need another test build, I'll take a look.
I assume you mean the minimal d9 i shared recently?I keep getting an error when restoring nand.bin saying it's too small but I can restore on the minid9. I'm running a n3ds with a9lh.
I did get this error with the .3dsx I used to use the brahma payload for it to workI assume you mean the minimal d9 i shared recently?
I have no idea how that's even possible as it's the same damn code as the usual D9. *confused*
Known bug, will be sorted out later. Just try again with the same input file.I keep getting an error when restoring nand.bin saying it's too small but I can restore on the minid9. I'm running a n3ds with a9lh.
Cheers for the answer I'll keep an eye on the GitHub repo thenKnown bug, will be sorted out later. Just try again with the same input file.
Hi @d0k3,
If I manually added the TWL Customer ID (taken from the Decrypt9.log or looking at screen output when decrypting stuff) to the end of my otp.bin with a hex editor, would this yield a valid otp0x108.bin?
It isn't needed now. all that stuff has been sorted out.By TWL Customer ID, you mean NAND CID, right ?
And an other question for @d0k3 : Is otp0x108.bin really needed ? I mean, if that's just otp.bin+nand cid, couldn't decrypt9 use this directly ?
It isn't needed now. all that stuff has been sorted out.![]()
Never? i don't know, maybe. atm though D9 doesn't need it.So no need to have it ? Never ? If we're not sure, I would like to make the file, in case I'll need it in the future![]()
Never? i don't know, maybe. atm though D9 doesn't need it.![]()
Stop asking questions and just wait a tiny bit longer. hahaWhy would it be needed exactly ? To be honest I don't even see what it really is. A decryption key ?
And to make it, do I take the NAND CID ? I'm not sure of what TWL Customer ID is...
Thanks for your answers![]()