Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Ooka]

Looks like we need a telemetry patch integrated into luma.

It has been discovered that any time you load a cia while online, nintendo is informed.

This seems to be the cause of the banwave.

The authors don't have any intent of blocking this. Unless they start covering their tracks now that they look silly. :3

 

[ombus]

Looks like we need a telemetry patch integrated into luma.

It has been discovered that any time you load a cia while online, nintendo is informed.

This seems to be the cause of the banwave.

if this is true then lazy nintendo..

 

[Zaphod77]

The problem is some legit homebrew apps are useless when not online. so to use them we need some sort of blocker to stop nintendo from getting telemetry.

A non complete list follows

1) luma updates
2) freeshop
3) homebr3w

there are probably others.

 

[Plailect]

The problem is some legit homebrew apps are useless when not online. so to use them we need some sort of blocker to stop nintendo from getting telemetry.

A non complete list follows

1) luma updates
2) freeshop
3) homebr3w

there are probably others.

Being banned only limits your access to Nintendo's online services, not the entire internet...

 

[Zaphod77]

Well it's possible for a system that doesn't pirate anything to be still banned. if that's the person's only system, they lose the ability to play online even though they do not pirate.

These bans hurt legit cfw users more than pirates.

and there are unconfirmed reports of people also having their clean systems banned, because of this exact fact. if you keep hacked stuff on one system, and never do stuff online with it, then nintendo knows that to cost you money they have to ban the clean one too.

I agree that if true, that's totally unfair, but i understand the logic.

So i think a solution to prevent bans of legit cfw users (say ntr streaming?) from getting banned would be good.

 

[zoogie]

I made a little thing that should make the switch from a9lh to boot9strap a little less painless:
https://github.com/zoogie/FIRMify

This will batch convert all a9lh payloads in the current directory to .firm format. Python2 or 3 and no extra libraries needed. Just run it in the sdmc:/luma/payloads directory.

 

[SnakeOil092]

Just wanted to clarify, latest hourly works perfectly.

 

[hidd12]

I guess I'll ask here as well. Chainloader menu does not boot up; when holding START, the screen flashes once, a slight pop from the speakers and the 3DS boots normally.

Tried a lot of things, I was on A9LH, moved to B9S without issues, everything works properly aside from the chainloader. Help?

 

[KunoichiZ]

I guess I'll ask here as well. Chainloader menu does not boot up; when holding START, the screen flashes once, a slight pop from the speakers and the 3DS boots normally.

Tried a lot of things, I was on A9LH, moved to B9S without issues, everything works properly aside from the chainloader. Help?

1) Try reupdating to Luma 7.1. I've seen reports that even after that, the chainloader doesn't always load for whatever reason.
2) You do have GodMode9 in your luma/payloads folder, right?

 

[hidd12]

1) Try reupdating to Luma 7.1. I've seen reports that even after that, the chainloader doesn't always load for whatever reason.
2) You do have GodMode9 in your luma/payloads folder, right?

Did, yep, even renamed it to force it to start directly by holding X.

 

[Redferne]

1) Try reupdating to Luma 7.1. I've seen reports that even after that, the chainloader doesn't always load for whatever reason.

It could be because it's the same button to enter the menu and exit it.
It happened to me once yesterday, I entered the chainloader menu and before I could select a payload it exited and load the Home menu. I wondered what happen and I realized that I was still holding Start.

 

[KunoichiZ]

It could be because it's the same button to enter the menu and exit it.
It happened to me once yesterday, I entered the chainloader menu and before I could select a payload it exited and load the Home menu. I wondered what happen and I realized that I was still holding Start.

Ah, I didn't realize there was a way to exit the chainloader without selecting an payload.

 

[tloberif]

Ah, I didn't realize there was a way to exit the chainloader without selecting an payload.

Morning dud

I update here...luma3ds with Luma Updater v2.1 and.......all work fine.

Current installed version : 7.1-8308e1a8

THANK´S

 

[hidd12]

It could be because it's the same button to enter the menu and exit it.
It happened to me once yesterday, I entered the chainloader menu and before I could select a payload it exited and load the Home menu. I wondered what happen and I realized that I was still holding Start.

Doesn't matter, renamed and tried multiple times, same thing happens

 

[pixelmasher]

I guess I'll ask here as well. Chainloader menu does not boot up; when holding START, the screen flashes once, a slight pop from the speakers and the 3DS boots normally.

Tried a lot of things, I was on A9LH, moved to B9S without issues, everything works properly aside from the chainloader. Help?

Pop sounds like a hardware issue.

 

[zoogie]

A little warning. The latest build, at least the latest hourly build available (4c87800-b9s-next) from lumaupdater, is broken. It just turns off the system on both sd and ctrnand.

Whoever is running that app should stick with the master branch and avoid the experimental ones, like b9s-next.

 

[hidd12]

Pop sounds like a hardware issue.

Can't replicate issue anywhere aside from when I try to start the chainloader. Ugh, I'm probably missing some file or smth, idk what could be the issue

EDIT: luma's payload is in NAND root, luma's folder is in /rw, rest of the payloads on sd:luma/payloads, bleh

 

[TuxSH]

A little warning. The latest build, at least the latest hourly build available (4c87800-b9s-next) from lumaupdater, is broken. It just turns off the system on both sd and ctrnand.

Whoever is running that app should stick with the master branch and avoid the experimental ones, like b9s-next.

B9S-Next requires the next branch from b9s, both will be the upcoming releases. Using Luma3DS/b9s-next with b9s v1.0 is undefined behavior and should be avoided at all costs.

Also, @zoogie https://github.com/SciresM/boot9str...a1e5#diff-9e11087a3a4c3a71e41db1c8bc151afdR30 the 0x23FFFE00 stuff is gone, requiring code change in payloads (already done by d0k3 on at least gm9).

 

[KunoichiZ]

A little warning. The latest build, at least the latest hourly build available (4c87800-b9s-next) from lumaupdater, is broken. It just turns off the system on both sd and ctrnand.

Whoever is running that app should stick with the master branch and avoid the experimental ones, like b9s-next.

It's not up to me for the hourlies. That's all on astronautlevel. They just told me the link to use. It's not my fault.

 

[SamanthaKitKat]

I'm a humongous noob, but I have a question. Can I install Luma3ds CFW on a New 3dsxl that is on FW 11.4? I've looked for the answer but haven't seen anything. I don't want to hard mod anything. I currently have Ninjhax and homebrew.
Thanks