Toggle sidebar

Hacking my DS Mode is Still bricked!

are you having the same problem?

  • Yes

    Votes: 15 26.8%

  • No

    Votes: 35 62.5%

  • yes but it's fixed

    Votes: 4 7.1%

  • no i have a different ds mode problem...

    Votes: 2 3.6%
  • Total voters
    56
Status
Not open for further replies.
CodyWGamer said:
same here lol, so back to the TwlightMenu, so u said ur ds bricked during the setup how is that?
Click to expand...

Well, more or less... I found out it had DS mode bricked when I went to try to install TWiLight menu...
But I wasn't even able to run it 1 time or anything...
If it wasn't for that, I wouldn't even find the issue...
 
so u TRIED to install it so did u get installed?​

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

and now im just having a huge flashback on that app and i think that is the reason

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

also keep in mind im just trying to see what the hell is wrong with our ds modes and why they dont work... so i cant help solve the problem

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

and if there WAS a solution then this thread wouldnt even exist XD
 
CodyWGamer said:
so u TRIED to install it so did u get installed?
and now im just having a huge flashback on that app and i think that is the reason
also keep in mind im just trying to see what the hell is wrong with our ds modes and why they dont work... so i cant help solve the problem
and if there WAS a solution then this thread wouldnt even exist XD
Click to expand...

Well, I managed to install the CIAs and run the TWiLight updater, after that, when I went to enter the main app to select the 3DS model, etc etc, that's when I found out the issue... I'm assuming the updater uses 3DS mode and not DS mode, since it works...
 
MDashK said:
If my information is correct, then yes.
AFAIK, ntrboot uses DS mode.
Hmm.... Now that I think about it... If I was able to enter that DS mode at boot to install CFW... Something along the installation got f*d up, somehow...
Click to expand...
Two different things.

"DS(i) mode" = rebooting into TWL_FIRM
"ntrboot" = launching software from an ntr(DS) cartridge instead of normal boot

For whatever reason the DS(i) mode fails on your devices: TWL_FIRM is not loaded when installing CFW with a flashcart. The software on the NAND is completely ignored.
3dbrew.org/wiki/Bootloader said:
Additionally, if the shell is closed and a special key combination (Start + Select + X) is held, boot9 will attempt to boot from an inserted NTR cartridge before booting from NAND.
Click to expand...
@CodyWGamer You never mentioned problems with your camera before…
I wonder if there is a connection between those two problems. A faulty camera can cause other "funny" issues; at least on the N3DSXL (black screens in normal mode, but working recovery mode).
 
This is quite an interesting read.

@CodyWGamer
I'm not sure if it would help, but I have xorpads and a few firmware dumps of an o3ds lying around. I could check (pm me) what kind of files and/or partitions are missing, corrupted or damaged in any way.
If this would return zero problems then this would be an indicator for a hardware problem.
I'm pretty skilled with that kind of stuff I did manual system transfers multiple times already.
 
GothicIII said:
This is quite an interesting read.

@CodyWGamer
I'm not sure if it would help, but I have xorpads and a few firmware dumps of an o3ds lying around. I could check (pm me) what kind of files and/or partitions are missing, corrupted or damaged in any way.
If this would return zero problems then this would be an indicator for a hardware problem.
I'm pretty skilled with that kind of stuff I did manual system transfers multiple times already.
Click to expand...

What would you need? xD
Just a NAND dump or some more specific files?
 
Last edited by MDashK,
KleinesSinchen said:
Two different things.

"DS(i) mode" = rebooting into TWL_FIRM
"ntrboot" = launching software from an ntr(DS) cartridge instead of normal boot

For whatever reason the DS(i) mode fails on your devices: TWL_FIRM is not loaded when installing CFW with a flashcart. The software on the NAND is completely ignored.

@CodyWGamer You never mentioned problems with your camera before…
I wonder if there is a connection between those two problems. A faulty camera can cause other "funny" issues; at least on the N3DSXL (black screens in normal mode, but working recovery mode).
Click to expand...
i never mentioned the camera app being broken because it wasn't that important to me
 
MDashK said:
Just tried this fix: https://gbatemp.net/threads/restore-sysnand-twlp-and-twln.482834/#post-7555009
No luck. DS mode still broken, even using NAND from a good 3DS doner... =\
Click to expand...
Turn on the 3DS and hold (SELECT) button to boot Luma3DS v9.1 configuration.
DS(i) mode does not work with EmuNAND. Ensure that your setup isn't using EmuNAND like this:
  • ( ) Autoboot EmuNAND
  • (x) Show NAND or user string in System Settings
