Hacking How to get my 3DS working with Luma ?

Nico128 · Apr 10, 2020

Hi!

I bought a defect New 3DS XL Zelda Edition and googling the issue (blue light turn on/off) I found the console uses a custom firmware. I asked the seller, he confirmed me.
Then I read many topics here about this common issue. I just want to say I'm a noob in this domain, I've never hacked a 3DS in the past.

I downloaded Luma3SD 10.0.1 and put boot.3dsx/boot.firm to the SD root -> problem persisted
In the SD there was a folder "luma" with arm9loaderhax.bin. I copied/pased this file to the root.

Now the 3DS shows this menu :-)
But I don't know what to do. Check checking "autoboot SysNAND", I got an error, it think it cannot find the NAND.
And why Luma is v6.6 ? I put the boot.3dsx/boot.firm v10 on the root.

Here the list on my SD card (+ arm9loaderhax.bin on root now)

Can you please help me what should I do now ?

Thank you!

Ricken · Apr 10, 2020

Nico128 said:
Hi!

I bought a defect New 3DS XL Zelda Edition and googling the issue (blue light turn on/off) I found the console uses a custom firmware. I asked the seller, he confirmed me.
Then I read many topics here about this common issue. I just want to say I'm a noob in this domain, I've never hacked a 3DS in the past.

I downloaded Luma3SD 10.0.1 and put boot.3dsx/boot.firm to the SD root -> problem persisted
In the SD there was a folder "luma" with arm9loaderhax.bin. I copied/pased this file to the root.

Now the 3DS shows this menu :-)
But I don't know what to do. Check checking "autoboot SysNAND", I got an error, it think it cannot find the NAND.
And why Luma is v6.6 ? I put the boot.3dsx/boot.firm v10 on the root.

Here the list on my SD card (+ arm9loaderhax.bin on root now)

Can you please help me what should I do now ?

Thank you!

https://3ds.hacks.guide/a9lh-to-b9s.html
^Should be all you need. b9s is basically arm9loaderhax but better; new Luma versions only support b9s

lone_wolf323 · Apr 10, 2020

Nico128 said:
Hi!

I bought a defect New 3DS XL Zelda Edition and googling the issue (blue light turn on/off) I found the console uses a custom firmware. I asked the seller, he confirmed me.
Then I read many topics here about this common issue. I just want to say I'm a noob in this domain, I've never hacked a 3DS in the past.

I downloaded Luma3SD 10.0.1 and put boot.3dsx/boot.firm to the SD root -> problem persisted
In the SD there was a folder "luma" with arm9loaderhax.bin. I copied/pased this file to the root.

Now the 3DS shows this menu :-)
But I don't know what to do. Check checking "autoboot SysNAND", I got an error, it think it cannot find the NAND.
And why Luma is v6.6 ? I put the boot.3dsx/boot.firm v10 on the root.

Here the list on my SD card (+ arm9loaderhax.bin on root now)

Can you please help me what should I do now ?

Thank you!

V6.6 is a9lh. The system will need to use the update A9LH to b9s. That would be the first thing to look at with this.

Nico128 · Apr 10, 2020

Thank you for the fast replies!
I followed the tutorial. Luma was in v10. Then I did:

Section III - Configuring Luma3DS

Press (Start) to save and reboot

And I have this error "Unable to mount CTRNAND or load the CTRNAND FIRM"
It is normal ?
Then I tried to "Continue to Finalizing Setup". I downloaded the different cia.

But I'm blocked to the section "Section II - Updating the System"
I don't understand the two remarsks in red and in blue, I don't know what the previous owner did...
Also, "Update your device by going to System Settings, then “Other Settings”
I cannot access to the home yet.

Thank you for your help!

KleinesSinchen · Apr 10, 2020

Nico128 said:
And I have this error "Unable to mount CTRNAND or load the CTRNAND FIRM"
It is normal ?

Unfortunately this is neither normal nor good.

Can you access GodMode9 by holding (Start) on power on? We need to know what is on your SYSNAND.
- Do the drives [1:] SYSNAND CTRNAND, [2:] SYSNAND TWLN and [3:] SYSNAND TWLP exist?
- If it exists, does [1:] SYSNAND CTRNAND contain normal folders (data, dbs, private, ro, rw…)
- Does GodMode9 show additional drives for EmuNAND [4:] EmUNAND CTRNAND?
Hold (Select) on power on to bring up the Luma3DS settings.
- Does it offer an option to boot into an EmuNAND?
- If so, tick the option (x) Autoboot EmuNAND for testing purposes. See if you can boot into an EmuNAND.

Nico128 said:
I don't understand the two remarsks in red and in blue, I don't know what the previous owner did...

The previous owner did use an earlier version of the guide (or similar). But hopefully they already did the restore part in the red box.
About that blue box: You might have to do that – If there is an EmuNAND on your SD.

