Ah, it might be using the qtm module then. That complicates things. Can't wait to see if I can fix it.11.0 Luma3DS a9lh. The guy who tested it uses the same setup.
Ah, it might be using the qtm module then. That complicates things. Can't wait to see if I can fix it.11.0 Luma3DS a9lh. The guy who tested it uses the same setup.

It uses the 3 only New3ds modules, removing them from exheader still crashes on 3ds logo.Ah, it might be using the qtm module then. That complicates things. Can't wait to see if I can fix it.![]()


You can check if you want, but it probably won't be there.Mmmmm... running CTRAging from "New" 3DS in Original 3DS, ther"s something that prevents it use in Original 3DS like most New 3DS titles does, even New 3DS Heaalth & Safety app prevents running in Original 3DS in normal way, beetwen what module it use it may be more possible to make it running or not, but researching in it will be needed.
Also I have a Original Cosmo Black 3DS I use it regularly and is my principal console, but it is a launch unit before price drop and orginally it came with 1.0.0 and also I didn"t messed it with any CFW or similar only normal use with Official Firmware, maybe I try downgrading and dump a Nand backup to see if something is here?
Either it works on O3DS or it does not. This is not a simple flag (at least afaik), the tool itself accesses N3DS only stuff, which will lead to unexpected results on O3DS.It seems to be an endless loop, there might be a menu if you press a button, since there are more images in the romfs than the shown in the video. Maybe there are options there to system format or something, after it passes the tests.
@d0k3 @Reisyukaku Do you think it is possible to make ctraging work on O3DS by removing N3DS dependences?



There's a video of it on N3DS in the original post.If anyone got it to work, can there be any pictures/images?



Already checked, no new factory titles there. CTRAging is broken (ExeFS:/.code and RomFS both hosed).I would love tobrick an emunandtake a look at this as well. I have written way to much onto my nand to even consider looking on there for a valid anything. On another note, has anyone tried looking for this on that demo console that popped up a while ago? (it was like 2am when i read the thread, but i think they had a dump of the most relevant things, so theres a small chance it may be on there)
My exefs .code and exheader is fine (banner is corrupt but who cares). Romfs has a problem in level 3.Already checked, no new factory titles there. CTRAging is broken (ExeFS:/.code and RomFS both hosed).

My exefs .code and exheader is fine (banner is corrupt but who cares). Romfs has a problem in level 3.
...
Yes, from an original 4.5.0-10U XL. Version 02 according to NCCH 0x112.O3DS? I believe I have a copy of O3DS CTRAging somewhere that has a valid RomFS and ExHeader, but björked ExeFS.

