Hacking Problem when restored luma3ds backup

[TurdPooCharger]

.
.
But I have to ask @TurdPooCharger at this point to confirm or negate this.

Here now. I had to be away due to family laundry machine breaking down.You held the fort. Rest easy.

Yes, I agree with @KleinesSinchen's assessment. This seems to be a scenario of corrupted database files.

All there is in my luma folder is config.bin and there is nothing in data management. It does say Booted from SD via B9S as the bottom when i hold select.

@Skittle, read these examples to see if your issue is this one. I might not be available to post here depending how my washing machine repair goes.

• N2DS SD card data management corruption?
• ALL INSTALLED APPS GONE AFTER DELETING SSB
• SD card rendered obsolete after 3DS format.

 

[Skittle]

Here now. I had to be away due to family laundry machine breaking down.You held the fort. Rest easy.

Yes, I agree with @KleinesSinchen's assessment. This seems to be a scenario of corrupted database files.



@Skittle, read these examples to see if your issue is this one. I might not be available to post here depending how my washing machine repair goes.

• N2DS SD card data management corruption?
• ALL INSTALLED APPS GONE AFTER DELETING SSB
• SD card rendered obsolete after 3DS format.

Sorry for the late reply i didn't have time to try this until now and now that i have im kinda confused on step 7. what do i do after i go to godmode9?

 

[TurdPooCharger]

Sorry for the late reply i didn't have time to try this until now and now that i have im kinda confused on step 7. what do i do after i go to godmode9?

Sorry bud. Late reply. Just finished fixing the family's laundry machine (yay!) but got some last minute thanksgiving house cleanup (boo!).

If you're referring to this post,

7. Go to GodMode9. Use the CTRTransfer (Type D9) - Fix movable.sed KeyY.

• Ensure the NAND movable.sed KeyY matches encryption with the <ID0> subfolder.

The purpose of step 7 is to check and (re)match the encryption matches between the 3DS firmware and Nintendo 3DS folder in the event the user changed this by doing a Format System Memory or SysNAND Restore.

***

You will need to,

• press (HOME) button → Scripts... → CTRTransfer (Type D9)

, when launching the gm9 script.

Make sure you're using the version 1.4 of this script. The file should be located at:

• sdmc:/gm9/scripts/CTRTransfer (Type D9).gm9

8. For signs of damaged database where only GodMode9 can see them in Search for titles, use the CTRTransfer (Type D9) - Rebuild 3DS Database.

• Use the Option (A) Quick if you have lots of games and your SD card checked out fine in step 4.
  
• Use the Option (B) Full if your SD card failed hardware testing in step 4. This will test for data corruption for titles that fail to get dumped back into CIAs.

That script has other menu options.

- Read the descriptions and instructions in the upper screen.
- I recommend you go with Rebuild 3DS Database → Option (B) Full as this will find any data corruption for any titles that can't be dumped into CIAs.
- There's a special trick to (1b) Backup CIAs & Saves in order to get this run and to prevent carelessness.
- Once the 3DS turns off, FBI reinstall all the dumped CIAs, and go back to the GodMode9 to do (2b) Restore Saves.​

9. For missing tickets, use faketik.

• System Settings → Data Management → Nintendo 3DS → Software

10. Backup all 3DS games saves + extdata using Checkpoint or JKSM.
11. Mass unwrap HOME Menu icons using Cthulhu.​

These should be self explanatory.

12. Certain games like Super Smash Bros 3DS and Animal Crossing: New Leaf require special attention as they have something called Secure Value.

To reset (all at once) the anti-cheat save protection, delete this specific NAND file.

• [1:] SYSNAND CTRNAND/data/<ID0>/sysdata/00010011/00000000
• Be careful. Don't delete the wrong 00000000 file.

If you use the version 1.4 of CTRTransfer (Type D9), you can skip step 12. The script automatically takes care of deleting this file back in (2b) Restore Saves.

 

[Skittle]

Sorry bud. Late reply. Just finished fixing the family's laundry machine (yay!) but got some last minute thanksgiving house cleanup (boo!).

If you're referring to this post,



The purpose of step 7 is to check and (re)match the encryption matches between the 3DS firmware and Nintendo 3DS folder in the event the user changed this by doing a Format System Memory or SysNAND Restore.

***

You will need to,

• press (HOME) button → Scripts... → CTRTransfer (Type D9)