Please do not actually modify anything on your NAND or your SD card partition table until we are sure in what state those two are.

Before any further modification backup the current status of the NAND chip to another, known good SD (containing Luma3DS boot.firm and the files and folder from latest GodMode9). Please check the SD you want to use for defects or fake if not already done recently. Store the backup on your computer.

Copy all your data from the SD to a computer. Reformat the SD to FAT32, 32kb cluster size, if bigger than 32GB and using Windows with guiformat.
Check your SD Windows, Linux, OS X.
- If you get any errors replace the SD.
- If you get no errors copy your files back on the SD.

Edit: Whatever you do, don't uninstall the custom firmware at this point!

Nico128 · Apr 10, 2020

The first thing I did when I received the 3DS is to backup the SD card, to format it with guiformat and to put back the files.

[1:] SYSNAND CTRNAND, -> yes it exists
[2:] SYSNAND TWLN -> no
[3:] SYSNAND TWLP -> no

SYSNAND CTRNAND contain normal folders (data, dbs, private, ro, rw…) -> yes
Luma3DS Does it offer an option to boot into an EmuNAND? -> no

I just did a backup of the NAND with GodMode9 (on the same SD, I hope it's ok..)

KleinesSinchen · Apr 10, 2020

Nico128 said:
The first thing I did when I received the 3DS is to backup the SD card, to format it with guiformat and to put back the files.

[1:] SYSNAND CTRNAND, -> yes it exists
[2:] SYSNAND TWLN -> no
[3:] SYSNAND TWLP -> no

SYSNAND CTRNAND contain normal folders (data, dbs, private, ro, rw…) -> yes
Luma3DS Does it offer an option to boot into an EmuNAND? -> no

I just did a backup of the NAND with GodMode9 (on the same SD, I hope it's ok..)

No EmuNAND, no NAND image on the SD (at least I didn't find it in your great list.txt file – but there is 2.1.0-4E_ctrtransfer_o3ds.bin (as expected for A9LH installation). Seems the console is in some kind of "Frankenfirm" state. I came later to 3DS modding; what I know of A9LH installation is it worked like this:

Backup current NAND
Downgrade to 2.1
Install A9LH while on 2.1
Restore NAND backup preserving the A9LH exploit (safe NAND restore)

If the last step is omitted this leaves the New 3DS(XL) consoles in a bad state. I guess the image from the first step doesn't even exist anymore.

Without the original backup you will probably need to use CTRTransfer Type D9 which just saw an update: v1.6. And this update mentions missing TWLN/TWLP on badly done A9LH installation. This is a lot of reading. You should definitely read carefully.

https://github.com/TurdPooCharger/CTRTransfer-Type-D9/releases/tag/v1.6

I can't be a great help at this point anymore.

Anyway: Good luck!

======================================================
= @TurdPooCharger, please. Your magic is needed at this point.=
======================================================

Nico128 · Apr 10, 2020

Thank you. I asked the previous owner if he still have a backup of the NAND. I'm waiting for his answer.

If I can't succeed in fixing the console, I'm going to find another New 3DS XL in order to repair this 3DS Majora Mask Edition.
Should I replace the motherboard or only the Bios ?

I'm not sure how to start the tutorial (see attached pictures).
- When I start the tuto from Github it says "Launch Nintendo 3DS Sound". But how ? lol...
- On the topic of gbatemp for CTRTransfer (Type D9), it says to start the script. I started it, it asked me if my 3DS experienced a blue screen of death. I answered no and it went back to the menu. Should I say yes ? If yes, the sript asked me the permission to write on the sysnand (I didn't want to fo further)

Thx!

TurdPooCharger · Apr 10, 2020

CTRTransfer (Type D9) - CTRTransfer

See bulletin #5 under Bricks that this can fix.

Edit 1 - For the 2.1.0_SOFTBRICK_SCENARIO, it backs up the currently bricked SysNAND for you.
Edit 2 - Nvm about the currently empty bulletin #5. See if your n3DSXL has these:

sdmc:/CTRTransfer/<serial>_nand.bin
sdmc:/CTRTransfer/<serial>_nand.bin.sha

Edit 3 - If you don't have those NAND files mentioned in Edit 2, you can still fix this 2.1.0 downgrade brick as if it was a bootrom 8046 softbrick. If that's not enough, you might need to run the CTRTransfer again for the script to do standard firmware repair.

Nico128 · Apr 10, 2020

I'm sorry but I'm not sure what which section exactly I must follow. Yes the section "[New 3DS only] Franken firmware due to 2.1.0 [...]" but it shows only a screenshot with Nintendo 3DS Sound, the Homebrew Launcher, ...

But are the instructions the same if the problem is one of these ones ?

Files and folders that are partially or fully deleted off the [1:] SYSNAND CTRNAND.
The [1:] SYSNAND CTRNAND is missing.
Strange '?' files that are stubbornly stuck in CTRNAND or cannot be deleted/replaced by conventional means.
The system turns on with Blue Screens of Death.
[New 3DS only] Franken firmware due to 2.1.0 downgrade from older A9LH guide followed by newer (2xrsa) B9S guide.

So...after executing point 9) CTRTransfer and enable to write permission, I should be able to start the home 3DS and run the Nintendo 3DS Camera at point 12) ? (see attached pictures)

TurdPooCharger · Apr 10, 2020

Nico128 said:
I'm sorry but I'm not sure what which section exactly I must follow. Yes the section "[New 3DS only] Franken firmware due to 2.1.0 [...]" but it shows only a screenshot with Nintendo 3DS Sound, the Homebrew Launcher, ...

But are the instructions the same if the problem is one of these ones ?

Files and folders that are partially or fully deleted off the [1:] SYSNAND CTRNAND.

The [1:] SYSNAND CTRNAND is missing.

Strange '?' files that are stubbornly stuck in CTRNAND or cannot be deleted/replaced by conventional means.

The system turns on with Blue Screens of Death.

[New 3DS only] Franken firmware due to 2.1.0 downgrade from older A9LH guide followed by newer (2xrsa) B9S guide.

So...after executing point 9) CTRTransfer and enable to write permission, I should be able to start the home 3DS and run the Nintendo 3DS Camera at point 12) ? (see attached pictures)

