Hacking RIP TWL-Firm

  • Thread starter Thread starter PrintHello
  • Start date Start date
  • Views Views 18,028
  • Replies Replies 64
I doubt it, I think the problem I am having is because the ctrnand transfer doesn't touch the TWLN (i think thats what its called) partition as TheCyberQuake said. So even if i restore to a nand backup, it isn't going to touch (or restore) the TWLN partition.
If you restore a FULL NAND backup, it WILL restore TWL partitions as well, I think. However, it's true that ctrtransfer doesn't touch TWL partitions at all.
Although the possibility seems low, if it's TWLN problem, then it's already damaged before you made your 2.1.0 nand backup.
 
  • Like
Reactions: PrintHello
So i changed over to corbenik (With the relevant firmware and twl files) to see if it was a problem with Luma, no change. Still a black screen loading cartridges and the error screen loading a flashcart. Guess its definitely my TWLN partition that has screwed up.

Edit: Updated from 9.2.0 to 11.0 and still no dice.
 
Last edited by PrintHello,
So i changed over to corbenik (With the relevant firmware and twl files) to see if it was a problem with Luma, no change. Still a black screen loading cartridges and the error screen loading a flashcart. Guess its definitely my TWLN partition that has screwed up.

Edit: Updated from 9.2.0 to 11.0 and still no dice.
Did you already try deleting the TWL system cia before doing the update, so it'll see it as missing and replace it?
 
Do a system format via system settings on your sysnand... sounds like the nds settings memory is corrupted...

Did a format, still not working.

Wow...Normmatt comes. ;) The problem will definately be resolved soon™.

soon™

Did you already try deleting the TWL system cia before doing the update, so it'll see it as missing and replace it?

No but I shall try that once i restore to 9.2.0

Does anyone know if it would be possible to run decrypt9 and dump the twln partition (of another 3ds) without installing a9lh or would i have to install a9lh, then dump the partition, and then remove a9lh again. (So as to leave the console in an unmodified state w/ all the data still intact)
 
Beautiful thanks
Unfortunately Things like Decrypt9 require arm9 exploits, which on OFW means you have to at least be 9.2. Anything above won't allow it. But you won't have to install A9LH, you just need to downgrade to 9.2, then you can run Decrypt9 from HBL even from OFW. So you won't even need to install emuNAND or anything, just the downgrade.
 
  • Like
Reactions: PrintHello
So I got my hands on dumps of a working O3DS's TWLN and TWLP partitions (I also backed up my original non-working ones just in case).
After flashing the working partitions over the top of the non-working ones (using partition inject w/ decrypt9), my 3ds will still not load ds games (But it didnt brick it so i guess thats a win?)

copying the files in from https://gbatemp.net/threads/a-few-questions-about-twln-twlp-partitions.421575/ results in...

nothing

Still the same as before, black screen on loading DS games. I am at a loss as to what could be the problem. Maybe my 3ds just wants to move on and leave its ancestors behind.

Interestingly though, mounting the images with OSFMount, there are a bunch of apps? in the title/00030004/ folder which are different between consoles but everything else seems to be the same, one of them I just googled 000300044b445956 seems to be some dsi related file, but that is as much as i can gather...

I'd be interested to see if there would be some way to run any of those .app files (or if it would be worthwhile to try and use the H&S injector to try and inject them just for fun)

Thanks anyway guys, I'll keep looking for the time being and post if I somehow fix this.

As a side note, am I correct in thinking that when a 3ds wants to go into 'ds mode' it sets some memory address and reboots, and when it reboots, the bootloader or whatever reads that and boots from the TWLN partition instead? Because if so, it doesn't look like my 3ds is hitting that reboot stage.
 
Could you make a ctrtransfer image from your good 3ds and then inject it into your bad one?
I still guess it's the fault of the public 9.2.0E ctrtransfer image.
 
yes, its in the same list of options as the auto ctrnand transfer

Will doing a CTRNAND transfer from a non-a9lh'ed 3ds remove a9lh?
Just making sure before i do anything stupid

Edit:
From the Decrypt9 readme.md
"
  • Auto CTRNAND Transfer: Automatically transfer a transferable CTRNAND image to this consoles NAND. Without A9LH installed, this will overwrite the FIRM0, FIRM1, CTRNAND. With A9LH installed, this will only overwrite CTRNAND. O3DS images can be transferred into N3DS consoles, but the NCSD header of the NAND may be overwritten.
"

Looks like im good to go
 
Last edited by PrintHello,
Will doing a CTRNAND transfer from a non-a9lh'ed 3ds remove a9lh?
Just making sure before i do anything stupid
afaik Decrypt9 detects whether you have A9LH installed or not and shouldn't overwrite FIRM0FIRM1 (where A9LH is installed) if it detects A9LH. Though this is something @d0k3 should verify.
 

Site & Scene News

Popular threads in this forum