, when launching the gm9 script.

Make sure you're using the version 1.4 of this script. The file should be located at:

• sdmc:/gm9/scripts/CTRTransfer (Type D9).gm9

That script has other menu options.

- Read the descriptions and instructions in the upper screen.
- I recommend you go with Rebuild 3DS Database → Option (B) Full as this will find any data corruption for any titles that can't be dumped into CIAs.
- There's a special trick to (1b) Backup CIAs & Saves in order to get this run and to prevent carelessness.
- Once the 3DS turns off, FBI reinstall all the dumped CIAs, and go back to the GodMode9 to do (2b) Restore Saves.​

These should be self explanatory.



If you use the version 1.4 of CTRTransfer (Type D9), you can skip step 12. The script automatically takes care of deleting this file back in (2b) Restore Saves.

It says i need to update gm9 to 1.9.0. How do i do that?

 

[TurdPooCharger]

It says i need to update gm9 to 1.9.0. How do i do that?

[d0k3, GitHub] GodMode9

• smdc:/luma/payloads/GodMode9.firm

You might want to back go back and do steps 1-4 if you skipped those. Rebuilding or relisting the 3DS databse will fail if your SD card is fake or bad.

Step 5 has a download link to a CFW starter kit. It includes all the necessary homebrew apps and acts as a reference to what an SD card setup should be.

 

[Skittle]

yes i have done all the previous steps and updated gm9. when i boot up the new version it says not running from a boot9strap compatible entrypoint and when i try to fix movable.sed KeyY it says 1:/private/movable.sed file is missing. I don't know if this matters but all there is in my sd card is the Nintendo 3DS folder, the gm9 folder, and the luma folder which i had to make. Also it boots up to gm9 even if i just press the power button without doing anyhting else

 

[TurdPooCharger]

yes i have done all the previous steps and updated gm9. when i boot up the new version it says not running from a boot9strap compatible entrypoint and when i try to fix movable.sed KeyY it says 1:/private/movable.sed file is missing. I don't know if this matters but all there is in my sd card is the Nintendo 3DS folder, the gm9 folder, and the luma folder which i had to make. Also it boots up to gm9 even if i just press the power button without doing anyhting else

What I meant about updating GodMode9 was replacing the FIRM file found on the SD card at that directory.

• sdmc:/ refers to the root of the sd memory card.

***

You mistakenly replaced boot9strap with GodMode9 on the 3DS system's internal nand stoarge. To fix this, reinstall boot9strap with one of these methods.

• [3ds.hacks.guide] Updating B9S
• GodMode9 → press (A) on SafeB9SInstaller.firm → FIRM image options... → Boot FIRM

-or-

• GodMode9 → press (A) on boot9strap.firm → FIRM image options... → Install FIRM → Install to both
  • You may want to first verify that the FIRM is correct using the Calculate SHA-256.
    
  • [version 1.3 | SHA-256: 79C68585B4BA1D7C4A91B858861553E768C6576B92E303810B33219736B3598B | size: 30 KB]

 

[Skittle]

What I meant about updating GodMode9 was replacing the FIRM file found on the SD card at that directory.

• sdmc:/ refers to the root of the sd memory card.

***

You mistakenly replaced boot9strap with GodMode9 on the 3DS system's internal nand stoarge. To fix this, reinstall boot9strap with one of these methods.

• [3ds.hacks.guide] Updating B9S
• GodMode9 → press (A) on SafeB9SInstaller.firm → FIRM image options... → Boot FIRM

-or-

• GodMode9 → press (A) on boot9strap.firm → FIRM image options... → Install FIRM → Install to both
  • You may want to first verify that the FIRM is correct using the Calculate SHA-256.
    
  • [version 1.3 | SHA-256: 79C68585B4BA1D7C4A91B858861553E768C6576B92E303810B33219736B3598B | size: 30 KB]

View attachment 188151​

Do i need to follow all of the steps or just download safeb9sinstaller and boot9strap?​

 

[TurdPooCharger]

Do i need to follow all of the steps or just download safeb9sinstaller and boot9strap?

Are you having trouble reinstalling boot9strap v1.3 to the FIRM0 and FIRM1 partitions? If you look in the CFW starter kit at step 5, it includes those already.

 

[Skittle]

Are you having trouble reinstalling boot9strap v1.3 to the FIRM0 and FIRM1 partitions? If you look in the CFW starter kit at step 5, it includes those already.

