Hacking Removing B9S

[xelrix]

Prove it post a video of you doing exactly what i had just said to your 3ds.

If you really think it wont work then you will have no problem doing so

u wot m8???
GM9 doesnt magically know how to remove the b9s from your firm partition.
Restore nand means it flashes the chosen nand image into your 3ds nand.
If the image has hax, the resulting flashed nand will have hax.

Btw, the burden of proof is on who made the claim, which in this case, YOU.
Post a video of what YOU claim it to be or sit in a corner and educate yourself.

 

[Deleted member 381889]

u wot m8???
GM9 doesnt magically know how to remove the b9s from your firm partition.
Restore nand means it flashes the chosen nand image into your 3ds nand.
If the image has hax, the resulting flashed nand will have hax.

Btw, the burden of proof is on who made the claim, which in this case, YOU.
Post a video of what YOU claim it to be or sit in a corner and educate yourself.

^ So much this
Don't post about stuff you don't understand.

 

[Halomach]

Lmfao then gtfo

Bruh

 

[katsup]

I always remove hacks when selling consoles if only to avoid potential unwanted attention, it is not worth the extra money to sell it hacked. I do however try to keep the console on an official firmware that is hackable.

In the case of my 3DS, this is why I stayed with 9.2 menuhax. Even though I haven't turned on wifi in over a year, I know I will need to test online play before selling my 3DS when the time comes, assuming nothing new is discovered. The original OP may want to disclaimer that the console had the hacks removed and at the time of testing, online play worked.

 

[thisisallowed]

formating my 3ds will not solve this ? since I'm not banned (yet?) I don't want to sell it to a kid, saying that it's not banned and got it back 2 days later because nintendo flagged it.

No one here answers you, so a real answer: The simple way to do this is to download a legit nintendo firmware, rename it boot.firm, and put it on the SD card and the CTRNAND. You will still have B9S but no CFW so Nintendo can't detect it.

 

[NTE78]

If you have a pre-mod NAND backup, go into Decrypt9 or something, and restore it.
Edit: Nevermind, didn't see the first page.

 

[Deleted member 381889]

If you have a pre-mod NAND backup, go into Decrypt9 or something, and restore it.

At least read the OP first.

Sadly, I can't find my pre-hack nand backup.

 

[NTE78]

At least read the OP first.

ye

 

[xelrix]

No one here answers you, so a real answer: The simple way to do this is to download a legit nintendo firmware, rename it boot.firm, and put it on the SD card and the CTRNAND. You will still have B9S but no CFW so Nintendo can't detect it.

That's not how it works. You dont remove the official firmware when youre installing b9s. You cant just download a "legit nintendo firmware", rename it to something else and it magically works because the "legit firmware", as you coined it, is not just 1, convenient file where you can conveniently rename it to conveniently work it into a whole other convenient loader/hax/system than what it used to (a loading environment with no pesky middlemen like b9s or a9lh).

Though it would be a neat idea to have a custom "firmware" (a patch, essentially) that doesnt have any other features, just firm protection.
No chainloaders, no emunand loading, no signature patching, nothing.
Just native firm partition protection.

 

[DjoeN]

