Hacking Help with 3ds slow Sysnand boot

straubreyyy · Jan 5, 2019

Hey guys I need some help. I recently noticed that my old 3ds on cfw 11.5.0 with latest version of Luma had difficulty turning off and booting. Sotimes, when I turn the system off, the 3d and power led would stay on longer before dying. However, when that happens, the system would take longer than usual to boot (noticably longer around 10 mins or more). I tried doing a sysnand backup restore and it worked for a while but would then go back to the same problem. However, the problem became worse yesterday. The os would take an incredibly long time to boot (more than 1 hour I think). And whenever I access the settings or notifications it would result to a black screen upon going back to the home menu. This time, restoring sysnans, doing ctrtransfer, or deleting home extdata did not improve the situation. The 3ds has been working perfectly for the past 2 months. Nothing but game CIAs and CIAs with the guide were installed. Also, GM9 and Luma settings work perfectly. It's just the home menu that take incredibly loong to boot. Any help would be appreciated thanks

Hayato213 · Jan 5, 2019

Check your card with H2testw

straubreyyy · Jan 5, 2019

Hayato213 said:
Check your card with H2testw

Alright I'll try that out. But could it be sd card related? Because it also behaves the same without an sd card

Hayato213 · Jan 5, 2019

straubreyyy said:
Alright I'll try that out. But could it be sd card related? Because it also behaves the same without an sd card

If it not the SD card you might have a faulty NAND.

straubreyyy · Jan 5, 2019

Hayato213 said:
If it not the SD card you might have a faulty NAND.

Is this still possible to fix?

Hayato213 · Jan 5, 2019

straubreyyy said:
Is this still possible to fix?

You can try using a NAND backup if you have any, see if restoring a NAND backup or CTR Transfer fix your problem.

straubreyyy · Jan 5, 2019

Hayato213 said:
You can try using a NAND backup if you have any, see if restoring a NAND backup or CTR Transfer fix your problem.

Unfortunately, as stated in the post, ctr transfer and sysnand backup restore didn't improve the boot

Hayato213 · Jan 5, 2019

straubreyyy said:
Unfortunately, as stated in the post, ctr transfer and sysnand backup restore didn't improve the boot

Check your card first I guess, I'm out of ideas, @TurdPooCharger any ideas?

E1ite007 · Jan 5, 2019

Try H2testw as @Hayato213 suggested. It should be the 'cause of the problem.
If not, a lot of people in the past tried to defrag the NAND of the 3DS and it worked nice. The problem is that it's not recommended because of the nature of the 3DS NAND Chip, and also it requires a way to recover the console if any brick happens.

TurdPooCharger · Jan 5, 2019

Well, here goes my annoying step-by-step do-da.

Copy everything off your SD card onto a computer.
Reformat the card with SD Memory Card Formatter.
Reformat it again in FAT32 + 32 KB cluster size but this time with Windows File Explorer or guiformat (if bigger than 32 GB).
Reformat it once more in FAT32 + 32 KB cluster size using MiniTool Partition Wizard (free edition).

Format: FAT32
Cluster Size: 32 KB
Partition: Primary
Disk: MBR

MiniTool Partition Wizard Software Tutorial Guide

