Hacking my DS Mode is Still bricked!

CodyWGamer · Feb 15, 2019

this is what has been happening since... not after i followed the guide from turbopoocharger but this is was has been happening...

TurdPooCharger · Feb 16, 2019

I. Don't use EmuNAND; disable EmuNAND.

Turn on the 3DS system, hold (SELECT) to access Luma3DS v9.1 configuration, and don't have this marked.

( ) Autoboot EmuNAND

Press (START) to save the settings.

II. Remove currently installed DSiWare and TWL_FIRM titles.

Use Delete Title And Ticket for these five (5) titles in FBI.

0004013800000102
- Old_3DS TWL_FIRM
- Version: 10864 (10.39.0)
- Product Code: CTR-P-CTAP
00048005484E4441
- DS Download Play
- Version: 1024 (1.0.0)
- Product Code: dlplay
0004800542383841
- Nintendo DSi™
- Version: 2048 (2.0.0)
- Product Code: DS INTERNET
0004800F484E4841
- Nintendo DS Cart Whitelist
- Version: 11264 (11.0.0)
- Product Code: <blank>
0004800F484E4C41
- TWL Version Data - v0
- Version: 0 (0.0.0)
- Product Code: <blank>

III. Add back those titles.

Download the first four (4)* from the above list using either:

A. System Settings → Other Settings → System Updates

or

B. Recovery Mode

* Online firmware update from Nintendo will not add back 0004800F484E4C41 - TWL Version Data - v0. This requires FBI to reinstall that single missing title.

or

C. FBI reinstalled these five (5) CIA files found at:

11.9.0-42U(Full).zip (bfed7c0d4e9b9dc40c2c2f7995ec7c54) from that darth site
- 0004013800000102.cia (1.64 MB - CRC32: 60103DAB)
DSi / DS functionality is broken after completing the guide
- DS Download Play - v1024.cia (437 KB - D74DA854)
- DS Internet - v2048.cia (1.25 MB - A48B2C7D)
- Nintendo DS Cart Whitelist - v11264.cia (382 KB - E1FAECFB)
- TWL Version Data - v0.cia (21.0 KB - 0B1E11EE)
  - DO NOT USE Old_3DS TWL_FIRM - v8817.cia because it's outdated.

IV. Clear extdata that may cause hang ups.

Clear Home Menu extdata
You can unwrap all the HOME Menu icons with Cthulhu.

V. NVRAM

Recover DS mode after an NVRAM "brick" (eg after using a DS Bricker)
There are open source *.3dsx and *.cia alternatives: 3DS_NVRAMtool

VI. Install a fresh example DSiWare game.

Look to that ISO site. Pick something like Zelda4Swords.

*********

If you do all of those Roman numerical steps and your DSi mode is still brick, what's left is CTRTransfer in Decrypt9WIP if you already tried CTRTransfer in GodMode9.
I advise that you don't jump ahead with Decrypt9WIP. While it does an amazing job fixing NAND issues, it will delete important files unlike it's newer counterpart GM9.

Using Decrypt9WIP requires care backing up those would-be deleted files and reinstalling them after its usage.

CodyWGamer · Feb 16, 2019

TurdPooCharger said:
I. Don't use EmuNAND; disable EmuNAND.

Turn on the 3DS system, hold (SELECT) to access Luma3DS v9.1 configuration, and don't have this marked.

( ) Autoboot EmuNAND

Press (START) to save the settings.

II. Remove currently installed DSiWare and TWL_FIRM titles.

Use Delete Title And Ticket for these five (5) titles in FBI.

0004013800000102

Old_3DS TWL_FIRM

Version: 10864 (10.39.0)

Product Code: CTR-P-CTAP

00048005484E4441

DS Download Play

Version: 1024 (1.0.0)

Product Code: dlplay

0004800542383841

Nintendo DSi™

Version: 2048 (2.0.0)

Product Code: DS INTERNET

0004800F484E4841

Nintendo DS Cart Whitelist

Version: 11264 (11.0.0)

Product Code: <blank>

0004800F484E4C41

TWL Version Data - v0

Version: 0 (0.0.0)

Product Code: <blank>

III. Add back those titles.

Download the first four (4)* from the above list using either:

A. System Settings → Other Settings → System Updates
or

B. Recovery Mode

* Online firmware update from Nintendo will not add back 0004800F484E4C41 - TWL Version Data - v0. This requires FBI to reinstall that single missing title.

or

C. FBI reinstalled these five (5) CIA files found at:

11.9.0-42U(Full).zip (bfed7c0d4e9b9dc40c2c2f7995ec7c54) from that darth site

0004013800000102.cia (1.64 MB - CRC32: 60103DAB)

DSi / DS functionality is broken after completing the guide

DS Download Play - v1024.cia (437 KB - D74DA854)

DS Internet - v2048.cia (1.25 MB - A48B2C7D)

Nintendo DS Cart Whitelist - v11264.cia (382 KB - E1FAECFB)

TWL Version Data - v0.cia (21.0 KB - 0B1E11EE)

DO NOT USE Old_3DS TWL_FIRM - v8817.cia because it's outdated.

IV. Clear extdata that may cause hang ups.

Clear Home Menu extdata

You can unwrap all the HOME Menu icons with Cthulhu.

V. NVRAM

Recover DS mode after an NVRAM "brick" (eg after using a DS Bricker)

There are open source *.3dsx and *.cia alternatives: 3DS_NVRAMtool

VI. Install a fresh example DSiWare game.

Look to that ISO site. Pick something like Zelda4Swords.

*********

If you do all of those Roman numerical steps and your DSi mode is still brick, what's left is CTRTransfer in Decrypt9WIP if you already tried CTRTransfer in GodMode9.
I advise that you don't jump ahead with Decrypt9WIP. While it does an amazing job fixing NAND issues, it will delete important files unlike it's newer counterpart GM9.
Using Decrypt9WIP requires care backing up those would-be deleted files and reinstalling them after its usage.

this one might be my last chance because the other one wont work either

CodyWGamer · Feb 16, 2019

CodyWGamer said:
this one might be my last chance because the other one wont work either

last chance failed.... i officially give up and my ds mode is clearly permanently bricked... I tried EVERYTHING and it just goes straight to sleep mode

TurdPooCharger · Feb 16, 2019

CodyWGamer said:
this one might be my last chance because the other one wont work either

So the completion of steps I-VI didn't work? I have to tell you upfront that I'm afraid about writing a guide using Decrypt9WIP. In the past, I recommended using that app when GodMode9 doesn't work. Due to the recent discovery where certain personal NAND files are deleted in D9WIP, I'm reluctant in writing that tutorial as I haven't 100% ascertain ALL the important & private files that needs attention before using it.

If you wish to try Decrypt9WIP, check back tomorrow as I try to determine the best approach without losing stuff.

CodyWGamer · Feb 16, 2019

i prefer not because i dont want to risk bricking my entire 3ds just to fix a non-recoverable ds mode....

TurdPooCharger · Feb 16, 2019

CodyWGamer said:
i prefer not because i dont want to risk bricking my entire 3ds just to fix a non-recoverable ds mode....

As long as you have prior made SysNAND *.bin image to recover or restore from, you will not brick the 3DS or permanently mess up.

It's just choreographing the exact steps where you fix your DS mode without forgetting to add back those NAND files. It's a little involved and a bit tricky with pre and post preparation in GodMode9 but not impossible to do. If you know how to use hotkey combos on a keyboard and file navigation with a mouse, it's not that difficult on the 3DS.

stevePlays · Feb 17, 2019

What you did with DS feature? Maybe you uninstalled tickets that are written purple and are you trying to apply cfw again with NTRBoot but if you have a nintendo ds,ds lite or dsi use these methods below

DS/DS Lite:
https://3ds.hacks.guide/flashing-ntrboot-(nds)

Nintendo DSi:
https://3ds.hacks.guide/flashing-ntrboot-(dsi)

