Of course, your NAND backup and hard mod save the day!
...right? Of course no one should use unsafe hacks before seeing multiple verifications.
Of course, sysNAND and emuNAND need to be same region and sysNAND must have a lower firmware than emuNAND.
I thought it was an evidence.
Of course, your NAND backup and hard mod save the day!
...right? Of course no one should use unsafe hacks before seeing multiple verifications.
A ticket.db file from 9.5 isn't going to get along with 4.x very well. I'm not too surprised you bricked it doing that.
A ticket.db file from 9.5 isn't going to get along with 4.x very well. I'm not too surprised you bricked it doing that.
Heh, well it's a little late now, huh? But now I know for future reference. Guess my DSiWare is toast for good.
I took a peek in my SD card and noticed the extracted ticket.db that was used to inject is 0KB. I probably should have checked that first, but rxTools said A-Okay, so it didn't occur to me.
At least now I know?
Also, you can't just import the ticket.db from an emunand that was unlinked from sysnand. If you took it from a unlinked emunand and put in sysnand, you would also need to import the private.sed file as I believe the ticket file is encrypted/authenticated using part the KeyY string found there.
However it appears you didn't. Thus the console bricked when you imported the lone ticket.db file. Even if the tile wasn't 0KB, you probably would have bricked it anyways. Also, since you have to move the the private.sed file over you'd also have to replace the contents of the data folder found inside the fat16 ctrpartition. (which can now be injected directly now that rxTools fixed file injection. However it still does not inject ctrnand fat16 directly to sysnand. It will only import that partition to emunand)
So in the end even if what you did worked, you'd just end up with a reset sysnand that would have you re-entered settings and you'd still lose what ever SD content you installed including DSiWare.
Also, you can't just import the ticket.db from an emunand that was unlinked from sysnand. If you took it from a unlinked emunand and put in sysnand, you would also need to import the private.sed file as I believe the ticket file is encrypted/authenticated using part the KeyY string found there.
However it appears you didn't. Thus the console bricked when you imported the lone ticket.db file. Even if the file wasn't 0KB, you probably would have bricked it anyways. Also, since you have to move the the private.sed file over you'd also have to replace the contents of the data folder found inside the fat16 ctrpartition. (which can now be injected directly now that rxTools fixed file injection. However it still does not inject ctrnand fat16 directly to sysnand. It will only import that partition to emunand)
So in the end even if what you did worked, you'd just end up with a reset sysnand that would have you re-entered settings and you'd still lose what ever SD content you installed including DSiWare.
The Data folder contains important stuff like current NNID settings, extdata and save game data to system modules. If the console doesn't find valid files here, it essentially goes to a factory reset condition and would most likely toss your custom tickets.db file and installed stuff will vanish.
You can extract the ticket.db from your emuNAND and use funkycia with -personal option to make a legit (personal) CIA of your DSiWare. Then you install it to sysNAND with PBT-CFW.That sounds like a huge complicated mess and way over my head, to be perfectly honest.
All I wanted to do was get my DSiWare working again since I broke it from splicing my Sysnand and Emunand. Is there any way to do that once I get everything de-bricked?
You can extract the ticket.db from your emuNAND and use funkycia with -personal option to make a legit (personal) CIA of your DSiWare. Then you install it to sysNAND with PBT-CFW.
Ehh...depends on what you mean by linkedThere's a safemode on the 3DS ?
Do the NANDs need to be linked for that to work ?
Please excuse me while I head-desk and shout obscenities into the void.
...
Oh well, having the hardmod would have been a good idea sooner or later anyways.
I've read a few posts of people already having success with rxTools on 9.7 EmuNAND on O3DS.I'm a little afraid to.
Has anyone seen THIS yet? Does this break rxTools? Anyone tested?