No, it has nothing to do with arm9loaderhax. Your o3DSXL has a badly softbricked 3DS firmware.
This will need to be fixed with alternative or heavy duty CTRTransfer.
- CTRTransfer (Type D9) - CTRTransfer
Good luck!
This will need to be fixed with alternative or heavy duty CTRTransfer.
Good luck!
I don't understand what you mean by this.
- Click on the CTRTransfer (Type D9) link in post #41.
- Scroll down until you see the Table of Contents and then click on Instructions.
- There should be a list of languages. Click on Deutsch to google translate the page to German.
- Sie sollen jetzt das Wort Anleitung sehen. Finden das Kätzchen.
- ( You should now see the word Instructions/Manual (in german). Find the kitty. )
It's probably because you're using an ancient version of Luma on a newer firmware version. Do this (these are links):
I'm willing to bet this will fix the problem.
I'm willing to bet this will fix the problem.
I bet you will loose that bet. Read the first post of this thread. Luma 9.1 is compatible to latest firmware (and even arm9loaderhax Luma versions should support the 11.5 CTRTransfer image).
This case is not that easy.
Nobody on the forum can do it for you. You will need the 11.5 CTRTransfer image and the script. Then the only thing that helps is reading the manual.
The machine translation into German language is usable on first look (did not completely read it). Some parts sound awkward (and the machine translates parts it should not) but it is overall understandable.
I would. He says it's compatible but it's barely true. It'll boot but I was getting random crashes before I updated.
You're not supposed to restore sysnand with the <date>_<serial>_sysnand_###.bin image created from step 8 in the Instructions. That image is for safety in case the CTRTransfer (Type D9) crashes or fails to fix the 3DS firmware.
Restoring the image undoes all of the repairs done by CTRTransfer (Type D9) and returns the o3DSXL back to its current softbricked state.
Wrong image file. Wrong location.
The SysNAND *.bin image,
- <date>_<serial>_sysnand_###.bin (943.0 MB)
It's not used by CTRTransfer (Type D9). Keep this one at the sdmc:/gm9/out.
***
Put the CTRTransfer *.bin image files inside the sdmc:/gm9/in directory.
- 11.5.0-38E_ctrtransfer_o3ds.bin (757.8 MB)
- 11.5.0-38E_ctrtransfer_o3ds.bin.sha (33 bytes)
Go back and start from step 5. Make sure you add the other files.
EDIT - This is what the SD card should contain by the time you reach step 9.
Root of the SD Card
- 3ds/
- FBI.3dsx
- faketik.3dsx
- Cthulhu.3dsx
- gm9/
- in/
- 11.5.0-38E_ctrtransfer_o3ds.bin
- 11.5.0-38E_ctrtransfer_o3ds.bin.sha
- out/
- <date>_<serial>_sysnand_###.bin
- <date>_<serial>_sysnand_###.bin.sha
- scripts/
- CTRTransfer (Type D9).gm9
- GM9Megascript.gm9
- NANDManager.gm9
- in/
- luma/
- payloads/
- GodMode9.firm
- payloads/
- boot.3dsx
- boot.firm
Last edited by TurdPooCharger,
Yes. Use the CFW starter kit if you don't know where to put the files and folders at the right locations.
Edit - You will still need to add the ctrtransfer *.bin and *.sha files at the sdmc:/gm9/in directory.
Last edited by TurdPooCharger,
I copied everything from the CFW starter kit to the SD card out/ <date> _ <serial> _sysnand _ ###. bin <date> _ <serial> _sysnand _ ###. bin.sha, for me the folder is empty ??
everything else is exactly as you described
everything else is exactly as you described
CFW starter kit will not have a copy of your SysNAND *.bin & *.sha image.
These are created at step 8.
sdmc:/gm9/out/
- <date>_<serial>_sysnand_###.bin
- <date>_<serial>_sysnand_###.bin.sha
From step 6, you supply the CTRTransfer *.bin & *.sha image.
sdmc:/gm9/in/
- 11.5.0-38E_ctrtransfer_o3ds.bin
- 11.5.0-38E_ctrtransfer_o3ds.bin.sha
Don't confuse the ( SysNAND image ) for the ( CTRTransfer image ). They're separate sets of .BIN & .SHA files.
where do I get <date> _ <seriell> _sysnand _ '
<date> _ <serial> _sysnand_.bin.sha
--------------------- MERGED ---------------------------
what step can I take?
--------------------- MERGED ---------------------------
is it the nand fuse ?? because I have copied nand fuse as in the instructions in Pc, as fuse.must the two dates into the out folder ??
<date> _ <serial> _sysnand_.bin.sha
--------------------- MERGED ---------------------------
what step can I take?
--------------------- MERGED ---------------------------
is it the nand fuse ?? because I have copied nand fuse as in the instructions in Pc, as fuse.must the two dates into the out folder ??
Vor (BEFORE)
- sdmc:/gm9/out/ (nichts!)
Jetzt (NOW), Step 8
- GodMode9 → (HOME) button → Scripts... → NANDManager → <X> Backup SysNAND
Später (LATER)
- sdmc:/gm9/out/
- <date>_<serial>_sysnand_###.bin
- <date>_<serial>_sysnand_###.bin.sha
- No one is chatting at the moment.
-
-
-
@
Veho:
Once again I fell down the martial arts rabbit hole and am plumbing the murky depths of the internet's various martial arts and fighting crafts echo chambers. -
@
Veho:
I like to get up to speed on that every now and then, see what the newest high wisdom everyone is spouting nowadays.
-
@
Veho:
If you're not actively involved and only get up to speed every few years or so, you can see the tide of public opinion flapping worse than my dong while I'm skipping naked down a hallway.
-
-
-
-
@
Veho:
Like most forced updates, this one has terrible support and was very poorly received by the userbase.
-
-
-
-
-
-
@
FAST6191:
How do you know the giant wasn't on walkabout https://c8.alamy.com/comp/ADKT2C/ce...carving-in-dorset-uk-thought-to-be-ADKT2C.jpg -
@
Veho:
That's what I said, maybe they were just doing a recreation of the Cerne Abbas giant but didn't finish it in time.
-
-
-
-
-
-
-
@
Psionic Roshambo:
https://imgur.com/gallery/ZfBfPgk 100 million... Can think of better uses but OK lol -
-