Try one of these if there is no error happening in the process

TurdPooCharger · Feb 21, 2019

@CodyWGamer, update from our PM. I have no idea if the next idea will solve your o3DS bricked DSi mode. Since you tried installing those five (5) TWL_FIRM and DSiWare CIAS, clearing HOME Menu extdata, CTRTransfer with GodMode9, and do not have a previous made SysNAND *.bin image, all that we have left is CTRTransfer in Decrypt9WIP to fall back on.

The difference between GodMode9 and Decrypt9WIP in how they handle CTRTransfer is that:

GodMode9 will wipe out system titles found in the title folder and install a fresh set. Personal, private, and essential files like those in the data, dbs, private, ro, and rw folders are mostly left alone / kept in place.
Decrypt9WIP will pull copies of those files, full sweep wipe the entire CTRNAND drive clean, install a fresh set of everything from the CTRTransfer *.bin image, and then add back those files of yours.

While Decrypt9WIP is extremely effective at what it does, it also fails to copy and restore several important files like:

HWCAL0.DAt and HWCAL1.DAt from the 1:/ro/sys directory. These are hardware calibration files that make minor adjustments in how your LCDs are displayed and sensitivity of the 3D camera.
- While these two are not required for the 3DS to function, they do affect the image clarity. From personal observation, my n3DSXL was noticeably blurry and had dithering.
friendsave.bin, nnidsave.bin, seedsave.bin, nagsave.bin, etc. from the 1:/data/<ID0>/ directory. The NNID and friend list are two most important for most people.
cert.db, import.db, ticket.db, title.db, tmp_i.db, and tmp_t.db from 1:/dbs directory. These are the database files that keep track of certifications, titles, and tickets.
- If you purchased stuff from the Nintendo eShop, ticket.db will house your legit tickets.

Only the items configsave.bin, LocalFriendCodeSeed_B, movable.sed, and SecureInfo_A/B are kept. Very bare minimum.

Equipped with this rather uncommon and unsettling knowledge, you'll have to excuse my slowness and reluctance in posting those instructions until double checking each step. A mistake or misstep isn't too much of a worry because you'll be creating a SysNAND *.bin image beforehand as a precaution. The tricky part is making sure you copy all those missed files and adding them back before and after the CTRTransfer.

CodyWGamer · Feb 21, 2019

TurdPooCharger said:
@CodyWGamer, update from our PM. I have no idea if the next idea will solve your o3DS bricked DSi mode. Since you tried installing those five (5) TWL_FIRM and DSiWare CIAS, clearing HOME Menu extdata, CTRTransfer with GodMode9, and do not have a previous made SysNAND *.bin image, all that we have left is CTRTransfer in Decrypt9WIP to fall back on.

The difference between GodMode9 and Decrypt9WIP in how they handle CTRTransfer is that:

GodMode9 will wipe out system titles found in the title folder and install a fresh set. Personal, private, and essential files like those in the data, dbs, private, ro, and rw folders are mostly left alone / kept in place.

Decrypt9WIP will pull copies of those files, full sweep wipe the entire CTRNAND drive clean, install a fresh set of everything from the CTRTransfer *.bin image, and then add back those files of yours.

While Decrypt9WIP is extremely effective at what it does, it also fails to copy and restore several important files like:

HWCAL0.DAt and HWCAL1.DAt from the 1:/ro/sys directory. These are hardware calibration files that make minor adjustments in how your LCDs are displayed and sensitivity of the 3D camera.

While these two are not required for the 3DS to function, they do affect the image clarity. From personal observation, my n3DSXL was noticeably blurry and had dithering.

friendsave.bin, nnidsave.bin, seedsave.bin, nagsave.bin, etc. from the 1:/data/<ID0>/ directory. The NNID and friend list are two most important for most people.

cert.db, import.db, ticket.db, title.db, tmp_i.db, and tmp_t.db from 1:/dbs directory. These are the database files that keep track of certifications, titles, and tickets.

If you purchased stuff from the Nintendo eShop, ticket.db will house your legit tickets.