so i need to copy everything from the cfw starter kit to my sd card?

 

[TurdPooCharger]

so i need to copy everything from the cfw starter kit to mt sd card?

From my previous 1-on-1 debugging sessions with others who were newcomers or inexperienced with 3DS custom firmware, I recommend copying and pasting all the contents within the CFW starter kit to their SD cards.

Other than saving us time and headache from tracking down all the individual app repos, downloading their latest versions, and extracting those files on the SD card to the correct locations, another big reason this kit was created was to minimum the incidents of onlookers wanting to haze noobs for failing to follow seemingly simple instructions. Back then, these encounters usually ended up with name calling and questioning one's intelligence. I would like to avoid this scenario/distraction and not have the person who need help feel like shit or unwelcomed from the community.

If the kit seems excessive or contains apps that aren't relevant to your interests, you should keep a copy of your current main setup on computer, temporarily use the reference setup to rebuild the 3DS database, copy the fixed Nintendo 3DS folder and the saves backed up from Checkpoint/JKSM to the main setup, delete the reference setup, copy the main setup back on the SD card, and then update the main setup to be more in line to what's specified in [3ds.hacks.guide] Finalizing Setup.

***

Explanation
The reason why SafeB9SInstaller failed to install sighax is because the boot9strap *.firm and *.sha files at the sdmc:/boot9strap folder are missing.

Once B9S is reinstalled after this long winded detour... revisit and continue at step 7.

 

[Skittle]

From my previous 1-on-1 debugging sessions with others who were newcomers or inexperienced with 3DS custom firmware, I recommend copying and pasting all the contents within the CFW starter kit to their SD cards.

Other than saving us time and headache from tracking down all the individual app repos, downloading their latest versions, and extracting those files on the SD card to the correct locations, another big reason this kit was created was to minimum the incidents of onlookers wanting to haze noobs for failing to follow seemingly simple instructions. Back then, these encounters usually ended up with name calling and questioning one's intelligence. I would like to avoid this scenario/distraction and not have the person who need help feel like shit or unwelcomed from the community.

If the kit seems excessive or contains apps that aren't relevant to your interests, you should keep a copy of your current main setup on computer, temporarily use the reference setup to rebuild the 3DS database, copy the fixed Nintendo 3DS folder and the saves backed up from Checkpoint/JKSM to the main setup, delete the reference setup, copy the main setup back on the SD card, and then update the main setup to be more in line to what's specified in [3ds.hacks.guide] Finalizing Setup.

***

Explanation
The reason why SafeB9SInstaller failed to install sighax is because the boot9strap *.firm and *.sha files at the sdmc:/boot9strap folder are missing.

Once B9S is reinstalled after this long winded detour... revisit and continue at step 7.

I am incredibly sorry for wasting so much of your time on this issue. Is there a way we can talk in pm? I can't do much right now because its a little too late and i will continue in the morning.

 

[TurdPooCharger]

I am incredibly sorry for wasting so much of your time on this issue. Is there a way we can talk in pm? I can't do much right now because its a little too late and i will continue in the morning.

There is nothing to apologies for as you haven't done anything that warrants blame. These kinds of setbacks and stumbling blocks are sort of expected when it comes to data recovery. Most of us folks here these days in the 3DS side of GBAtemp forum are super chill. I just wanted to provide a little backstory why that CFW starter kit came to be during the tailend height of the 3DS homebrew scene when there were some among us who weren't very cash and not so chill.

We can continue our discussion in private message if you feel more comfortable freely asking questions that way. I might reply back to you at really weird hours and long stretches though (got some catching up to do with family visits for Thanksgiving holiday).

 

[Skittle]

There is nothing to apologies for as you haven't done anything that warrants blame. These kinds of setbacks and stumbling blocks are sort of expected when it comes to data recovery. Most of us folks here these days in the 3DS side of GBAtemp forum are super chill. I just wanted to provide a little backstory why that CFW starter kit came to be during the tailend height of the 3DS homebrew scene when there were some among us who weren't very cash and not so chill.

We can continue our discussion in private message if you feel more comfortable freely asking questions that way. I might reply back to you at really weird hours and long stretches though (got some catching up to do with family visits for Thanksgiving holiday).

Thank you. I would very much feel more comfortable talking in pm. I'll get around to you tomorrow when i get the chance