My bad. I wrote that bulletin point #5 yesterday and haven't finished it yet. Just woke up the last hour forgetting that still needs some work done to it. I added some late edits in my post #9 above yours regarding that.

The last person (~~your buddy~~ the seller) who hacked that n3DSXL should have had a backed up SysNAND image that was dumped by SafeCTRTransfer when the n3DSXL was downgraded to 2.1.0. It should be located and named something like this:

sdmc:/CTRTransfer/QW12345678_nand.bin
sdmc:/CTRTransfer/QW12345678_nand.bin.sha

If you don't have those in place, the CTRTransfer will default to treating this as it was a bootrom 8046 softbrick. You can run CTRTransfer twice to fix this if you don't have that original SysNAND image.

Nico128 · Apr 13, 2020

Hi. Thank you the the explanation. The seller replied me. He doesn't have any backup...

I started GodMode9 -> Script -> CTRTransfer
Then I have to select a file. Should I use 11.5.0-38E_ctrtransfer_n3ds ?

TurdPooCharger · Apr 13, 2020

Nico128 said:
Hi. Thank you the the explanation. The seller replied me. He doesn't have any backup...

I started GodMode9 -> Script -> CTRTransfer
Then I have to select a file. Should I use 11.5.0-38E_ctrtransfer_n3ds ?

Can you download the quick fix v1.7b release of the CTRTransfer (Type D9) and replace the script before running CTRTransfer? I found a major bug in the previous v1.6 that would have erased the CTRNAND partition for a 2.1.0 downgraded n3DS(XL) system.

Edit 1 - You can still fix this n3DSXL with CTRTransfer (Type D9) even without the original SysNAND *.bin image. Just pick the appropriate n3DS ctrtransfer image. It doesn't have to be EUR if you want to region change the 3DS firmware to JPN, USA, KOR.

Edit 2 - When asked if it's a bootrom 8046 softbrick, just accept and continue as is following the Instructions.

Nico128 · Apr 13, 2020

I executed CTRTransfer 2x.
The home menu of the 3DS didn't boot and I remembered that I forgot to to copy the v1.7. My bad... I connected my SD to the laptop to copy the file 11.5.0-38E_ctrtransfer_n3ds and CTRTransfer 1.7 But then I forgot it.

Then I started CTRTransfer v1.7 but I don't know if it executed something, it displays "23". When I press A, it returns to the menu.

Now I have
[2:] SYSNAND TWLN
[3:] SYSNAND TWLP

Luma3DS doesn't offer an option to boot into an EmuNAND.

TurdPooCharger · Apr 13, 2020

Nico128 said:
I executed CTRTransfer 2x.
The home menu of the 3DS didn't boot and I remembered that I forgot to to copy the v1.7. My bad... I connected my SD to the laptop to copy the file 11.5.0-38E_ctrtransfer_n3ds and CTRTransfer 1.7 But then I forgot it.

Then I started CTRTransfer v1.7 but I don't know if it executed something, it displays "23". When I press A, it returns to the menu.

Now I have
[2:] SYSNAND TWLN
[3:] SYSNAND TWLP

Luma3DS doesn't offer an option to boot into an EmuNAND.

Shit.

Is the [1:] SYSNAND CTRNAND missing now? Did you use the previous v1.6 of the CTRTransfer (Type D9)?

Nico128 · Apr 13, 2020

Yes [1:] SYSNAND CTRNAND is missing.

