Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[squall14716]

CTR Bootmanager since it's a full fledged manager with menu and worked just fine before.

Anyway if thats the problem, then there is still a bug in aurei.

It's not a bug, it's a specifically mentioned limitation with a fix provided.

http://www8.zippyshare.com/v/UioYD4Mt/file.html

Use the patcher provided pathchanger folder. Drag AuReiNand's arm9loaderhax.bin onto the exe, type in the path/name that you're using (for me, it's AuReiNand.bin) and voila.

 

[AkGBA]

The path is hardcoded since i've modified the src.

Use the path patcher if you use a boot manager. Period.

 

[astronautlevel]

The path is hardcoded since i've modified the src.

http://gbatemp.net/threads/aureinand-n3ds-o3ds-a9lh.411110/page-372#post-6248500

Use the path patcher to make sure you did it right.

 

[hominid9]

Thank you all for the help. Now it works perfectly.

 

[Pacman`]

The tradeoff is you can't connect to the regular eShop, so keep that in mind if you turn it on (will work fine again when you turn the patch off).

What do you mean by the "regular eshop"?
I have the Use DEVUNIT info option ON and eShop works fine.

Edit: It's really called "Use developer UNITINFO" for those interested

 

[liomajor]

http://gbatemp.net/threads/aureinand-n3ds-o3ds-a9lh.411110/page-372#post-6248500

Use the path patcher to make sure you did it right.

Ok, agb works again, but still the problem that ntr only boots in sysnand mode after opening system setting once. Without only blackscreen.

 

[Omegadrien]

What do you mean by the "regular eshop"?
I have the Use DEVUNIT info option ON and eShop works fine.

Edit: It's really called "Use developer UNITINFO" for those interested

Seriously? With me (when it's activated) i have the 022-2452 error code when i try to connect the 3ds on eShop...

 

[Pacman`]

Seriously? With me (when it's activated) i have the 022-2452 error code when i try to connect the 3ds on eShop...

Yep, I just tried with AuReiNand_v4.2.4fabe1f (working N3DS CPU patch from @TuxSH)

Edit: USA eShop

 

[Omegadrien]

Yep, I just tried with AuReiNand_v4.2.4fabe1f (working N3DS CPU patch from @TuxSH)

Are you sure you have activated the DEVUNIT info option?
https://gbatemp.net/threads/after-running-ntr-3-4-i-get-022-2452.422683/#post-6251330

 

[Pacman`]

Are you sure you have activated the DEVUNIT info option?
https://gbatemp.net/threads/after-running-ntr-3-4-i-get-022-2452.422683/#post-6251330

I'm NOT running NTR though.
I just set that "Use developer UNITINFO" option to ON in aureinand settings menu.

I turned it OFF now, since I have no idea what it does.

 

[Omegadrien]

I'm NOT running NTR though.
I just set that "Use developer UNITINFO" optionON in aureinand settings menu.

I turned it OFF now, since I have no idea what it does.

It's just to display more info when you got the error message "an error was occurred..."

 

[astronautlevel]

I'm NOT running NTR though.
I just set that "Use developer UNITINFO" option to ON in aureinand settings menu.

I turned it OFF now, since I have no idea what it does.

It has nothing to do with NTR, where did you get that?

 

[Pacman`]

I'm running on emunand 10.7, if that's any help

 

[Lumince]

did you use the path patcher ?

I used the path changer and the gba and dsi games are a no go.

 

[driverdis]

so, how do I boot 9.0 FIRM with the latest AuReiNAND? I have firmware90.bin in the aurei folder (I also tried without it) and holding L on boot does not use 9.0 FIRM. I need to boot my RedNAND with 9.0 FIRM so I can boot Gateway for the rare situation in which I want to use it.

 

[liomajor]

so, how do I boot 9.0 FIRM with the latest AuReiNAND? I have firmware90.bin in the aurei folder (I also tried without it) and holding L on boot does not use 9.0 FIRM. I need to boot my RedNAND with 9.0 FIRM so I can boot Gateway for the rare situation in which I want to use it.

To have 9.X (sysNAND) set config to Autoboot Sysnand and Updated SysNAND.

Since 9.X only starts ntr for me going into system settings once, i've placed firmware90.bin as firmware.bin in aurei's folder.

Now ntr works properly without opening system settings first and i can boot into emunand with holding L when turning on

and it loads firm from emunand > 10.4 (sadly this way 10.2 is impossible).

 

[driverdis]

To have 9.X (sysNAND) set config to Autoboot Sysnand and Updated SysNAND.

Since 9.X only starts ntr for me going into system settings once, i've placed firmware90.bin as firmware.bin in aurei's folder.

Now ntr works properly without opening system settings first and i can boot into emunand with holding L when turning on

and it loads firm from emunand > 10.4 (sadly this way 10.2 is impossible).

My issue is different
My setup was this

10.7.0-32U SysNAND (10.2 firmware.bin for NTR)
9.2.0-20U RedNAND (9.0 firmware90.bin for Gateway Support) {Hold L on powerup} [Shows Emu9 prefix in Settings]
-----------------------------
now it is this with the new build

10.7.0-32U SysNAND (10.2 firmware.bin for NTR)
9.2.0-20U RedNAND (uses 10.2 firm? | Gateway broken) {Hold L on powerup} [shows Emu instead of Emu9 in Settings]
Holding R shows EmuA instead of Emu in Settings, not sure what changes also when doing this.

 

[DjoeN]

To have 9.X (sysNAND) set config to Autoboot Sysnand and Updated SysNAND.

Since 9.X only starts ntr for me going into system settings once, i've placed firmware90.bin as firmware.bin in aurei's folder.

Now ntr works properly without opening system settings first and i can boot into emunand with holding L when turning on

and it loads firm from emunand > 10.4 (sadly this way 10.2 is impossible).

AuReiNand should indeed have an option to set preffered firmware.bin for NTR when booting into main nand of your choice (my case EmuNand 10.7)
putting firmware.bin (10.2) for NTR compatibility, into "aurei" folder doesn't work, like @liomajor says, it boots with firmware 10.4 (or higher?)

 

[driverdis]

AuReiNand should indeed have an option to set preffered firmware.bin for NTR when booting into main nand of your choice (my case EmuNand 10.7)
putting firmware.bin (10.2) for NTR compatibility, into "aurei" folder doesn't work, like @liomajor says, it boots with firmware 10.4 (or higher?)

putting firmware.bin in the aurei folder works fine. I just did that now and was able to boot NTR 3.3 with no issues (I am not using any 10.4 mod version of NTR, I am using the 10.2 firm version)
I am on the latest AuReiNAND build with the working (v2 CPU speed patch) also.

 

[Jiro2]

How about making it work like this: The CFW looks for two files--first it looks for arm9aurei.bin, and if that is not present it looks for arm9loaderhax.bin. Instead of a hardcoded path, it picks whichever one it finds first.

If you're not using a boot manager, you install it as arm9loaderhax.bin and when it reboots it sees that arm9aurei.bin isn't found so it reboots using arm9loaderhax.bin. If you are using a boot manager, you install it as arm9aurei.bin and when it reboots it finds that and reboots using that as the path.

Alternatively, how about a config option where the user can specify "reboot as this filename"? If the user is using a boot manager, he installs it as the alternate filename, and if not he installs it as arm9loaderhax.bin. (Of course it would fail if he installs it as arm9loaderhax.bin and forgets to take the option out of the config.)