Hacking RIP TWL-Firm

  • Thread starter Thread starter PrintHello
  • Start date Start date
  • Views Views 18,047
  • Replies Replies 64
If it did overwrite it though, you'd be at 9.2 and could easily install it again
That would depend what firmware the console you dump the transferable ctrnand from. If say you dump it from a 11.0 AND it overwrote A9LH, it would be game over. But from what I know it won't overwrite A9LH, because if it did people wouldn't be able to use a 9.2 ctrnand transfer after installing A9LH on 2.1 if they didn't have a backup.
 
  • Like
Reactions: Quantumcat
That would depend what firmware the console you dump the transferable ctrnand from. If say you dump it from a 11.0 AND it overwrote A9LH, it would be game over. But from what I know it won't overwrite A9LH, because if it did people wouldn't be able to use a 9.2 ctrnand transfer after installing A9LH on 2.1 if they didn't have a backup.
Oops my mistake, I thought you were still discussing a transfer from a 9.2 console.
 
Oops my mistake, I thought you were still discussing a transfer from a 9.2 console.
The 2nd console does have 9.2.0 now since I had to downgrade to run decrypt9 without installing a9lh.

Anyway I dumped the ctrnand image from it and installed it to mine and it results in the same black screen.
 
The 2nd console does have 9.2.0 now since I had to downgrade to run decrypt9 without installing a9lh.

Anyway I dumped the ctrnand image from it and installed it to mine and it results in the same black screen.
Curiouser and curiouser! Did you end up trying deleting the TWL system cia and then updating to 11.0? I guess there must be more to TWL mode than just that cia, or your other efforts would probably have worked already...
 
Curiouser and curiouser! Did you end up trying deleting the TWL system cia and then updating to 11.0? I guess there must be more to TWL mode than just that cia, or your other efforts would probably have worked already...

No I did not, I shall try that now.
 
I had this problem too - no ds game work. My o3ds started at 6.1 and did the 9.2 ctrtransfer. i only fixed it by going back to my 6.1 nand and update to 9.2 with sysupdater instead. Luma3ds wouldn't boot v6.1
 
I had this problem too - no ds game work. My o3ds started at 6.1 and did the 9.2 ctrtransfer. i only fixed it by going back to my 6.1 nand and update to 9.2 with sysupdater instead. Luma3ds wouldn't boot v6.1
Do you mean it's the problem of the public 9.2.0E ctrtransfer image? Or something is broken when doing a ctrtransfer from other's console (e.g. some ID/checksums mismatch between CTRNAND and TWLNAND)?
If it's the latter, I don't have any idea to fix, since OP doesn't have any original CTRNAND backup.:(
 
I had this problem too - no ds game work. My o3ds started at 6.1 and did the 9.2 ctrtransfer. i only fixed it by going back to my 6.1 nand and update to 9.2 with sysupdater instead. Luma3ds wouldn't boot v6.1

So maybe the ctrnand transfer process itself is what is breaking the ability to load ds games?

Do you mean it's the problem of the public 9.2.0E ctrtransfer image? Or something is broken when doing a ctrtransfer from other's console (e.g. some ID/checksums mismatch between CTRNAND and TWLNAND)?
If it's the latter, I don't have any idea to fix, since OP doesn't have any original CTRNAND backup.:(

I do have a 2.1.0 original, I just need a way to load up the 2.1.0 restore w/ a9lh installed, or to maybe directly go to the homebrew launcher. I read somewhere that one of the recent dev builds of a9lh can load up without an sd card in. Might be worth seeing if that will work.

Edit: Would the devmenu work on 2.1.0 with a9lh?

Edit 2: I dont think its something to do with that specific ctrtransfer though because I made my own from a working 3ds and it still wouldn't load ds games
 
Last edited by PrintHello,
Do you mean it's the problem of the public 9.2.0E ctrtransfer image? Or something is broken when doing a ctrtransfer from other's console (e.g. some ID/checksums mismatch between CTRNAND and TWLNAND)?
If it's the latter, I don't have any idea to fix, since OP doesn't have any original CTRNAND backup.:(

Yes i think that there is something wrong with the 9.2 ctrtransfer. Even updating it up to 11.0, still doesn't work.

--------------------- MERGED ---------------------------

So maybe the ctrnand transfer process itself is what is breaking the ability to load ds games?



I do have a 2.1.0 original, I just need a way to load up the 2.1.0 restore w/ a9lh installed, or to maybe directly go to the homebrew launcher. I read somewhere that one of the recent dev builds of a9lh can load up without an sd card in. Might be worth seeing if that will work.

Edit: Would the devmenu work on 2.1.0 with a9lh?

Edit 2: I dont think its something to do with that specific ctrtransfer though because I made my own from a working 3ds and it still wouldn't load ds games

can you use decrypt9 with Luma chainloading to restore it if you have a9lh?
 
Last edited by Guyver,
So maybe the ctrnand transfer process itself is what is breaking the ability to load ds games?

