Hacking 3DS NOOB PARADISE - Ask questions here

[djender]

Hey guys, I've been away from the scene for quite some time now. My son has an old 3ds on 11.8.0 with bootstrap9 + luma. How can I upgrade to the latest firmware without losing hack?

 

[Lacius]

Hey guys, I've been away from the scene for quite some time now. My son has an old 3ds on 11.8.0 with bootstrap9 + luma. How can I upgrade to the latest firmware without losing hack?

If you are already on 11.8, then it is safe to update to 11.10 through the system settings, and you will not lose your hacks.

11.10 requires that you have at least Luma3DS v9.1 installed, but 11.8 also requires v9.1 or higher, so that means you already have it. If you haven't already done so, it is recommended that you update Luma3DS to v10.0.1. You can check your Luma3DS version by holding Select when you power on the 3DS.

 

[Dava]

Hi guys i have a big Problem. I have a hacked 2ds and i forgot wich Hack i used b9s or the old one armloaderhaxx. How I can find out that? Because luma don’t let me update the cfw

 

[TurdPooCharger]

Hi guys i have a big Problem. I have a hacked 2ds and i forgot wich Hack i used b9s or the old one armloaderhaxx. How I can find out that? Because luma don’t let me update the cfw

• CFW: I formatted my 2ds's sd card and now it wont turn on [post #17]

or hold (SELECT) when you turn on the 2DS.

 

[nqs]