Delete Partition (for both partitions)
Initialize to MBR Disk -or- Convert GPT to MBR Disk (if it's in GPT Disk)
Rebuild MBR
Create a New Partition [ Create as: Primary | File System: FAT32 | Cluster Size: 32 KB ]

You guys might be curious as to why he should reformat the card three times with separate programs that do the same thing. Because @straubreyyy slow boot issue seems eerily similar to what I experienced messing with cluster/allocation size using MiniTool's pro version cluster size changer, he needs to go with the nuclear option. This is to rule out badly formatted card, which is super shitty in debugging because there's no obvious signs.

5. Full Write + Verify the empty card with H2testw. DO NOT SKIP THIS STEP.
6. If the card passes without error, delete the *.h2w test files.

However, if an error was reported, you may stop the test. Replace the hardware failed card and go back to step 1.

7. Build a custom firmware test setup using the starter kit found here. Hold off from using any files from your main setup for the time being.
8. Insert the card into the 3DS, turn on the system, and hold (Select) to access Luma3DS v9.1 configuration. Select only this option:

(x) Show NAND or user string in System Settings

9. Perform CTRTransfer with Decrypt9WIP. See instructions here.

FateForWindows · Jan 5, 2019

@straubreyyy Once you go through TurdPooCharger's steps, I'd also recommend doing a system update. It's not normally mandatory but newer updates, provided you are using current CFW releases, don't break anything (except for varying reports on NTR being broken, though it works fine for me).

straubreyyy · Jan 5, 2019

Thank you very much I will try this out. I'm currently testing H2testw to see if my card is indeed faulty. One question, how is performing CTR Transfer with Decrypt9WIP different from the Godmode9 method? And how safe is it?

TurdPooCharger · Jan 5, 2019

straubreyyy said:
Thank you very much I will try this out. I'm currently testing H2testw to see if my card is indeed faulty. One question, how is performing CTR Transfer with Decrypt9WIP different from the Godmode9 method? And how safe is it?

Decrypt9WIP will overwrite system titles whether or not they're already installed. GodMode9 has safety checks that prevent installing a title if the correct version is present. Decrypt9WIP is more thorough of the two, but is considered less safe for reasons the ~~older~~ longer established 3DS members and the dev himself behind the two apps know.

You resort to CTRTransfer with Decrypt9WIP only when GodMode9 fails to fix the 3DS firmware like what happened with Extrasklep's weirdly softbricked o2DS.

2DS softlocks or crashes when trying to launch anything from the home menu

Edit - As for why the CTRTransfer method in Decrypt9WIP never made its way into GodMode9, I'm assuming it's serious enough that if things are exactly right (ie, clean CTRTransfer image and 100% functioning SD card), you can super softbrick!? ← I dunno, this is my speculation.

wormdood · Jan 5, 2019

straubreyyy said:
And how safe is it?

its usually not considered safe (because as @TurdPooCharger said there is no safety checks in place) its also the most likely to work solution for most all firmware related problems... so its more like a last resort, although as long as you have the correct file(s) it will be fine . . . worst case scenario you install an image meant for the incorrect model 3ds family system and you brick as a result and then need a ntrboot compatible flashcard ($20 usd) to attempt to fix it (so make sure you get the correct files)

straubreyyy · Jan 5, 2019

UPDATW:

I was able to do a CTR Transfer using Decrypt9WIP. However nothing changed. I did get it to boot however after waiting for about an hour and the homescreen was telling me about the new features and the layout was back to the default layout as if it was a fresh update which tells me the CTR Transfer was a success. However, turning the system off and on again just shows a blackscreen and will probably take a while to load to home screen... Again

Sir Tortoise · Jan 5, 2019

Since payloads, the luma boot, and your SD card are all fine, it sounds like either an unfixable hardware issue, or your NAND has a problem. If I were you, I'd try making an emuNAND next. Look at https://3ds.hacks.guide/godmode9-usage and format the SD card (back it up first) as instructed, but create an emuNAND when prompted. Luma3DS can be configured to use the emuNAND by default.

TurdPooCharger · Jan 5, 2019

straubreyyy said:
UPDATW:

I was able to do a CTR Transfer using Decrypt9WIP. However nothing changed. I did get it to boot however after waiting for about an hour and the homescreen was telling me about the new features and the layout was back to the default layout as if it was a fresh update which tells me the CTR Transfer was a success. However, turning the system off and on again just shows a blackscreen and will probably take a while to load to home screen... Again

10. Updating B9S, to ensure your custom firmware is updated on both SD card and CTRNAND.

SafeB9SInstaller → button combo → etc. (to update to boot9strap v1.3)
GodMode9 → (Home) button → Scripts… → GM9Megascript → Scripts from Plailect’s Guide → Setup Luma3DS to CTRNAND → etc.

11. Recovery Mode, to update the 3DS firmware to 11.9.0-42.
12. Battery trick, to reset RAM. Boot the 3DS without the SD card and game cart.
13. If it's still slow, try @Sir Tortoise idea of EmuNAND.

GodMode9 → (Home) button → Scripts… → NANDManager → <RIGHT> Transfer Sys to Emu → etc.
- This will delete everything on the card. Add back the CFW starter kit afterwards.

14. With SD card inserted, turn on the 3DS, hold (Select) to get back to Luma3DS v9.1 configuration, and select both of these:

(x) Autoboot EmuNAND
(x) Show NAND or user string in System Settings

15. If boot time improves going to HOME Menu, check System Settings for the Emu 11.9.0-42[J/U/E] tag. The Emu means you're booting the 3DS firmware from the SD card.

16. Turn off ( ) Autoboot EmuNAND and check again in System Settings for the Sys. If you noticed that booting EmuNAND is indeed faster than SysNAND, this would indicate your onboard NAND is failing.

straubreyyy · Jan 5, 2019

Hey guys quick update. I tried to make an emunand however, I cant seem to get it to boot. I've left it on for long periods of time yet nothing's happening. Anything else I can try?

TurdPooCharger · Jan 5, 2019

straubreyyy said:
Hey guys quick update. I tried to make an emunand however, I cant seem to get it to boot. I've left it on for long periods of time yet nothing's happening. Anything else I can try?

Did you complete steps 10–14?

straubreyyy · Jan 7, 2019

Yes. I did manage to get the system to boot to homescreen however. Is it safe to update to try and see if that improves things?

Hacking Help with 3ds slow Sysnand boot

Member

Newcomer

Member

Newcomer

Member

Newcomer

Member

Newcomer

wierd avatar guy

Meh.

Well-Known Member

Member

Meh.

pirate booty inspector

Member

Well-Known Member

Meh.

Member

Meh.

Member

Similar threads

Popular threads in this forum