Only the items configsave.bin, LocalFriendCodeSeed_B, movable.sed, and SecureInfo_A/B are kept. Very bare minimum.

Equipped with this rather uncommon and unsettling knowledge, you'll have to excuse my slowness and reluctance in posting those instructions until double checking each step. A mistake or misstep isn't too much of a worry because you'll be creating a SysNAND *.bin image beforehand as a precaution. The tricky part is making sure you copy all those missed files and adding them back before and after the CTRTransfer.

alright i guess we can give this a shot... this may be my last chance/hope for my ds mode... but if anything DOES go wrong and my 3ds DOES brick i do have a flashcart with NTRBoot and a sysnand backup and a magnet so....

TurdPooCharger · Feb 21, 2019

CodyWGamer said:
alright i guess we can give this a shot... this may be my last chance/hope for my ds mode... but if anything DOES go wrong and my 3ds DOES brick i do have a flashcart with NTRBoot and a sysnand backup and a magnet so....

While this isn't necessarily, it's recommended you do this on a second or spare SD card if you have one. This is so you can leave alone your main setup. A minimum card size of 4 GB is required, although 8 GB and bigger is fine.

Preferably using a different SD card and since this is for an o3DS, verify the switch is not in the LOCK position.
Copy everything off the SD card onto a computer.
Reformat the SD card in FAT32 + 32 KB cluster size with either Windows File Explorer. If it's bigger than 32 GB, use guiformat.
Full Write + Verify the empty SD card with H2testw. Unless you're using the main SD card that was already previously checked before, do not skip this step.
- It is crucial that the SD card that will be used is 100% functional to prevent bricking.
If the card passes, delete the *.h2w test files. If an hardware error was detected, replace the card and go back to step 1.
Build a test setup using the CFW starter kit found here. Hold off from borrowing or using files from your main setup.
Insert the SD card into the 3DS, turn on the system, and hold (SELECT) to access Luma3DS v9.1 configuration.
- Choose only (x) Show NAND or user string in System Settings.
Press (START) to save the settings, and hold (START) to access Luma3DS chainloader.
Update to the latest boot9strap v1.3 if you haven't already. Do so anyway to ensure your o3DS is indeed using B9S v1.3.
- SafeB9SInstaller → button combo → <A> to continue.
- If you mistakenly run OpenFirmInstaller, this will instead install fastboot3ds v1.2 stable in place of boot9strap.
- For the sake of troubleshooting, stick to or flash it back to boot9strap if fastboot3ds was installed.
- Turn on the 3DS → hold (HOME) button to access fastboot3ds → [+] Boot from file... → sdmc:/luma/payloads/SafeB9SInstaller.firm
Update to the latest 3DS firmware 11.9.0-42U if you haven't already. Again, go through the motion of updating.
- HOME Menu → System Settings → Other Settings → System Update
- or, Recovery Mode
GodMode9 → (HOME) button → Scripts... → NANDManager → <X> Backup SysNAND → etc.
- For safety, this will backup the current SysNAND *.bin image at 0:/gm9/out.
Go to 0:/gm9/out/######_XX########_sysnand_000.bin.
- NAND image options... → Verify file.
  - You want NAND validation success.
- Calculate SHA-256
  - You want SHA verification: passed!
- These checks ensure the image is intact in case a SysNAND restore is required.
Turn off the 3DS and remove the SD card. If your SD card is 4 GB, cut and paste these two (2) files from the card onto the computer to claim back some free space.
- sdmc:/gm9/out/######_XX########_sysnand_000.bin → computer
- sdmc:/gm9/out/######_XX########_sysnand_000.bin.sha → computer
Download the CTRTransfer *.bin and *.sha image and place them at:
- sdmc:/files9/11.5.0-38U_ctrtransfer_o3ds.bin
- sdmc:/files9/11.5.0-38U_ctrtransfer_o3ds.bin.sha
Create this empty folder on the root of the SD card.
- sdmc:/1 - SYSNAND CTRNAND
Add a DSiWare game of your choice onto the card. For example,
- sdmc:/gm9/out/Zelda4Swords.cia
Insert the card back into the 3DS, turn on the system, hold (START) → Luma3DS chainloader → GodMode9.
Navigate in the [1:] SYSNAND CTRNAND directory. Press the (L)-shoulder button to highlight select yellow these exact seven (7) folders.
- data
- dbs
- fixdata
- private
- ro
- rw
- ticket
Press (Y) button to [CLIPBOARD] select these folders. See the bottom screen at the top-right corner.
- If a mistake occurred, press (SELECT) to reset the selection.
Back out from the drive using the (B) button. Go to the [0:] SD CARD ( )/1 - SYSNAND CTRNAND folder.
While in that empty folder, press (Y) again → Copy path(s).
- This will make a 1-to-1 copy of those folders with your personal files onto the SD card.
Press (START) to exit GodMode9 and hold (START) to enter Luma3DS chainloader.
Decrypt9WIP → SysNAND Options → CTRTransfer... → Auto CTRNAND Transfer → button combo → 11.5.0-38U_ctrtransfer_o3ds.bin → etc.
- Step #0: Optional NAND backup, Press <B> to skip and continue without backup
- You can skip the D9WIP step 0 because a SysNAND *.bin image was made from this guide's step 11.
- Step #1: .sha verification of CTRNAND image... will verify if the CTRTransfer *.bin image hash matches against the *.sha.
After the CTRTransfer, the 3DS firmware will be downgraded to 11.5.0-38U. Update it back to 11.9.0-42U with either System Update or Recovery Mode.
Here comes the litmus test. Install the DSiWare game of your choice. For example,
- FBI → SD:/gm9/out/Zelda4Swords.cia → Install CIA.
- If you have no particular DSiWare titles in mind, you can install NitroHax_v0.99.NTR.cia found in the cias folder.
- [Video Tutorial] How to Inject Homebrew Into Official App - Stealth Homebrew w/ Rosalina Menu
Unwrap and launch the DSiWare title from HOME Menu. Does it work?
- If launching NitroHax without a flashcart or DS game, you should be greeted with the message, "No cartridge detected Please insert a cartridge to continue!".

[TO BE CONTINUED]
Depending if DSiWare game works, we will continue restoring the rest of NAND files or resign that the DSi mode is truly broken for whatever reason. Here's hoping for the best of luck that we get a successful software repair.

CodyWGamer · Feb 21, 2019

alright im getting to it right now... im currently backing up my sysnand just in case...

EDIT: im also hoping you saw the video tho... so you can see what type of ds brick im currently in...

Zaphod77 · Feb 22, 2019

btw the trick to not getting ds mode bricked seems to be playing a real ds game before you hack. if you hack a system that has never played a legit ds cart, it will brick ds mode when you hack. but if you play one first, then things work, as long as you didn't need to do a ctrtransfer.

at least my experience.

CodyWGamer · Feb 22, 2019

Zaphod77 said:
btw the trick to not getting ds mode bricked seems to be playing a real ds game before you hack. if you hack a system that has never played a legit ds cart, it will brick ds mode when you hack. but if you play one first, then things work, as long as you didn't need to do a ctrtransfer.

at least my experience.

really? because using frogminer seems to use ds software lol

i also have played ds games before i hacked my 3ds

also TurdPooCharger I have made the discovery that might not be good... my TWLNAND is missing from FBI and godmode9 same with my TWLP (which that one doesnt matter...) meaning that explains why it would say error when i launch ds software... But if i use a cartridge it will have that white screen, sleep mode effect... Did i just dig an even worse hole than before?

TurdPooCharger · Feb 22, 2019

CodyWGamer said:
also TurdPooCharger I have made the discovery that might not be good... my TWLNAND is missing from FBI and godmode9 same with my TWLP (which that one doesnt matter...) meaning that explains why it would say error when i launch ds software... But if i use a cartridge it will have that white screen, sleep mode effect... Did i just dig an even worse hole than before?