Go in System Settings and look for Sys 11.9.0-42E.

***

Go to FBI → Titles.

If you're on 3DS firmware 11.9.0-42E and depending on old or new series (2/3)DS, the latest TWL_FIRM is:
  • 0004013800000102
    • Old_3DS TWL_FIRM
    • Version: 10864 (10.39.0)
    • Product Code: CTR-P-CTAP
  • 0004013820000102
    • New_3DS TWL_FIRM
    • Version: 10962 (10.45.2)
    • Product Code: CTR-P-CTAP

The other four (4) TWL system titles.
  • 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
    • Version: 0 (0.0.0)
    • Product Code: <blank>
 
Last edited by TurdPooCharger,
  • Like
Reactions: Quantumcat
TurdPooCharger said:
Turn on the 3DS and hold (SELECT) button to boot Luma3DS v9.1 configuration.
DS(i) mode does not work with EmuNAND. Ensure that your setup isn't using EmuNAND like this:
  • ( ) Autoboot EmuNAND
  • (x) Show NAND or user string in System Settings
Go in System Settings and look for Sys 11.9.0-42E.

***

Go to FBI → Titles.

If you're on 3DS firmware 11.9.0-42E and depending on old or new series (2/3)DS, the latest TWL_FIRM is:
  • 0004013800000102
    • Old_3DS TWL_FIRM
    • Version: 10864 (10.39.0)
    • Product Code: CTR-P-CTAP
  • 0004013820000102
    • New_3DS TWL_FIRM
    • Version: 10962 (10.45.2)
    • Product Code: CTR-P-CTAP

The other four (4) TWL system titles.
  • 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
    • Version: 0 (0.0.0)
    • Product Code: <blank>
Click to expand...
there's the man himself
 
MDashK said:
The system does not have emunand. autoboot setting is not enabled.
Title information is correct according to the post.
Click to expand...
You're the third person who has a broken DS(i) mode like this despite:
  1. not using EmuNAND
  2. have all updated TWL system titles
  3. tried CTRTransfer
  4. tried TWLTransfer (per AnalogMan's gm9 script)
    • CodyWGamer has does something similiar using verified good twlmbr.bin, twln.bin, and twlp.bin partitions.
  5. used NVRAM unbricker
  6. cleared HOME Menu extdata
The other person had a strangely broken touchscreen despite it perfectly working in 3DS mode.

Since we have nothing else to go by from a software standpoint, I would have to agree with @KleinesSinchen that the issue stems with something wrong at the hardware level.
Not directly related to broken DS(i) mode, but read here how a non-functioning camera can cause a 3DS system to partially not work with BSoD brick.
The 3DS systems don't have fail safes and will act erratically if any the daughter/accessory components are not properly communicating with the motherboard.

Because both Cody and you state that your 3DS cameras aren't working correctly, we can only guess this part somehow interferes with DS(i) mode.
Maybe booting to TWL_FIRM fails to call/handshake with camera, so it panics and boots back to HOME Menu.

The only way to test or rule out the camera would to be fix/replace it. That repair task is extremely difficulty due to the hinge often breaking the top LCD, speaker + volume, and camera flex cables..
 
TurdPooCharger said:
The only way to test or rule out the camera would to be fix/replace it. That repair task is extremely difficulty due to the hinge often breaking the top LCD, speaker + volume, and camera flex cables..
Click to expand...

If that's the case, then it's not worth the effort...
I'll just tell him to use his old DS Lite to play DS games and leave it has is.
 
  • Like
Reactions: Deleted member 473231
Status
Not open for further replies.

Site & Scene News

Go to forum More news

Popular threads in this forum

Homebrew  Twilight Princess Port Indev by Game of Tobi

Homebrew Homebrew game  Legend of Zelda: A Link to the Past 3DS Port

[Project Idea] Super Mario Galaxy Demake for Nintendo 3DS

[Project Idea] Splatoon Demake for Nintendo 3DS

Homebrew Misc Project  Looking for 3DS C++ Homebrew app developer

3DSCast -- A Podcast Focusing on the 3DS -- Launches Today

Hacking ROM Hack  System settings and Roms not launching

Gaming Homebrew Project  OcarinaCTRComposer - a .3gx cheat plugin for Zelda OoT3D