Homebrew HELP ME.

  • Thread starter Thread starter sergej
  • Start date Start date
  • Views Views 15,573
  • Replies Replies 99
I downloaded 11.5.0-38E_ctrtransfer_o3ds, copied to SD card gm9.hab then with god mode9, did ctrtransfer.
when I restart, the picture shows me again.

can it be something to do with arm9loaderhax ??
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.
Click on Deutsch to translate the Instructions from English → German.

Good luck!
 
  • Like
Reactions: Alexander1970
do I have to transfer the CTR (Type D9) to the SD card or GM9 ?? what further step do I have to take ??
 
do I have to transfer the CTR (Type D9) to the SD card or GM9 ?? what further step do I have to take ??
I don't understand what you mean by this.
  1. Click on the CTRTransfer (Type D9) link in post #41.
  2. Scroll down until you see the Table of Contents and then click on Instructions.
  3. There should be a list of languages. Click on Deutsch to google translate the page to German.
  4. 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):

  1. Upgrade to B9S (A9LH is no longer supported).
  2. Install the latest version of Luma.
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.

do I have to transfer the CTR (Type D9) to the SD card or GM9 ?? what further step do I have to take ??
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.
 
  • Like
Reactions: Alexander1970
have I heard until is I have to do ???
upload_2020-7-26_12-23-33.png
 
did everything as described until step 11, I press V #. # configuration start in the Luma3DS, then the error comes again ??

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

I also did that, as with the instructions
 

Attachments

  • IMG_1486.JPG
    IMG_1486.JPG
    2.9 MB · Views: 297
  • IMG_1485.JPG
    IMG_1485.JPG
    1.2 MB · Views: 297
  • IMG_1487.JPG
    IMG_1487.JPG
    1.8 MB · Views: 311
  • IMG_1488.JPG
    IMG_1488.JPG
    1.9 MB · Views: 261
would that go ?? Upgrade to B9S (A9LH is no longer supported). Install the latest version of Luma.

is it worth trying?
upload_2020-7-26_13-26-58.png
 
tried upgrading to B9S (A9LH is no longer supported). Install the latest version of Luma. When I press power I get to Luma 10.2, then I press start the same error occurs again ???
 
did everything as described until step 11, I press V #. # configuration start in the Luma3DS, then the error comes again ??

I also did that, as with the instructions
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.
 
  • Like
Reactions: Alexander1970
does it go to step 6 ??

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

at step 9, continue again ??
 
does it go to step 6 ??
Wrong image file. Wrong location.

The SysNAND *.bin image,
  • <date>_<serial>_sysnand_###.bin (943.0 MB)
, does not go in the sdmc:/gm9/in directory at step 6.

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)
at step 9, continue again ??
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
  • luma/
    • payloads/
      • GodMode9.firm
  • boot.3dsx
  • boot.firm
 
Last edited by TurdPooCharger,
  • Like
Reactions: Alexander1970
copy everything from CFW starter kit to SD card?
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
upload_2020-7-26_20-10-50.png
 
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

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.
 
  • Like
Reactions: Alexander1970
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 ??
 
where do I get <date> _ <seriell> _sysnand _ '
<date> _ <serial> _sysnand_.bin.sha

what step can I take?

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
 
i can't get into godmode9 anymore. press power button then start, then the same error comes again
 

Site & Scene News

Popular threads in this forum