Hacking Downgrading to 9.2.0?

[The Catboy]

well, I don't want to back it up, fix and possible format the old sd card, and then restore the old card from the backup, because it obviously didn't transfer something to the new card. so that same something might not transfer to the backup of the old sd card.
and sorry turd for not being clear. Ill try harder

If you still have your 32GB backup, then you are good to go. You need to reformat your 64GB, then run H2testw to test if the card is broken/fake

 

[Rdpruitt]

so you are saying that I should repair my old sd card if I have a backup?

 

[TurdPooCharger]

so you are saying that I should repair my old sd card if I have a backup?

Did you already reinsert your old (32 GB) SD card into your 3DS and see if all your games are still there and are working? If you cannot answer this one question, I'm going to presume your original copy of your entire custom firmware setup has been corrupted and none of it is recoverable.

If your data has somehow become damged on that old card, backing up your 3ds stuff or copying it over to the new SD card won't do you any good at this point.

All that you have left is to try salvaging your old card by doing an Windows error check and reformatting it again. You should not trust your old card again unless it passes the H2testw test inspection.

 

[Rdpruitt]

My old card still has all the data and everything still works. I have been trying to figure out how to use the 64gb card for weeks, and I still play on my 3ds often with my old card

 

[Quantumcat]

My old card still has all the data and everything still works. I have been trying to figure out how to use the 64gb card for weeks, and I still play on my 3ds often with my old card

So it is the 64GB card that doesn't work? Did you run it through H2testw with a full read and write check? https://3ds.guide/h2testw-(windows)

 

[TurdPooCharger]

My old card still has all the data and everything still works. I have been trying to figure out how to use the 64gb card for weeks, and I still play on my 3ds often with my old card

Excellent, we have a baseline of knowing you have intact (or least working) data on that old card. This is super good thing!

**

- You already established and verified that your new (64 GB) card has been checked against H2testw and formatted in FAT32 + 32 KB from your other thread.

- Your computer recognizes there's an error on that old card, but you have up til now, refused to scan and fix it due to concerns of corrupting or deleting your setup.

- Despite that error, you tried copying your setup from the old card onto the new card. Your new card with the copied setup does not work with your New 2DS XL.

- You also checked that your old card is running on SysNAND and not EmuNAND/redNAND.

**

I think we have the complete picture.

First possibility (kinda sucky): The new card was formatted with a GPT partition table instead of the needed MBR one. Try reformatting that new card again with MiniTool Partition Wizard. As seen from your other thread screenshot, do Select Delete All Partitions, Rebuild MBR, Create [File System: FAT32, Cluser Size: 32 KB], and Apply.

Second possibility (dreadful): Your old card is meta-stable with an improper allocation table. Your computer cannot verify some of your file(s) as they've failed their checksum, meaning those files in question have somehow changed. This can happen because of incomplete read and write from power loss or your old card derped during normal usage. Another likely cause is that the card's flash memory NAND cells containing parts of those files have failed.

As for the second possibility, one of the things you should do is back up all your game saves and extdata through Checkpoint and copy them over to your desktop (look in the 3ds/checkpoint directory). If you try using Windows error checker, there's a very real possibility it will reformat the entire card leaving you to lose everything.

Try building your setup from your new SD card without borrowing anything from the old one. Reinstall fresh copies of all your games through freeShop and that iso site. Restore those saves & extdata through Checkpoint once all games are reinstalled.

 

[Rdpruitt]

I have done h2testw on my new(64gb) card, and it is fine. it is my old sd card(32gb) that gives me a popup when I insert it into a computer, but lone wolf said that it should be fine.
and turd, would doing that 'check drive for file system errors' delete any data, or 'damage' it in an unwanted way?

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

sorry turd, you replied as I was typing to quantumcat
but yes, your list of probloms and facts are correct

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

Try building your setup from your new SD card without borrowing anything from the old one. Reinstall fresh copies of all your games through freeShop and that iso site. Restore those saves & extdata through Checkpoint once all games are reinstalled.

would this mean I need to get the luma, homebrew, fbi, and all that stuff from 3ds.guide?
and how can I check if my card is 'meta-stable with an improper allocation table'? can I check without formatting?

 

[TurdPooCharger]

I have done h2testw on my new(64gb) card, and it is fine. it is my old sd card(32gb) that gives me a popup when I insert it into a computer, but lone wolf said that it should be fine.
and turd, would doing that 'check drive for file system errors' delete any data, or 'damage' it in an unwanted way?

Most of the time, Windows does a good job fixing those check errors without reformatting. Most of the time.

From experience, I had a USB 1.0 64 MB flash drive long ago from my high school days that worked on computers but had that error check nag that kept popping up. One day, I got tired of it and allowed the checker to go through and accepted a reformat out of blind rage annoyance. I didn't know any better and lost some computer science homework, which was not fun scrambling in redoing those. Grr.

So while error checker works, you have to be cautionary in case it asks to reformat (reject that shiet if it asks to).

would this mean I need to get the luma, homebrew, fbi, and all that stuff from 3ds.guide?
and how can I check if my card is 'meta-stable with an improper allocation table'? can I check without formatting?

* Old card is already meta-stable as Windows keeps asking you to check for errors. Only way to correct this is by going through with the error checking. (Not advised at this moment due to possibility of losing your data).

Yes, build your 64 GB card setup from scratch using what 3ds.hack.guide tells you to do. Since your N2DSXL is already hacked, here's a somewhat shorthanded cheat guide in getting the new card up and running.

• https://gbatemp.net/threads/3ds-cfw-restoring-functionality-on-a-new-sd-card.507458/#post-8052010