You have a previous backup from before B9S?
Restore to that (i bet it's a A9LH), and A9LH is easy to remove.

 

[GizmoTheGreen]

That's not how it works. You dont remove the official firmware when youre installing b9s. You cant just download a "legit nintendo firmware", rename it to something else and it magically works because the "legit firmware", as you coined it, is not just 1, convenient file where you can conveniently rename it to conveniently work it into a whole other convenient loader/hax/system than what it used to (a loading environment with no pesky middlemen like b9s or a9lh).

Though it would be a neat idea to have a custom "firmware" (a patch, essentially) that doesnt have any other features, just firm protection.
No chainloaders, no emunand loading, no signature patching, nothing.
Just native firm partition protection.

https://gbatemp.net/threads/release-kecleon-patch-for-luma3ds.455090/ ?

 

[Garou]

https://gbatemp.net/threads/release-kecleon-patch-for-luma3ds.455090/ ?

from page 1
no idea if it can be converted to firm as stated in here https://gbatemp.net/threads/release-kecleon-patch-for-luma3ds.455090/page-7#post-7325114

Kecleon doesn't work with B9S. It's an A9LH payload.

You cannot convert it either since CFWs do not work with the converter.

 

[GizmoTheGreen]

from page 1
no idea if it can be converted to firm as stated in here https://gbatemp.net/threads/release-kecleon-patch-for-luma3ds.455090/page-7#post-7325114

someone will need to build (not convert) a .firm version or apply the patches to newer luma3ds and build that... just a matter of time until someone does it I think.

 

[Bosshi]

someone will need to build (not convert) a .firm version or apply the patches to newer luma3ds and build that... just a matter of time until someone does it I think.

So there's currently no solution ? well I guess I'll just wait and hope I doesn't get strike down by nintendo

 

[Deleted-379826]

Well I know you can uninstall a9lh with safea9lhinstaller, is this really not a thing with B9S?

 

[marcoz9999]

it is alredy a way to unistall b9s ?

 

[CrispyYoshi]

So there's currently no solution ? well I guess I'll just wait and hope I doesn't get strike down by nintendo

it is alredy a way to unistall b9s ?

There is a solution. However, before you (and anyone else reading this) actually chooses to do this, please consider that:
- Nintendo likely already flagged your system for a ban, and you're best off getting a new system if you have already done unauthorized activity and shared it online somehow
- Hacked consoles sell significantly higher than unhacked consoles.

That said, here is one way you can uninstall b9s:
0) Make sure you have a functional NAND backup before you start, in case anything goes wrong.
1) Download the .firm for your matching firmware+model on 3ds.guide's hardmod page: https://3ds.guide/installing-boot9strap-(hardmod)
**If you download and flash the wrong one, you will hardbrick.
2) Rename the .firm to firm0.bin and copy it to your SD card
3) Boot up GodMode9 and copy/paste the firm0.bin from your SD to the SysNand Virtual (S:/ ) drive. Heed all of the warnings.
**The system will warn you several times and also tell you that your super small ~300kbish file is nowhere near the entire 4mb you're replacing. This is fine: Do it anyway (as long as you're 100% sure it's the right file)
4) Reboot and perform a system update to clean your firm1.

 

[Lacius]

There is a solution. However, before you (and anyone else reading this) actually chooses to do this, please consider that:
- Nintendo likely already flagged your system for a ban, and you're best off getting a new system if you have already done unauthorized activity and shared it online somehow
- Hacked consoles sell significantly higher than unhacked consoles.

• If your 3DS has already been flagged to be banned during the next banwave, removing B9S will do nothing to protect you. If you do get banned, you will have no way to unban yourself because you removed B9S.
• It appears that Nintendo is banning people due to the detection of illegitimate titles, not because they're detecting B9S or Luma3DS. So, removing B9S is pointless.

That said, here is one way you can uninstall b9s:
0) Make sure you have a functional NAND backup before you start, in case anything goes wrong.
1) Download the .firm for your matching region on 3ds.guide's hardmod page: https://3ds.guide/installing-boot9strap-(hardmod)
**If you download and flash the wrong one, you will hardbrick.
2) Rename the .firm to firm0.bin and copy it to your SD card
3) Boot up GodMode9 and copy/paste the firm0.bin from your SD to the SysNand Virtual (S:/ ) drive. Heed all of the warnings.
**The system will warn you several times and also tell you that your super small ~300kbish file is nowhere near the entire 4mb you're replacing. This is fine: Do it anyway (as long as you're 100% sure it's the right file)
4) Reboot and perform a system update to clean your firm1.

If someone tries to remove B9S on a console that, for example, was unbanned in part by generating a new SecureInfo_A, removing B9S will result in a brick. The original SecureInfo_A needs to be restored first.

 

[PrincessLillie]

I also want to unmod my old3DS running A9LH (NOT B9S) so I can sell it. However, I already did a System Transfer, so it's on stock and the top screen doesn't work. I also don't have the NAND backup anymore. Ideas?

 

[CrispyYoshi]

I also want to unmod my old3DS running A9LH (NOT B9S) so I can sell it. However, I already did a System Transfer, so it's on stock and the top screen doesn't work. I also don't have the NAND backup anymore. Ideas?

System transfer doesn't remove A9LH, and you can back up your NAND and uninstall A9LH easily despite a non-functional top screen.

Hourglass9, though outdated, has very few menu options and someone could probably help you navigate to dump your NAND, and uninstalling A9LH is as simple as running SafeA9LHInstaller as a payload, then pressing Start and inputting the button combo to uninstall A9LH.

Someone on A9LH/willing to read the source code will have to help you with that, though, because I've already forgotten what the Hourglass9 menu+SafeA9LHInstaller button combo looks like to give you precise details.