I do have a 2.1.0 original, I just need a way to load up the 2.1.0 restore w/ a9lh installed, or to maybe directly go to the homebrew launcher. I read somewhere that one of the recent dev builds of a9lh can load up without an sd card in. Might be worth seeing if that will work.
From what I've read, your 2.1.0 NAND backup is also made after ctrtransfer from a public image, so it's not "original" (corresponding to your TWL partitions). Am I wrong?

Edit: Would the devmenu work on 2.1.0 with a9lh?
As mentioned in #16, the easiest way to boot 2.1 under a9lh is corbenik.
EDIT: Sorry, I misunderstood the question. I don't know.

Edit 2: I dont think its something to do with that specific ctrtransfer though because I made my own from a working 3ds and it still wouldn't load ds games
It seems not that easy, :( again.
 
Last edited by orochi115,
From what I've read, your 2.1.0 NAND backup is also made after ctrtransfer from a public image, so it's not "original" (corresponding to your TWL partitions). Am I wrong?


As mentioned in #16, the easiest way to boot 2.1 under a9lh is corbenik.
EDIT: Sorry, I misunderstood the question. I don't know.


It seems not that easy, :( again.

I have multiple 2.1.0 backups, one of which is before the 9.2.0 ctrnand upgrade, I just have to figure out which one, which is why I want to try and boot up each 2.1.0 backup and try and run my ds cartridges on them, and if one of them works, I can upgrade to 6.something with my Prof. Layton 3ds game cartridge and possibly run luma from that.

Edit: in regards to corbenik, I thought there needed to be some modification to it for it to be able to run 2.1.0 (As you need to copy in a 9.2.0 firmware.bin file for it to run firmwares >= 9.2.0) but I may be wrong as I know diddly squat about how cfw works

Edit 2: Also just wanted to say a big thanks to everyone who has helped thus far, I think I have learnt so much over the past few days about 3ds hacking than I have in the 4+ years i've owned my 3ds
 
Last edited by PrintHello,
  • Like
Reactions: Quantumcat
I have multiple 2.1.0 backups, one of which is before the 9.2.0 ctrnand upgrade, I just have to figure out which one, which is why I want to try and boot up each 2.1.0 backup and try and run my ds cartridges on them, and if one of them works, I can upgrade to 6.something with my Prof. Layton 3ds game cartridge and possibly run luma from that.
I mean even before 9.2.0 ctrtransfer, it's already after 2.1.0 ctrtransfer.
Nevermind. Hopefully get good luck this time.
 
I mean even before 9.2.0 ctrtransfer, it's already after 2.1.0 ctrtransfer.
Nevermind. Hopefully get good luck this time.

True, but if that were the case with the 2.1.0 ctrtransfer then everyone who has downgraded to 2.1.0 should be having the same problem that I am having as that is a mandatory step in installing a9lh according to Plailect's guide. :unsure:
 
True, but if that were the case with the 2.1.0 ctrtransfer then everyone who has downgraded to 2.1.0 should be having the same problem that I am having as that is a mandatory step in installing a9lh according to Plailect's guide. :unsure:

well they wouldn't have that problem if they restored their original nand after the 2.1.0 ctrtransfer
 
  • Like
Reactions: PrintHello
well they wouldn't have that problem if they restored their original nand after the 2.1.0 ctrtransfer
Someone should do a poll of people who didn't make a NANDmin backup when prompted and instead used the 9.2 ctrtransfer, to see how many people have problems with DS games. Quite possibly there's loads of people who just haven't noticed since they don't play DS games often.
 
  • Like
Reactions: zoogie
Another problem I found when you don't backup NANDmin when downgrading to 2.1.0 and restore it later.

If your console is CHN, TWN or KOR, you don't (and never will) have a 2.1.0 ctrtransfer image for your region.
Thanks to d0k3's Decrypt9WIP, when there's region mismatch, it will do a region change for you automatically, when you haven't installed A9LH.
Wait... how does it do the region change? Not modifying previous SecureInfo_A as most think, but using the whole SecureInfo_A from the ctrtransfer image instead.
It's quite ok for most cases you will restore your NANDmin backup later, but...
After installing A9LH, doing a ctrtransfer will leave previous SecureInfo_A there even if region mismatch happens.
That means if you didn't backup NANDmin before downgrading, you'll never get your original SecureInfo_A back following the guide.
Well, I know that's a bit misleading, since your original SecureInfo_A is actually already backed up in sd:/files9 folder, and you can inject it back anytime.
However, the guide didn't mention it I guess most will ignore that at all.

What's the risk if you use a public SecureInfo_A? From my understanding, that somehow means you share the same console ID with others, may cause permanent ban or some other data problems.
And who in the hell owns a CHN/TWN/KOR console and didn't do a NANDmin backup? Maybe very very few. But it also happens when downgrading to 2.1.0 using a ctrtransfer image from another region.

Although it's corner case of the corner cases, it's still a problem there.
 
  • Like
Reactions: Quantumcat

Site & Scene News

Popular threads in this forum