Once you get that new card and bare bone setup working as intended, reinstall all your games. Remember, treat all the files from the old card as bad juju, so don't source your game CIA files from it.

The only files you do bring over are your backed up saves through Checkpoint. If you're lucky, all your saves and progress will have transferred over through this really convoluted method of migrating to your new card.

**
(really bad case scenario)

If for some reason your saves do not work when you tried copying them off your old card to the computer by SD card reader, you might have to try exporting the Checkpoint backed up save files using 3dshell and FTP (a form of wifi wireless data transfer).

 

[Rdpruitt]

I could use saves from JKSM right? instead of checkpoint?

and if I follow the shortcut guide you posted, will I still need the luma files/folder, homebrew files/folder, and other .3dsx stuff?

 

[TurdPooCharger]

I could use saves from JKSM right? instead of checkpoint?

JKSM is a valid save manager. It, however, has not kept up with the changing times due to the author of that app having to go away for a while, so some games may fail to get backed up with it. Checkpoint is considered current, go-to defacto save manager with user friendly GUI.

This may someday change in the future as JK (the author of JKSM) has decided to restart work on JKSM.

You can use both, but make sure to keep the saves made by each manager separate. I think the backed up saves are cross compatibility with one another when restoring, but you should not test that theory out.


and if I follow the shortcut guide you posted, will I still need the luma files/folder, homebrew files/folder, and other .3dsx stuff?

and if I follow the shortcut guide you posted, will I still need the luma files/folder, homebrew files/folder, and other .3dsx stuff?

That CFW starter kit.zip contains luma3DS [boot.firm], homebrew launcher's [boot.3dsx], boo9strap (folder + files), GodMode9 [.firm in luma/payloads], and an accompanying selection of several .3dsx apps, which includes Checkpoint v3.2.0 .

You'll need to dump the dspfirm.cdc using the provided DSP1 app and Rosalina Menu inject HBL into your selected system app (like Download Play, AR Games, etc).

* Edit (to add more) - When you get Homebrew Launcher and FBI working, the rest is up to you in finding and reinstalling all your games.

You might want to test some of your backed up saves to see if you can get them to restore on the new card as you build your new card's setup.

 

[Rdpruitt]

this is definatly looking promising. ill try it later today
and sorry I was stupid and didn't notice that the shortcut file was a .zip. stupid question

 

[Rdpruitt]

are all the files in the CFW starter kit.zip the newest updates? for example, is the luma in that .zip on v9.0?

 

[Rdpruitt]

uumm… I just noticed that(compared to the cfw starter pack) my old sd card does not have a boot9strap folder. is this bad? it doesn't have al9h things either

 

[Quantumcat]

uumm… I just noticed that(compared to the cfw starter pack) my old sd card does not have a boot9strap folder. is this bad? it doesn't have al9h things either

The boot9strap folder is only used for installing boot9strap, then you can delete it.

 

[TurdPooCharger]

are all the files in the CFW starter kit.zip the newest updates? for example, is the luma in that .zip on v9.0?

All the files in there are the newest stable releases at the time it was posted, but it's really the user's responsibility in updating their apps. That shorthanded guide was meant to quickly help troubleshoot users with messed up luma3ds CFW or SD card. It's not to be followed unless you've exhausted all other options in trying to get homebrew working again after you've hacked the 3DS/2DS using 3ds.hack.guide (which takes precedents over everything else). My raggity guide was more for my laziness in rewriting instructions. At some time later, I'll probably update that .zip and instructions, but they're still up to date.

 

[Rdpruitt]

ok thanks. im testing it now

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

right now i'm in section VII and there is no 'essential.exefs' in the /gm9/out/ folder

 

[TurdPooCharger]

ok thanks. im testing it now

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

right now i'm in section VII and there is no 'essential.exefs' in the /gm9/out/ folder

You at least have the <date>_<serialnumber>_sysnand_###.bin, right? That's the NAND image for restoring in case something happens. Keep that file safe somewhere (never delete it).

The 'essential.exefs' seems like a new thing from the guide. I crossed checked the hashes of the GM9 scripts in GodMode9 v1.6.3 versus the ones found in that zip, so nothing's changed files. I think the 3ds.hack.guide updated the instructions in anticipation of a new GodMode9 release.

In any case, continue on the tutorial.

 

[Rdpruitt]

Yes I have the serial number ones. But my old SD card does have the essential.exefs.

 

[TurdPooCharger]

Yes I have the serial number ones. But my old SD card does have the essential.exefs.

Okay, I did a little searching and found this. You have to get yours manually.

• Section VII - Backup Essential Files | No essential.exefs file in gm9/out folder

I looked at the Backup SysNAND.gm9 script.

# SysNAND backup GM9 script
# This will create a backup named [DATESTAMP]_[SERIAL]_sysnand_???.bin
# author: d0k3

set ERRORMSG   "SysNAND backup failed"
set SUCCESSMSG "SysNAND backup success"

ask "Create a SysNAND backup in $[GM9OUT]?"
findnot $[GM9OUT]/$[DATESTAMP]_$[SERIAL]_sysnand_???.bin OUTPATH
cp -h S:/nand_minsize.bin $[OUTPATH]
echo "Backup created successfully:\n$[OUTPATH]"

The first two lines are comments about what the script does and who the author is. The new two written lines are error messages. The rest are permission to copy your NAND image, finding a unused name for it, copying that file, and then announcement. That script does not extract essential.exefs for you as far as I can tell.

 

[Rdpruitt]

What should I do to copy over my saves from jksm? Should I copy the contents of the folder JKSV on the old SD card to the same folder on the new SD card?
And should I get the games from freeshop before I transfer the saves or after?