hey uh, i bought a modded new 3ds xl on ebay. it has luma3ds, homebrew (soundhax ver, i think? that's what it says on the sd card anyway), nts cfw, luma updater, boot9strap and fbi. it was modded in 2017 so i was trying to update everything but i dont know how to install luma updater, plus luma3ds just crashes when i try to open the app. i don't know how to update fbi (i've tried but it stays at 2.4.8) and it gives me error 0xd8a0a03c every time i try to use the update it has. i dont really know where to start except for the 3ds.hacks.guide and finalizing the homebrew soundhax setup :/ can someone help and tell me where i can start/how to fix luma3ds + fbi?

 

[shideravan]

I came back to 3DS afterva year occupied with other things and now I'm trying to transfer my saves from gateway to another 3ds with luma, but the gateway site is off and I need another way to access the emunand. What are my options? (firm 9.2.0-20U)

also, I have Cubic Ninja cartridge, it can helps to launch Gateway exploit anyway?

 

[Dava]

• CFW: I formatted my 2ds's sd card and now it wont turn on [post #17]

or hold (SELECT) when you turn on the 2DS.

Do i Need to install it again ? I‘m a little bit confused. It shows me only that on the picture. And when I try to update luma it shows this (the another picture)
What is the best way to show me my hack

 

[TurdPooCharger]

Do i Need to install it again ? I‘m a little bit confused. It shows me only that on the picture. And when I try to update luma it shows this (the another picture)
What is the best way to show me my hack

Update to boot9strap v1.3, Luma3DS v10.0.1, and GodMode9 v1.8.0 on both SD card and CTRNAND.

• Updating B9S
• CTRNAND Luma3DS

 

[Atomic-Red-Star]

I promised I tried to find an answer...

But I couldn't find any threads for this specific use case (I'm sure it's buried somewhere).

I have one CFW 2DS XL and one stock (brand new). Made a LOT of digital purchases on my original 2DS before modifying it. I wanted to transfer my legitimately purchased games to the new 2DS (along with my NNID) and keep my CFW 2DS modified for my injected VC games and emulators. I would like to keep the new one "pure" in stock form. Should I:

- Uninstall the CFW and return the original 2DS to stock and then perform a transfer
- Perform a transfer from CFW 2DS to new non-CFW 2DS (I realize I can then delete non-stock games and folders)

Will the CFW 2DS still work once the NNID is transferred to the new stock 2DS? Can I just create a new NNID on the CFW 2DS after I transfer everything? Any risk in transferring from CFW to non-CFW? I would prefer to avoid returning the original one to stock just to transfer the purchased games and NNID over. I want the end result to be:

- Awesomely modified 2DS XL with CFW and all my injected VC ROM back-up games (with new NNID?)
- Vanilla Stock 2DS XL with my original NNID and all of its associated digital purchases

Has anyone gone through a similar use case? All the posts I read involved CFW to CFW transfers.

Thank you in advance!

 

[Quantumcat]

I promised I tried to find an answer...

But I couldn't find any threads for this specific use case (I'm sure it's buried somewhere).

I have one CFW 2DS XL and one stock (brand new). Made a LOT of digital purchases on my original 2DS before modifying it. I wanted to transfer my legitimately purchased games to the new 2DS (along with my NNID) and keep my CFW 2DS modified for my injected VC games and emulators. I would like to keep the new one "pure" in stock form. Should I:

- Uninstall the CFW and return the original 2DS to stock and then perform a transfer
- Perform a transfer from CFW 2DS to new non-CFW 2DS (I realize I can then delete non-stock games and folders)

Will the CFW 2DS still work once the NNID is transferred to the new stock 2DS? Can I just create a new NNID on the CFW 2DS after I transfer everything? Any risk in transferring from CFW to non-CFW? I would prefer to avoid returning the original one to stock just to transfer the purchased games and NNID over. I want the end result to be:

- Awesomely modified 2DS XL with CFW and all my injected VC ROM back-up games (with new NNID?)
- Vanilla Stock 2DS XL with my original NNID and all of its associated digital purchases

Has anyone gone through a similar use case? All the posts I read involved CFW to CFW transfers.

Thank you in advance!

You can do a normal system transfer from the CFW console to the stock one. The result:

• The stock console will have the NNID and bought games
• The stock console will have the files from the non-bought games but they won't do anything
  
• The CFW console will be formatted and you'll have to do the finalising setup page again, and install everything again.

To avoid these annoyances do the following:

• Make a NAND backup and SD card backup of the source console before the transfer
• Uninstall all non-bought games from the source console
• Do the transfer
• Restore the NAND backup and SD card backup to the source console
• Look at https://3ds.hacks.guide/godmode9-usage and follow 'Remove NNID without formatting your device' on the source console
• Make a new NNID on the source console

Then you should have everything you're after

 

[Atomic-Red-Star]

You can do a normal system transfer from the CFW console to the stock one. The result:

• The stock console will have the NNID and bought games
• The stock console will have the files from the non-bought games but they won't do anything
  
• The CFW console will be formatted and you'll have to do the finalising setup page again, and install everything again.

To avoid these annoyances do the following:

• Make a NAND backup and SD card backup of the source console before the transfer
• Uninstall all non-bought games from the source console
• Do the transfer
• Restore the NAND backup and SD card backup to the source console
• Follow 'Remove NNID without formatting your device' on the source console
• Make a new NNID on the source console

Then you should have everything you're after

You are truly a Quantum Cat. Thank you for the speedy response. Exactly what I needed! Thanks again!

 

[Atomic-Red-Star]

You can do a normal system transfer from the CFW console to the stock one. The result:

• To avoid these annoyances do the following:

• Make a NAND backup and SD card backup of the source console before the transfer
• Uninstall all non-bought games from the source console
• Do the transfer
• Restore the NAND backup and SD card backup to the source console
• Follow 'Remove NNID without formatting your device' on the source console
• Make a new NNID on the source console

Then you should have everything you're after

Once I restore the NAND backup and SD card backup to the source console, and remove my original NNID, I assume I'll lose access to the purchased software originally on my SD card, right? @Quantumcat

 

[Quantumcat]

Once I restore the NAND backup and SD card backup to the source console, and remove my original NNID, I assume I'll lose access to the purchased software originally on my SD card, right? @Quantumcat

That's right. But you can still get them back the non-buying way.

Probably a good idea to back up all your save files with JKSM or Checkpoint and copy to a pc before you start as well.

 

[PoiRan]

Total noob here, never even held a 3ds before, got a 3ds xl yesterday, had 4.5E installed so followed hacks guide, latest versions of all tools, used soundhax, installed boot9strap, booted into Luma 10.0.1 settings. Pressed start to save settings.

After that, reboot to black screen. Used Luma 9 boot.firm, and console boots fine. Godmode also loads.

But not Luma 10. If I delete luma config, Luma 10 again boots to settings, after saving settings, reboots to black screen. Select, or Start, doesn't work on this black screen.

So...Maybe I should leave it as it is, bit I'm thinking of system update and then trying Luma 10 again, maybe my system, 4,5, is just too old?

(written from phone, pardon for autocontects)

 

[Quantumcat]

Total noob here, never even held a 3ds before, got a 3ds xl yesterday, had 4.5E installed so followed hacks guide, latest versions of all tools, used soundhax, installed boot9strap, booted into Luma 10.0.1 settings. Pressed start to save settings.

After that, reboot to black screen. Used Luma 9 boot.firm, and console boots fine. Godmode also loads.

But not Luma 10. If I delete luma config, Luma 10 again boots to settings, after saving settings, reboots to black screen. Select, or Start, doesn't work on this black screen.

So...Maybe I should leave it as it is, bit I'm thinking of system update and then trying Luma 10 again, maybe my system, 4,5, is just too old?

(written from phone, pardon for autocontects)

Yes you should update - there's no advantage to being on a lower firmware. That's why the guide tells you to update. If you want to preserve the ability to go back easily, make a NAND backup first. That being said I have never heard someone not being able to boot Luma 10 because they were on a lower firmware though. So it is possible the firmware isn't the issue

 

[PoiRan]

Yes you should update - there's no advantage to being on a lower firmware. That's why the guide tells you to update. If you want to preserve the ability to go back easily, make a NAND backup first. That being said I have never heard someone not being able to boot Luma 10 because they were on a lower firmware though. So it is possible the firmware isn't the issue

Thanks, that's what I thought. I just figured that if for, whatever reason, Luma 10 won't run even after updating system it might be safer to never update att all. I'll try another SD card, not that I think there's anything wrong with this, but I'll copy the files fresh, maybe I made a mistake somewhere. I'll make a NAND backup first though.

 

[KleinesSinchen]

Thanks, that's what I thought. I just figured that if for, whatever reason, Luma 10 won't run even after updating system it might be safer to never update att all. I'll try another SD card, not that I think there's anything wrong with this, but I'll copy the files fresh, maybe I made a mistake somewhere. I'll make a NAND backup first though.

Just tested it and can confirm: current Luma v10.0.1 with official firmware on 4.5.0-10 also results in double black screen for me* and the O3DSXL can only be turned off by holding power for some seconds. Loads normally with Luma v9.1

Some more tests should be done, but it seems newest Luma broke compatibility with very old firmware. That's bad because if somebody – like you – follows the guide normally, they end up with latest Luma and never even come to this point:
https://3ds.hacks.guide/finalizing-setup#section-ii---updating-the-system
without downgrading Luma first.

Create a backup first – always a good idea – and use the official updater while Luma v9.1 is loaded.

_______________________
* downgraded my system

 

[Quantumcat]

Just tested it and can confirm: current Luma v10.0.1 with official firmware on 4.5.0-10 also results in double black screen for me* and the O3DSXL can only be turned off by holding power for some seconds. Loads normally with Luma v9.1

Some more tests should be done, but it seems newest Luma broke compatibility with very old firmware. That's bad because if somebody – like you – follows the guide normally, they end up with latest Luma and never even come to this point:
https://3ds.hacks.guide/finalizing-setup#section-ii---updating-the-system
without downgrading Luma first.

Create a backup first – always a good idea – and use the official updater while Luma v9.1 is loaded.

_______________________
* downgraded my system

Wow I didn't think of the fact that you don't get told to update until later. Thanks for testing. Someone should create an issue on the guide's repo so it gets fixed.

 

[jonm]

Total noob here, never even held a 3ds before, got a 3ds xl yesterday, had 4.5E installed so followed hacks guide, latest versions of all tools, used soundhax, installed boot9strap, booted into Luma 10.0.1 settings. Pressed start to save settings.

After that, reboot to black screen. Used Luma 9 boot.firm, and console boots fine. Godmode also loads.

But not Luma 10. If I delete luma config, Luma 10 again boots to settings, after saving settings, reboots to black screen. Select, or Start, doesn't work on this black screen.

Another noob here, just tried to install the latest Luma on an old 3DS with 4.4, same issue with black screen after the first config screen. I did what PoiRan did and used the v9 boot and manage to load the home screen,

If I were to update my firmware what disadvantages would there be on a newer firmware and whats the best way to update? thanks for the help!

 

[KleinesSinchen]

Another noob here, just tried to install the latest Luma on an old 3DS with 4.4, same issue with black screen after the first config screen. I did what PoiRan did and used the v9 boot and manage to load the home screen,

If I were to update my firmware what disadvantages would there be on a newer firmware and whats the best way to update? thanks for the help!

No disadvantages in higher firmware. You can update the firmware normally with System Settings like a normal, unhacked System. You will not lose CFW by updating.

Seems there is a regression in Luma 10 preventing booting on 4.x firmware. I tested some other firmware versions (so far no other version besides 4.x seems to be affected) and will continue the tests tomorrow or a day later.

https://gbatemp.net/threads/very-old-3ds-firmware-versions-and-luma.543141/