Homebrew Boot9Strap is Corrupted

[AJBauer]

I made a post earlier about how FBI, Homebrew Launcher, Luma, and all of my software (Including games) had disappeared from the home menu of my N3DSXL after I tried to update SSB.
I made a back up of my MicroSD, reformatted it with guiformat (FAT32), put the data back. Nothing. I can boot Godmode9 and Luma from the Luma chainloader but Boot9strap just gave me a black screen.
I asked around and was told to update BS9 with this guide. I followed the guide to the letter and I got this error every time I tried to boot B9S:

 

[Joom]

How are you transferring the files to the SD, and have you checked the card itself for corruption?

 

[AJBauer]

How are you transferring the files to the SD, and have you checked the card itself for corruption?

Yes, I checked for corruption. I move the files back and forth between the 3DS and the PC via a USB MicroSD reader.

 

[Joom]

Try transferring the files over FTP and see if that makes a difference.

 

[gamesquest1]

double check your SD card is genuine using this tool
http://www.rmprepusb.com/tutorials/...s/FAKEFLASHTEST_v1.1.1.zip?attredirects=0&d=1

if you are just copying all the files you backed up from the SD card before reformatting the boot.bin file may have been corrupted copying a fresh one should fix the issue.....but if its a fake SD card you will just keep running into issues every time you fill it up past a certain point

just in an effort to educate people how these fake SD card work here is a video summing up how and why fake cards "work" for a while

 

[RHOPKINS13]

This is fixable! This screen is normal to get if you were running an older version of B9S with an old version of Luma, updated your version of B9S, and haven't updated your version of Luma yet. Download the latest version of Luma3DS (https://github.com/AuroraWright/Luma3DS/releases) and place boot.firm on the root of your SD card, overwriting the one that is there. Good luck and hope this helps!

 

[comput3rus3r]

pretty sure he's messing up the steps. go back and double check your steps.
People love to blame sd card corruption when that's maybe a 10 percent chance of it being the problem vs 90 percent of the time is just user error.

 

[AJBauer]

pretty sure he's messing up the steps. go back and double check your steps.
People love to blame sd card corruption when that's maybe a 10 percent chance of it being the problem vs 90 percent of the time is just user error.

What? Okay, first off I did the steps twice just to make sure I didn't miss anything. Secondly, I wasn't blaming the card and saying it was corrupted. I literally said the exact opposite, that the card isn't corrupted.

This is fixable! This screen is normal to get if you were running an older version of B9S with an old version of Luma, updated your version of B9S, and haven't updated your version of Luma yet. Download the latest version of Luma3DS (https://github.com/AuroraWright/Luma3DS/releases) and place boot.firm on the root of your SD card, overwriting the one that is there. Good luck and hope this helps!

I already updated Luma like the guide told me to and it didn't help.

double check your SD card is genuine using this tool
http://www.rmprepusb.com/tutorials/...s/FAKEFLASHTEST_v1.1.1.zip?attredirects=0&d=1

if you are just copying all the files you backed up from the SD card before reformatting the boot.bin file may have been corrupted copying a fresh one should fix the issue.....but if its a fake SD card you will just keep running into issues every time you fill it up past a certain point

just in an effort to educate people how these fake SD card work here is a video summing up how and why fake cards "work" for a while

The first program found no issues. The "deeper" scan gives this error every time:

Error reading file 'D:\15.h2w', offset 0x700000.
(The system cannot find the file specified. Code 2)
Reading speed: 19.4 MByte/s
H2testw v1.4

 

[comput3rus3r]

I wasn't saying you said the sd card is corrupted. I'm saying when somebody has a problem people always tell them their sd card is corrupted. which is rarely the case.

 

[Joom]

I wasn't saying you said the sd card is corrupted. I'm saying when somebody has a problem people always tell them their sd card is corrupted. which is rarely the case.

There's a reason for this. Data doesn't just corrupt itself. Failed transfers and faulty hardware, however, do.

 

[AJBauer]

I wasn't saying you said the sd card is corrupted. I'm saying when somebody has a problem people always tell them their sd card is corrupted. which is rarely the case.

Ah. Sorry, I misunderstood your intentions, then.

 

[AJBauer]

I'm starting to question if this is fixable at all.
I can't find anyone else that has had this problem.
All I want to do is reinstall FBI but I need Homebrew Launcher for that.
But I can't figure out how to reinstall Homebrew Launcher.

 

[comput3rus3r]

are you following the guide? at what step are you?

 

[RHOPKINS13]

I already updated Luma like the guide told me to and it didn't help.

At this point, assuming you updated Luma correctly, it sounds more like either the SD card is faulty and the 3DS system is having problems reading it, or maybe it's a problem with the sd card reader in the system. Since you have a backup of your microSD, I would try wiping it and just throwing Luma's boot.firm on it.

I would recommend using guiformat like the 3DS guide says on the homepage, with an allocation unit size of 32K.

Your 3DS should boot, after going through the Luma config screen, although you won't have any of your games or saves (yet). After that you can try copying over your Nintendo 3DS folder, and any other stuff you wanted off of your microSD backup.

But at this point I would seriously consider getting a new card.

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

I'm starting to question if this is fixable at all.
I can't find anyone else that has had this problem.
All I want to do is reinstall FBI but I need Homebrew Launcher for that.
But I can't figure out how to reinstall Homebrew Launcher.

If you're on the latest version of Luma, you don't need to "install" the Homebrew Launcher. You use Rosalina for that. Download the new-hbmenu release from here:
https://github.com/fincs/new-hbmenu/releases

