There isn't.Is there a screen shot function on luma?
I have a problem: So I finished installing a9lh and I have luma3ds working on the sysnand, basically im on section VI of this guide https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax) and the problem is that I need to make one final backup of my hacked sysnand BUT whenever I try to open OTPHelper it takes me directly to the CTR boot manager and therefore I am unable to make a backup, whats going wrong and can I fix this?
No so use NTR CFWIs there a screen shot function on luma?
I have a problem: So I finished installing a9lh and I have luma3ds working on the sysnand, basically im on section VI of this guide https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax) and the problem is that I need to make one final backup of my hacked sysnand BUT whenever I try to open OTPHelper it takes me directly to the CTR boot manager and therefore I am unable to make a backup, whats going wrong and can I fix this?
--------------------- MERGED ---------------------------
Edit: I remember deleting some stuff off my SD card to clean up some stuff so I'm guessing there's files required to be on the SD root but I dont know which ones I need/are missing
TLDR: OTPHelper doesnt open anymore and instead relaunches CRT Boot Manager
You need it for full pasta cfw, but I just needed mini pasta. I thought they were the same for a moment.Who said u needed it?
No u don'tYou need it for full pasta cfw, but I just needed mini pasta. I thought they were the same for a moment.
You can go ahead and delete it no probsI have a o3ds on 9.2 sysnand that was running rxtool and I installed Luma and I had no need to create EMUNAND as Rxtools already had one and luma continues to use that same one... my question is can I delete all the rxtools stuff like Rxtools.dat and the folder,etc would it affect my emunand in anyway since it was created by Rxtools and not luma
Do you use bootanim9? Or any boot loader other than the one built into luma? Tell us your exact set up and what error you get exactly or just black screen?
I use Menuhax w/o any boot loader. I used to use CTRBootManager, but I stop using it after learning that boot loaders cause problems with Luma3DS. When I load a GBA game, it just gives me a black screen. I have them installed on sysNAND and emuNAND.I'm not sure what to suggest then. DSiware and Smash are working, and your AGB_FIRM isn't patched, in theory it ought to be working. What happens exactly when you try to run your GBA games? you've tried more than one game I take it?
boot loaders only cause issues on arm9loaderhax. you can keep using CTRBootManager just fine.I use Menuhax w/o any boot loader. I used to use CTRBootManager, but I stop using it after learning that boot loaders cause problems with Luma3DS. When I load a GBA game, it just gives me a black screen. I have them installed on sysNAND and emuNAND.
Oh, maybe. I'll check when I get home.boot loaders only cause issues on arm9loaderhax. you can keep using CTRBootManager just fine.
have you by chance patched AGB_FIRM on sysnand as well?
Sorry about my almost-absence, basically personal stuff happened (not necessarily negative ones! ).
If anyone is interested, yesterday I pushed an update to my a9lh fork to merge screen init and non screen init stage2s into one, and to include a stripped down Luma for when there's no payload or no SD inserted (has just two patches, signatures and firm writes). https://github.com/AuroraWright/arm9loaderhax
I guess they are not the new pre-compiled one from the 19th?Sorry about my almost-absence, basically personal stuff happened (not necessarily negative ones! ).
If anyone is interested, yesterday I pushed an update to my a9lh fork to merge screen init and non screen init stage2s into one, and to include a stripped down Luma for when there's no payload or no SD inserted (has just two patches, signatures and firm writes). https://github.com/AuroraWright/arm9loaderhax