Homebrew Deleted something wrong and now 3DS wont boot

[TurdPooCharger]

The 3DS boots...kinda. I get a power on but the screens are still black.

EDIT: I got a crash when pressing the power button to turn off

1. Unless this is a n2DSXL, try the battery trick to reset the RAM.
   
2. Rename the Nintendo 3DS folder on the SD card to Nintendo 3DS (main).
3. Try booting to HOME Menu.

(A) If the 3DS boots to HOME Menu,

4a. Delete the (dummy) Nintendo 3DS folder and rename the Nintendo 3DS (main) back to Nintendo 3DS.
5a. Black screen on SysNAND boot
6a. Clear Home Menu extdata
​

-or-

(B) If the 3DS still produces the ARM11 error,

4b. Delete the (dummy) Nintendo 3DS folder and rename the Nintendo 3DS (main) back to Nintendo 3DS.
5b. Backup the current SysNAND for safety.

• Creating a NAND Backup

6b. Re-attempt 3DS firmware repair but this time with the alternative CTRTransfer (Type D9).

• Use the v1.4 of the script found attached below the post.

 

[lomgth]

1. Unless this is a n2DSXL, try the battery trick to reset the RAM.
   
2. Rename the Nintendo 3DS folder on the SD card to Nintendo 3DS (main).
3. Try booting to HOME Menu.

(A) If the 3DS boots to HOME Menu,

4a. Delete the (dummy) Nintendo 3DS folder and rename the Nintendo 3DS (main) back to Nintendo 3DS.
5a. Black screen on SysNAND boot
6a. Clear Home Menu extdata
​

-or-

(B) If the 3DS still produces the ARM11 error,

4b. Delete the (dummy) Nintendo 3DS folder and rename the Nintendo 3DS (main) back to Nintendo 3DS.
5b. Backup the current SysNAND for safety.

• Creating a NAND Backup

6b. Re-attempt 3DS firmware repair but this time with the alternative CTRTransfer (Type D9).

• Use the v1.4 of the script found attached below the post.

Well, none of this worked, so I think it might be a lost cause because I dont have the expertise to do all of this. I appreciate your help today and if I do this again, Ill know not to go deleting root files on my 3DS in gm9.

 

[Deleted-236924]

I'm fairly certain your SecureInfo_A is fucked. Try placing this at nand:/rw/sys/ and see if it helps.

 

[TurdPooCharger]

Well, none of this worked, so I think it might be a lost cause because I dont have the expertise to do all of this. I appreciate your help today and if I do this again, Ill know not to go deleting root files on my 3DS in gm9.

Alright, let me know if you wish to try fixing this again if or when you're more comfortable following the (Type D9)'s Instructions. If you can hold off a while, I am planning to release a v1.5 update of that script sometime this month which will have even better capabilities at fixing niche softbricks.

It's not getting released any sooner due to laziness revising the about page/tutorial/etc.

 

[Deleted-236924]

For what it's worth, this is (very nearly) the exact error I get when region code in SecureInfo is wrong.

R12, LR and PC are slightly different from yours, I suspect that this could be firmware version-related though because that 2DS is not quite on latest firmware, while my XL that's on 6.2.0 gets a very different error for the same thing.

 

[TurdPooCharger]

For what it's worth, this is (very nearly) the exact error I get when region code in SecureInfo is wrong.

Yours is an o3DS, right? On my n3DSXL, when I remove the SecureInfo_A|B, the 3DS creates a dummy version filled with all 00's. It'll only boot if the 3DS firmware region is JPN (region code = 00 at offset 0x100). Otherwise, the screens stay at pitch black.

I agree with @Ammako's assessment. From past experience deleting everything in the 1:/ drive and running standard CTRTransfer,
stuff like the HWCAL0.DAt, HWCAL1.DAt, movable.sed, SecureInfo_A|B, and LocalFriendCodeSeed_B from the essential.exefs are not restored. You would have to manually mount that EXEFS and restore them yourself if you know your way around basic file navigation, renaming, copying, and where these are suppose to be added back to.

The bare minimum for a 3DS to boot HOME Menu is intact copies of the title.db and import.db paired to the title folder and a compatible SecureInfo_A|B.

 

[Deleted-236924]

Yours is an o3DS, right? On my n3DSXL, when I remove the SecureInfo_A|B, the 3DS creates a dummy version filled with all 00's. It'll only boot if the 3DS firmware region is JPN (region code = 00 at offset 0x100). Otherwise, the screens stay at pitch black.

I agree with @Ammako's assessment. From past experience deleting everything in the 1:/ drive and running standard CTRTransfer,
stuff like the HWCAL0.DAt, HWCAL1.DAt, movable.sed, SecureInfo_A|B, and LocalFriendCodeSeed_B from the essential.exefs are not restored.

The bare minimum for a 3DS to boot HOME Menu is intact copies of the title.db and import.db paired to the title folder and a compatible SecureInfo_A|B.

Regular 2DS, yes. All of them generate a 00-filled SecureInfo_A on boot if secureinfo is missing.

Either way, it's worth a try to see if it helps. If it works then it's worth checking if essentials.exefs is there, so you could restore the original files. Otherwise you're kinda stuck with this and will need to keep cfw installed to use your 3DS.

 

[lomgth]

Alright, let me know if you wish to try fixing this again if or when you're more comfortable following the (Type D9)'s Instructions. If you can hold off a while, I am planning to release a v1.5 update of that script sometime this month which will have even better capabilities at fixing niche softbricks.

It's not getting released any sooner due to laziness revising the about page/tutorial/etc.

I'll be sure to message you in a month or so, just feeling defeated right now.