Hacking Homebrew Help!!! my 3ds is broken (i think)

[QwerpTz]

Help me please i can launch luma 3ds and godmode9 but my system does not work when i try to load the main os (I REPEAT LUMA AND GM9 WORKS)
please help i have a blue light that goes on forever and no sound

 

[woolywoods]

This is actually a surprisingly common problem. Could you describe what it was that you did before it broke? The fix really depends on what happened.

 

[QwerpTz]

This is actually a surprisingly common problem. Could you describe what it was that you did before it broke? The fix really depends on what happened.

i followed a clickbait tutorial that told me to delete the sys folder (2)

 

[woolywoods]

This is out of my area of expertise- maybe change the thread title to "Deleted my SYS file, how to recover?" People who have experience with that could help that way

 

[Dudee15]

i followed a clickbait tutorial that told me to delete the sys folder (2)

the Nintendo 3DS folder?

 

[godreborn]

If that's on the nand, maybe a ctrnand transfer?

 

[KleinesSinchen]

i followed a clickbait tutorial that told me to delete the sys folder (2)

I'd like to see that. Please share the link.


I don't think CTRTransfer (standard) will solve the issue since
[1:] SYSNAND CTRNAND:/ro/sys
[1:] SYSNAND CTRNAND:/rw/sys
contain console-unique data.

Also: It is very hard to miss the warning or "accidentally" delete unique data with GodMode9.



The HWCAL0.dat and HWCAL1.dat files in "ro" aren't needed to successfully boot (should be restored nevertheless)
===============

The fastest (and in my opinion easiest) way to repair the damage is mounting a NAND backup with GodMode9 and copy the missing folders from there to CTRNAND. The data is also part of the embedded essentials backup GodMode9 writes to NAND (named differently).

Thankfully I've never been in the situation requiring CTRTransfer or CTRTransfer Type D9, but the latter one might be an option here. In any case create a NAND backup before trying any radical attempts like CTRTransfer. Yes, a bricked state is worth backing up.

##########################################################
# If the entire setup was deleted, lost, or missing #
# vital NAND files, the backup 'essential.exefs' will #
# be used to create a new setup or individually restore #
# any of these five if needed. #
# frndseed | LocalFriendCodeSeed_B #
# hwcal0 | HWCAL0.dat #
# hwcal1 | HWCAL1.dat #
# movable | movable.sed #
# secinfo | SecureInfo_A / SecureInfo_B #
##########################################################

(The formatting is strange since the forum throws away excess whitespaces and using "[pre] [/pre]" resulted in unneeded newlines.)

 

[QwerpTz]

I'd like to see that. Please share the link.


I don't think CTRTransfer (standard) will solve the issue since
[1:] SYSNAND CTRNAND:/ro/sys
[1:] SYSNAND CTRNAND:/rw/sys
contain console-unique data.

Also: It is very hard to miss the warning or "accidentally" delete unique data with GodMode9.
View attachment 300446 View attachment 300447 View attachment 300448


The HWCAL0.dat and HWCAL1.dat files in "ro" aren't needed to successfully boot (should be restored nevertheless)
===============

The fastest (and in my opinion easiest) way to repair the damage is mounting a NAND backup with GodMode9 and copy the missing folders from there to CTRNAND. The data is also part of the embedded essentials backup GodMode9 writes to NAND (named differently).

Thankfully I've never been in the situation requiring CTRTransfer or CTRTransfer Type D9, but the latter one might be an option here. In any case create a NAND backup before trying any radical attempts like CTRTransfer. Yes, a bricked state is worth backing up.

(The formatting is strange since the forum throws away excess whitespaces and using "[pre] [/pre]" resulted in unneeded newlines.)

i tried to do CTRTransfer but after i could not boot into os

 

[retrospect]

i followed a clickbait tutorial that told me to delete the sys folder (2)

That folder is on sysNAND right? Didn't you back-up sysNAND when you first hacked your console?

 

[KleinesSinchen]

i tried to do CTRTransfer but after i could not boot into os

*Sigh* It will not boot without 1:/rw/sys/SecureInfo_A or 1:/rw/sys/SecureInfo_B and standard CTRTransfer probably doesn't cover this. CTRTransfer Type D9 on the other hand should.

Step 1: Backup the currently bricked status (I hope you already did this before attempting CTRTransfer)
Step 2: Restore the missing file(s).

Possibility A)​

Mount a previous, intact NAND image with GodMode9 and copy the missing folders to the correct location. No, I'm not going to walk you through that. I assume using the copy+paste file manager functions of GodMode9 is not hard but self-explanatory. It will ask for lvl1permissions, maybe even lvl2 permissions – that is okay. GodMode9 should not ask for lvl3 permissions (turning screen red).​

​

Possibility B)​

Navigate to [1:] SYSNAND CTRNAND/rw and create the folder sys if it is missing.​

Navigate to [S:] SYSNAND VIRTUAL and select essentials.exefs – mount this image and enter path.​

You will find a file named secinfo there. Copy it to [1:] SYSNAND CTRNAND/rw/sys​

Rename the file to SecureInfo_A and try to boot. If it doesn't work, rename it to SecureInfo_B and try again​

It will ask for lvl1permissions, maybe even lvl2 permissions – that is okay. GodMode9 should not ask for lvl3 permissions (turning screen red).​

Possibility C)​

Do a full NAND restore (safe) of a known good image from before the deletion of the sys folders.​

NAND restore will ask for lvl3 permissions. That is expected.​

You might have to run faketik in order to have your games re-appear.​

​

Possibility D)​

Run CTRTransfer Type D9. Read the full manual. It might require 11.5 CTRTransfer images (magnet links not in the guide anymore) if TurdPooCharger hardcoded the sha256 checksums into the script. When using CTRTransfer Type D9, GodMode9 will ask for lvl3 permissions. That is expected.​

Step 3: Once everything is working again, backup the NAND once again and store this on multiple locations.


Please do never try to uninstall CFW, especially when using Possibility B) (incomplete, other files missing). If possible, use Possibility A); fastest and not invasive. C) and D) seem are overkill in my opinion.

I'd still like to see that clickbait tutorial.

 

[QwerpTz]

the Nintendo 3DS folder?

No not on sd card

 

[QwerpTz]

i got the guy banned of yt an could not find it anymore so sorry about the tutorial part (btw i am gonna try it soon, but you saved me from 4 weeks of no sleep)

 

[CoolMe]

Do you still have the Luma3DS files on the sd card, or were they removed too? Also uncheck "disable Arm11 exception handlers" on Luma3DS menu if it's checked, and see if it shows the error once you boot it up again.

 

[QwerpTz]

*Sigh* It will not boot without 1:/rw/sys/SecureInfo_A or 1:/rw/sys/SecureInfo_B and standard CTRTransfer probably doesn't cover this. CTRTransfer Type D9 on the other hand should.

Step 1: Backup the currently bricked status (I hope you already did this before attempting CTRTransfer)
Step 2: Restore the missing file(s).

Possibility A)​

Mount a previous, intact NAND image with GodMode9 and copy the missing folders to the correct location. No, I'm not going to walk you through that. I assume using the copy+paste file manager functions of GodMode9 is not hard but self-explanatory. It will ask for lvl1permissions, maybe even lvl2 permissions – that is okay. GodMode9 should not ask for lvl3 permissions (turning screen red).​

​

Possibility B)​

Navigate to [1:] SYSNAND CTRNAND/rw and create the folder sys if it is missing.​

Navigate to [S:] SYSNAND VIRTUAL and select essentials.exefs – mount this image and enter path.​

You will find a file named secinfo there. Copy it to [1:] SYSNAND CTRNAND/rw/sys​

Rename the file to SecureInfo_A and try to boot. If it doesn't work, rename it to SecureInfo_B and try again​

It will ask for lvl1permissions, maybe even lvl2 permissions – that is okay. GodMode9 should not ask for lvl3 permissions (turning screen red).​

Possibility C)​

Do a full NAND restore (safe) of a known good image from before the deletion of the sys folders.​

NAND restore will ask for lvl3 permissions. That is expected.​

You might have to run faketik in order to have your games re-appear.​

​

Possibility D)​

Run CTRTransfer Type D9. Read the full manual. It might require 11.5 CTRTransfer images (magnet links not in the guide anymore) if TurdPooCharger hardcoded the sha256 checksums into the script. When using CTRTransfer Type D9, GodMode9 will ask for lvl3 permissions. That is expected.​

Step 3: Once everything is working again, backup the NAND once again and store this on multiple locations.


Please do never try to uninstall CFW, especially when using Possibility B) (incomplete, other files missing). If possible, use Possibility A); fastest and not invasive. C) and D) seem are overkill in my opinion.

I'd still like to see that clickbait tutorial.

Would this work if I deleted [0:] SDCARD, [1:] CTRNAND and [2:] SYSNAND TWLN?

 

[KleinesSinchen]

Would this work if I deleted [0:] SDCARD, [1:] CTRNAND and [2:] SYSNAND TWLN?

Please clarify the current status:
Forget about the SD. Everything on SD (but personal data like savegames) can be replaced. When starting GodMode9: What is missing, what is there?

It should look like:

Spoiler: this at startup

With the three drives:

• [1:]SYSNAND CTRNAND
• [2:]SYSNAND TWLN
• [3:]SYSNAND TWLP

Spoiler: And this inside CTRNAND

Ignore the folder fastboot3DS – that is only there if fastboot3DS is installed/used.

=======================
=======================
=======================

On startup it should not look:

Spoiler: like this (missing CTRNAND)

Spoiler: or like this (missing everything *ON* CTRNAND)