Did you complete the guide in post #71 as instructed?

I don't understand. You don't have [2:] SYSNAND TWLN and [3:] SYSNAND TWLP in GodMode9?

If you see [2:] SYSNAND TWLN, or TWLNAND drive, this one is suppose to contain:

BOLD = folder | Courier New = file | <blank> = empty

import/

<blank>

progress/

<blank>

shared1/

<blank>

shared2/

0000

sys/

log/

inspect.log
inspect.log~
product.log
product.log~

TWLFontTable.dat

ticket/

<blank>

title/

0003000f/

.
.

00030004/

.
.

tmp/

es/

write/

<blank>

opera.ini

***

TWLP is just TWL PHOTO. Not as important.

CodyWGamer · Feb 25, 2019

TurdPooCharger said:
Did you complete the guide in post #71 as instructed?

I don't understand. You don't have [2:] SYSNAND TWLN and [3:] SYSNAND TWLP in GodMode9?

View attachment 158581

If you see [2:] SYSNAND TWLN, or TWLNAND drive, this one is suppose to contain:

BOLD = folder | Courier New = file | <blank> = empty

import/

<blank>
progress/

<blank>
shared1/

<blank>
shared2/

0000
sys/

log/

inspect.log
inspect.log~
product.log
product.log~
TWLFontTable.dat
ticket/

<blank>
title/

0003000f/

.
.
00030004/

.
.
tmp/

es/

write/

<blank>
opera.ini

***

TWLP is just TWL PHOTO. Not as important.

no i dont anymore... and i figured twlp wasnt important

TurdPooCharger · Feb 25, 2019

CodyWGamer said:
no i dont anymore... and i figured twlp wasnt important

Well, this is unexpected.

We must refer to the Grandmaster of 3DS troubleshooting,

♪ The amazing and wonderful, @Quantumcat! ♪

Trying to fix @CodyWGamer's DS(i) broken mode, he found his o3DS are missing SYSNAND TWLN and SYSNAND TWLP drives. They aren't visible directories in GodMode9 and FBI.

Quantumcat · Feb 25, 2019

TurdPooCharger said:
Well, this is unexpected.

We must refer to the Grandmaster of 3DS troubleshooting,

♪ The amazing and wonderful, @Quantumcat! ♪

Trying to fix @CodyWGamer's DS(i) broken mode, he found his o3DS are missing SYSNAND TWLN and SYSNAND TWLP drives. They aren't visible directories in GodMode9 and FBI.

Wow, sorry, I have no idea!! I think you long ago surpassed me at 3DS debugging. Sad for OP though if you don't know how to help

CodyWGamer · Feb 25, 2019

im so sorry for just wasting your guys time lol i didnt think it was gonna be this much of a nightmare lol

TurdPooCharger · Feb 25, 2019

Quantumcat said:
Wow, sorry, I have no idea!! I think you long ago surpassed me at 3DS debugging. Sad for OP though if you don't know how to help

@Quantumcat, I dread scenarios where one finds a problem with no known solution or answer.

@CodyWGamer, you should go buy a lottery ticket later this week. Maybe reverse the unlucky polarity and hit jackpot.

Gonna go in my bed and curl into ball.

CodyWGamer said:
~~im so sorry for just wasting your guys time lol~~ i didnt think it was gonna be this much of a nightmare lol

You have nothing to apologies for. Your case of missing TWL drives may be the first. I don't think any of us has ever heard about this.

Eh... I'll go pay a visit at discordapp to try digging around in what this particularity mean.

Hacking my DS Mode is Still bricked!

are you having the same problem?

Yes

No

yes but it's fixed

no i have a different ds mode problem...

Well-Known Member

Meh.

Well-Known Member

Well-Known Member

Meh.

Well-Known Member

Meh.

Well-Known Member

Meh.

Well-Known Member

Meh.

Well-Known Member

Well-Known Member

Well-Known Member

Meh.

Well-Known Member

Meh.

Dead and alive

Well-Known Member

Meh.

Similar threads

Popular threads in this forum