Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CIA build v2.4 gets stuck at white screens. #6

Open
TurdPooCharger opened this issue May 24, 2020 · 10 comments
Open

CIA build v2.4 gets stuck at white screens. #6

TurdPooCharger opened this issue May 24, 2020 · 10 comments

Comments

@TurdPooCharger
Copy link

TurdPooCharger commented May 24, 2020

Backstory
While trying to help this user figure out why his games are slowing down when played from R4i Gold 3DS Plus flashcart, I suggested that he try chainload booting from NTR Launcher instead of the HOME Menu game cart icon in order to run the games in TWL clock speed.

I managed to replicate his experience on my end in regards to Tony Hawk's Downhill Jam when racing against AIs. His slowdown issue is separate from this one.

Ultimately, I wanted to see if NTR Launcher could help speed up the game. I updated my installation from v2.2 → v2.4 by replacing the config file,

  • sdmc:/nds/NTR_Launcher.ini

and

FBI installing the release CIA,

  • NTR_Launcher_v2_4.cia

I was able to verify NTR Launcher was reading off its .INI after changing the animated and ntr splashes settings, but could not get my flashcart to run on this release.

My Setup

  • New 3DS XL
  • Sys 11.13.0-45U firmware
  • Luma3DS v10.1.3
  • Luma configuration, only this option selected: (x) Show NAND or user string in System Settings
  • R4i Gold 3DS Plus flashcart

Not related to this main github issue.

I downgraded back to v2.2, which was created using this method. When I played the Tony Hawk game with TWLCLOCK = 1, NTR Launcher did speed up gameplay in that AI racing scenario.

@Masamune3210
Copy link

couldn't get it to work on mine either, just hadn't made a issue yet because of work. all I get is a white screen as well

@dudamoos
Copy link

I have this issue as well. I have an old CycloDS Evolution flash cart. After looking around on the internet, I found a work-around. If you start NTR Launcher without the flash cart inserted, then insert it when it prompts you to insert a cartridge, then it will work correctly. I'm not sure what the cause of this is, but I would be glad to help debug it if anyone has any ideas.

@red9350
Copy link

red9350 commented Nov 4, 2020

I too have this issue, but the above workaround does not work for me

@Nogardrevlis
Copy link

Same Problem for me, I have an Original R4 Card ( Yep The First one Produced ) It Works fine with NTR Launcher 2.2 and 2.3 that I currently use since 2.4 stuck on White Screen.

@ApacheThunder
Copy link
Owner

ApacheThunder commented Mar 2, 2021

I got around to working on NTR_Launcher again. Test things again with the new legacy mode option. This should allow you to use carts that had worked in v2.2/v2.3 versions of NTR_Launcher but didn't work in 2.4. Note that Legacy mode won't support most of the advanced options like extended vram and such but the TWL clock speed option does work with it.

My R4 also did not work with 2.4. But I can confirm myself that my R4 does work with the legacy mode option enabled. Now that I got my 3DS back I was able to test things on it. Performance seems to be the same on it too. If your flashcart still doesn't work, confirm that it is making contact in the slot. With some 3DS models the original R4 for example has a PCB that is too thin and doesn't make contact with the slot pins. I had to insert paper under the PCB to make it work on 3DS.

@shad00m
Copy link

shad00m commented Mar 11, 2021

The 2.3 CIA works on my 3DS with a wood r4.
2.5 ends up in white/black screen with legacymode set to 1 - is there anything else i need to set in 2.5 for it to work?

@Nogardrevlis
Copy link

@shadb00m The same happens for me Original R4 and Wood Firmware, it seems neither the new loading code from 2.4 nor the legacy loading code from 2.5 likes the way the Wood Firmware works. 2.3 works flawless.

@RibShark
Copy link

RibShark commented Aug 17, 2021

I get dual white screens with a CycloDS Evo with 2.5 with legacymode set to 1 or 0. Also tested on 2.3 and the same happens there regardless of whether resetslot1 is set to 1 or not. TwilightMenu++ can boot the cart just fine.

EDIT: fork at https://github.com/unresolvedsymbol/TWLM_NTR_Launcher works fine

@dudamoos
Copy link

dudamoos commented Oct 26, 2022

I also have a CycloDS Evo and 2.5 didn't work for me. I think the 2.5 release might just be broken, though since it doesn't even show as "NTR Launcher" on the menu. 2.4 did work but I had to make sure the cart wasn't inserted until after I started NTR Launcher. I had to go all the way back to 1.99 (before the 3DS and DSi versions were combined) to get a version that didn't fall afoul of anti-piracy measures, and I still have to insert the cart after I launch it.

@ApacheThunder
Copy link
Owner

ApacheThunder commented Aug 16, 2024

3.0 introduces a new stage2 menu used to boot rom dumps of flashcarts or bootloaders extracted from their rom dumps. Also pushed recently a 3.1 update that finally got DSTwo to boot via the cart loader. Though still requires entering stage2 menu while the card is not inserted/reinserted.

Anyways give it another try and let me know how it goes. As for the op's original issue, please post a rom dump of the R4i Gold Plus and I can see if I can find a bootloader SRL embedded in their spoofed game to see if stage2 menu can get the card working. as this method worked for getting my R4 SDHC Gold Pro to boot which is a DSTTi "Demon" timebombed clone. That card had similar issue where it showed header CRC error. The new stage2 menu got around this. :D

You can contact me on Discord (apachethunder) if you want to send me the rom dump there as well as test the extracted bootloader if I find one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants