Hacking Luma3DS - Noob-proof 3DS Custom Firmware

Status
Not open for further replies.

wiiuser2

Well-Known Member
Member
Joined
Sep 12, 2009
Messages
186
Trophies
0
XP
211
Country
Netherlands
Hi I upgraded mine A9LH O3DS XL from ARN 4.1 to Luma3DS 5.4 using this upgrade guide here:

https://github.com/AuroraWright/Lum...ade#upgrading-from-arn-43-or-older-to-luma3ds

After upgrading, I did the initial setup, and check marked "Force A9LH detectection" and "SHow current NAND in System Settings".

All works as intended (1st emuNAND boots by default, sysNAND boots by holding L, 2nd emuNAND boots by holding B)

But none of the payloads works (just blank screen with backlight on), I have named them all in the newer format and I guess I no more have to hold L key with the payload key anymore.

Kindly let me know what went wrong, why none of the payloads work. I have start_d9.bin (Decrypt9), x_emund9.bin (EmuNAND9), y_uncart.bin (UnCart) in the luma/payloads folder.
Are you sure you use the latest versions of the payloads?
 

Just3DS

Well-Known Member
Member
Joined
Jan 31, 2015
Messages
440
Trophies
0
XP
237
Country
Are you sure you use the latest versions of the payloads?
No, I just renamed them... but none of the payloads works. I will try replacing them with new one right now.

EDIT: Thanks! Using latest payloads for each worked. One thing I noticed that for start button payload you still need to hold L key for it to work.
 
Last edited by Just3DS,

Yudowat

That one guy that shows up occasionally
Member
Joined
Jun 12, 2015
Messages
552
Trophies
0
XP
341
Country
Australia
I think not. you have to modify source code to patch it.

Sent from my 403SC using Tapatalk
Ah that's such a shame. Might look into something else then, Thanks!
edit: actually, i saw a ton of stuff about it much earlier on in this thread, if someone that knows for sure could comment that would be teriffic :)
 
Last edited by Yudowat,

Just3DS

Well-Known Member
Member
Joined
Jan 31, 2015
Messages
440
Trophies
0
XP
237
Country
Following the guide for region changing and using eShop on O3DS XL for Luma3DS

https://github.com/Plailect/Guide/wiki/Region-Changing

I tried it for 2nd emuNAND (although the guide is meant for sysNAND)

System stock SecureInfo_A is EUR in emuNAND whereas SecureInfo_C is JPN in emuNAND (changed according to guide)

Apparently Luma3DS doesn't seem to read SecureInfo_C on boot from 2nd emuNAND, so it is using stock SecureInfo_A

So it shows English language with black boxes (because I deleted those titles), instead of the JPN language and titles as intended

Alternatively, using modified SecureInfo_A to JPN and opening JPN eShop does not work, it gives error 005-4270 first, then error 007-2670, and then error 007-2001

Is there anyway to force read SecureInfo_C on 2nd emuNAND using Luma3DS?
 
Last edited by Just3DS,

pbanj

The "friendly" neighborhood sandwich
Member
Joined
Dec 29, 2014
Messages
2,754
Trophies
1
Location
in a ziploc
Website
pbanjin.space
XP
1,680
Country
United States
Ah that's such a shame. Might look into something else then, Thanks!
edit: actually, i saw a ton of stuff about it much earlier on in this thread, if someone that knows for sure could comment that would be teriffic :)
Iirc it does, its how its doing the ver change in system settings and I think a few other things.
 
  • Like
Reactions: Gray_Jack

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,060
Trophies
1
XP
972
Country
United States
oh , safesysupdater !? that sounds easy enough , i shall try it later on thank u.

edit: any U.S version of 9.2 emuNAND is fine yes ? (from the iso site)

edit1: and ooh , i almost forgot , so if i use the sysupdater app and then install the 9.2 emuNAND downgrade cia files will that automatically downgrade emuNAND and not touch sysNAND yes?

so steps for me with updated sysNAND only would be these v

1.creating/restoring a backup of my emuNAND (my backup is a 10.x fw)
2.download the U.S emuNAND 9.2 update cia files put them in updates folder on sd card.
3.use sysupdater and install the cias off updates folder.

yes?

Why not just restore SysNAND_original.bin to your EmuNAND? Already unlinked, and already on 9.2. You restored EmuNAND to SysNAND. If you restore it to EmuNAND as well, your NANDs WILL be linked. So you will need to run TinyFormat.
 
Last edited by Kazuma77,
  • Like
Reactions: proflayton123

SirByte

Well-Known Member
Member
Joined
Dec 30, 2012
Messages
524
Trophies
1
XP
1,059
Country
Canada
I've used a previous version of the region change manual to create an EUR EmuNAND (SysNAND is USA) and am using a 'public' EUR SecureInfo_A; by editing your own don't you invalidate the RSA2048 signature, or is the whole idea that Luma patches any SecureInfo_A checks?
 

daxtsu

Well-Known Member
Member
Joined
Jun 9, 2007
Messages
5,627
Trophies
2
XP
5,194
Country
Antarctica
I've used a previous version of the region change manual to create an EUR EmuNAND (SysNAND is USA) and am using a 'public' EUR SecureInfo_A; by editing your own don't you invalidate the RSA2048 signature, or is the whole idea that Luma patches any SecureInfo_A checks?

It patches those checks, but if you ever go back to a "clean" environment without sig checks being disabled, the system won't boot without an untouched SecureInfo_A, of course. On a stock system with no emuNAND or A9LH that would mean it'd brick effectively (assuming one was silly enough to flash it to an unprotected sysNAND like that).
 
Last edited by daxtsu,

Ramzh

I am a living meme
Member
Joined
Nov 29, 2014
Messages
328
Trophies
0
Location
31 32 37 2E 30 2E 30 2E 31
XP
201
Country
I just want make sure about one thing, can I restore the sysNAND 9.2.0-20E (no A9LHAX) with D9 to have a clean 9.2 and then I after I finished working on this firmware go back to sysNAND-A9LHAX with D9 and Luma CFW?
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Psionic Roshambo @ Psionic Roshambo: https://youtu.be/gXtJ12EeaOs?si=ESC50o7Vr5sUh71I