Put boot.3dsx on the root of your microSD card.

Then, you have to assign an installed title to launch the file. The guide uses Download Play, some people use the Health & Safety app, some people use AR Games... etc. Open whatever app you want to use to launch the homebrew menu. Then, by default, the key combination to open the Rosalina menu is L+Down+Select.

Go to Miscellaneous Options, Switch the hb. title to the current app. Then make sure to go back and choose Save settings. Now back out of the Rosalina menu, go back to the home menu, and try launching your app again. You should get the homebrew menu instead.

Hope this helps.

 

[AJBauer]

At this point, assuming you updated Luma correctly, it sounds more like either the SD card is faulty and the 3DS system is having problems reading it, or maybe it's a problem with the sd card reader in the system. Since you have a backup of your microSD, I would try wiping it and just throwing Luma's boot.firm on it.

I would recommend using guiformat like the 3DS guide says on the homepage, with an allocation unit size of 32K.

Your 3DS should boot, after going through the Luma config screen, although you won't have any of your games or saves (yet). After that you can try copying over your Nintendo 3DS folder, and any other stuff you wanted off of your microSD backup.

But at this point I would seriously consider getting a new card.

I've already formatted the card. Just to be sure I tried a second card that was intended for my Switch and it wouldn't read that either. I have tried wiping the card several times.
If I can somehow reinstall Homebrew Launcher and FBI that'd be enough. I can always get the stuff I lost via CIAs if FBI is installed.

are you following the guide? at what step are you?

Well it seems that you're not supposed to even open boot9strap via the chainloader, it only exists to install Luma (Which I actually have, already).
I'm going through finalizing steps in the hopes that'll help but when I use Rosalina, select “Switch the hb. title to the current app.”, close Rosalina, then reopen Download Play, this happens:

I have no idea how to open crash dumps.

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

 

[The Real Jdbye]

I've already formatted the card. Just to be sure I tried a second card that was intended for my Switch and it wouldn't read that either. I have tried wiping the card several times.
If I can somehow reinstall Homebrew Launcher and FBI that'd be enough. I can always get the stuff I lost via CIAs if FBI is installed.



Well it seems that you're not supposed to even open boot9strap via the chainloader, it only exists to install Luma (Which I actually have, already).
I'm going through finalizing steps in the hopes that'll help but when I use Rosalina, select “Switch the hb. title to the current app.”, close Rosalina, then reopen Download Play, this happens:

I have no idea how to open crash dumps.

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

Did you put the boot.3dsx from new-hbmenu on the root of the SD card like you were told to?

 

[RHOPKINS13]

I'm going through finalizing steps in the hopes that'll help but when I use Rosalina, select “Switch the hb. title to the current app.”, close Rosalina, then reopen Download Play, this happens:

I have no idea how to open crash dumps.

Download the latest version of hbmenu from the link I gave you before:
https://github.com/fincs/new-hbmenu/releases

Throw that boot.3dsx file on the root of your SD card, overwriting any that is already there. You have to use this version, as it has Rosalina support. Older versions of the homebrew launcher don't have Rosalina support, and they crash like this instead. Then you should be able to load Download Play and the homebrew launcher should come up. You're almost there!

Well it seems that you're not supposed to even open boot9strap via the chainloader, it only exists to install Luma (Which I actually have, already).

Boot9Strap is the exploit used to load Luma, not the other way around. Once Boot9Strap is installed, it runs every time you power on your 3DS, and launches boot.firm, which is hopefully the latest version of Luma in your case. And then you can use Luma's chainloader to load other .firm payloads, like GodMode9.

 

[AJBauer]

Did you put the boot.3dsx from new-hbmenu on the root of the SD card like you were told to?

Didn't see that on the guide but it worked!

But now all the CIAs are failing to install in FBI... (Result code: 0xC8804478, if that helps.)

 

[RHOPKINS13]

Didn't see that on the guide but it worked!

But now all the CIAs are failing to install in FBI... (Result code: 0xC8804478, if that helps.)

Download the latest 3DSX version of FBI from here:
https://github.com/Steveice10/FBI/releases
And throw it in your /3ds/ folder.

In case you're wondering why so much has changed, our best guess as to how Nintendo has been banning 3DS units from online play has been that Nintendo can see which titles you have been playing. Any Homebrew CIA would use a title ID that doesn't match one of Nintendo's titles, so Nintendo can tell if you're running homebrew, and ban you for it.

By using Rosalina, it makes it look like you're on the Health & Safety App / Download Play / AR Games / whatever app you chose. If you care about online play, it's safest to uninstall all of your homebrew CIAs, and just use .3dsx versions from now on. You can use a homebrew app called Cthulu to wipe your activity log if you wish.

 

[AJBauer]

Download the latest 3DSX version of FBI from here:
https://github.com/Steveice10/FBI/releases
And throw it in your /3ds/ folder.

In case you're wondering why so much has changed, our best guess as to how Nintendo has been banning 3DS units from online play has been that Nintendo can see which titles you have been playing. Any Homebrew CIA would use a title ID that doesn't match one of Nintendo's titles, so Nintendo can tell if you're running homebrew, and ban you for it.

By using Rosalina, it makes it look like you're on the Health & Safety App / Download Play / AR Games / whatever app you chose. If you care about online play, it's safest to uninstall all of your homebrew CIAs, and just use .3dsx versions from now on. You can use a homebrew app called Cthulu to wipe your activity log if you wish.

It still isn't working.