Yes I ran 2x v1.6 (my mistake...) + 1x v1.7 (but I guess it didn't do anything)
If now the 3DS is in too bad condtion, I don't want to waste your time. We can stop unless your are interrested by the challenge to recover it.

TurdPooCharger · Apr 13, 2020

Nico128 said:
Yes [1:] SYSNAND CTRNAND is missing.

Yes I ran 2x v1.6 (my mistake...) + 1x v1.7 (but I guess it didn't do anything)
If now the 3DS is in too bad condtion, I don't want to waste your time. We can stop unless your are interrested by the challenge to recover it.

No, it's not you. I do lots of troubleshooting and unbricking 3DS'es around here. Yours is probably my biggest mistake I've made so far with bad advice.

Did you make a backup of that n3DSXL's SysNAND image before using v1.6 of CTRTransfer (Type D9)? Without it, I'm terribly sorry as your n3DSXL's console unique files won't be recoverable.

Nico128 · Apr 13, 2020

I have this backup I've previously done https://gbatemp.net/threads/how-to-get-my-3ds-working-with-luma.562081/#post-9007821

I just tried Scripts -> GM9Megascript -> restore (Safe) and I have this errpr (attached picture)
line 132: find fail
find I:/twin.bin NULL

I have now [7:] and [I:]

TurdPooCharger · Apr 13, 2020

Nico128 said:
I have this backup I've previously https://gbatemp.net/threads/how-to-get-my-3ds-working-with-luma.562081/#post-9007821

I just tried Scripts -> GM9Megascript -> restore (Safe) and I have this errpr (attached picture)

Oh thank goodness!

The backed up semi-bricked 2.1.0 SysNAND *.bin image can't be Restore (Safe) because of the mismatched partition size of the [1:] SYSNAND CTRNAND (ctrnand_full.bin) and the missing [2:] SYSNAND TWLN (twln.bin) and [3:] SYSNAND TWLP (twlp.bin).

I'm going to be asking you do something not recommended to the average user. I want you to manually (Forced) restore the 2.1.0 nand image. It's the only way you'll be able to retrieve the lost CTRNAND partition.

In GodMode9, go in the [0:] SDCARD () directory and press (Y) on the <mmddyy>_<serial>_sysnand_000.bin (Size: 943.0 MB) to [CLIPBOARD] select the image file.
- Please make sure the correct image or file is chosen. Reflashing the wrong file will lead to a bootrom 8046 softbrick.
- If the wrong choice is made, press (SELECT) button to reset the [CLIPBOARD].
Back out with (B) button. Go in the [S:] SYSNAND VIRTUAL. Press (A) on nand.bin → Inject data @offset → | 00000000 | → <A> yes → button combo → etc.
- Do not change the offset! It has to be exactly all zeros. Don't disturb or cancel with (B). Allow the forced reflash to complete.
Due to reverting the firmware back to its 2.1.0 frankenfirm state, GodMode9 will not properly read or write to the partitions. The program will need to be reset. Press the (POWER) button to turn off the n3DSXL. Hope and pray your n3DSXL still boots up the next time you turn it on.
Return to GodMode9. Rerun the CTRTransfer (Type D9) to repair the 3DS firmware but this time around with intact CTRNAND partition.
- (HOME) button → Scripts... → CTRTransfer (Type D9) → CTRTransfer.
- sdmc:/gm9/scripts/CTRTransfer (Type D9).gm9 (version 1.7b)
- sdmc:/gm9/in/11.5.0-38E_ctrtransfer_n3ds.bin
- sdmc:/gm9/in/11.5.0-38E_ctrtransfer_n3ds.bin.sha

Nico128 · Apr 13, 2020

Tour instructions are very cleared, thank you!
Good news, the 3DS now boots to the home menu

Steps 1-3 were successful. For step 4, I ran CTRTransfer (Type D9) v1.7 only once and it did all the jobs successfully (no need to run it twice).
Then I rebooted the console and :grog:

What are the next steps now ?
- Make a backup (backup the current status of the NAND)
- Upgrade to firmware to the lastest version ? Or is 11.5.0-38E alreay the lastest ?
- Do you have any guide qui explain what I must not do ? To play online, to use the shop, to update the firmware via the official methods (via online, via a game, ...) ?

Thank you very much to all of you!!

Hacking How to get my 3DS working with Luma ?

Member

Attachments

Searching for the air to breathe~

Well-Known Member

Member

Attachments

GBAtemp's Backup Reminder + Fearless Testing Sina

Member

Attachments

GBAtemp's Backup Reminder + Fearless Testing Sina

Member

Attachments

Meh.

Member

Attachments

Meh.

Member

Meh.

Member

Attachments

Meh.

Member

Attachments

Meh.

Member

Meh.

Member

Attachments

Similar threads

Popular threads in this forum