Hacking Easy Way to Hack ANY 3DS! (This method is way easier than Plailect's Guide!)

[linuxares]

how come this isn't locked ?

Since it's not a violation of our rules. Therefore the thread is still open. Their guide technically work no?

 

[peteruk]

Since it's not a violation of our rules. Therefore the thread is still open. Their guide technically work no?

It was more of a rhetorical question tbh, but seeing as you're asking I think it brings confusion as guides can be outdated very quickly. For the same reason the majority of us on here frequently recommend against following YouTube guides.

The guide is the guide and will always be the guide, that's all really.

 

[KleinesSinchen]

I followed this thread only partially and thought long if replying would do any good. I’m ready to accept @dwain12435 had good intentions when writing this (and putting some effort in it). Nevertheless my comments why I don’t think having yet another guide is a good idea and what I think is dangerous here; making the guide shorter (“easier”) by omitting steps is not a good idea either.

1. Not mentioning hardware testing the SD.
   • Fake or defective or corrupted SDs can cause serious trouble.
   • If everything seemingly worked good and the NAND image is written to a bad SD this might lead to impossibility of NAND restore and/or secondary damage if the backup is needed at some point.
2. Missing setup Luma3DS boot.firm to CTRNAND. If the console SD reader fails at some point this makes the console a full brick. Not completely missing. Still not optimal since the script self-deletes.
   
3. I’m not very happy with so called “convenient all-in-one-packages" in order to only have to download and extract a single archive. Those require the author to constantly monitor for necessary updates and will most likely be outdated pretty soon.
   • The same is true for the tutorial: It has to be maintained – like the “official” guide.
   • Like video guides, another resource makes troubleshooting and helping newbies harder. If everybody used the “official” guide it would be so much easier to help.
4. Official GodMode9 scripts (Megascript) are missing in the package. Only an incomplete replacement. Why?
   • The uninstall part of the script in the package looks pretty short and relies on having native firmware already on SD if I got this correctly.
     
   • The backup option in this script doesn''t include the serial number but names the image "System Backup.bin" This gets confusing for people with multiple consoles.
5. DSP dumping is missing.

My conclusion: Incomplete, potentially dangerous in special cases.

Since it's not a violation of our rules. Therefore the thread is still open. Their guide technically work no?

As for that question: As far as I can see this it should technically work, yes. Could not verify the new method on my test machine (always got stuck on red screen on trying to start slotTool – but this particular console is far from representative) and ended up without CFW.

 

[E1ite007]

Since it's not a violation of our rules. Therefore the thread is still open. Their guide technically work no?

Yeah, @LinusRG tutorial for not getting banned also work and the thread was closed 'cause being irrelevant, and potentially dangerous.

 

[PabloMK7]

Since it's not a violation of our rules. Therefore the thread is still open. Their guide technically work no?

Yeah, @LinusRG tutorial for not getting banned also work and the thread was closed 'cause being irrelevant, and potentially dangerous.

This guide presents a potential risk. Imagine Nintendo releases a new system version, which breaks current methods of installing and causes old guides to brick. While the official guide is maintained by a lot of knowledgeable people, this guide is only maintained by a single person which may or may not update the guide. Also, seeing the claims this user made, they look a bit selfish.

NOTE: Plailect's Guide has now added this method, but I am going to leave this guide up, since I worked hard writing this guide. (And in my opinion, this guide is simpler than Plailect's Guide, since you only need to download one file.)

For me, this is enough to not trust this user and this guide, including any claims that it will be updated.
Also, as many other users said, it will cause a pain to the entire community as they try to help users who made the mistake of following outdated guides.

 

[linuxares]

Yeah, @LinusRG tutorial for not getting banned also work and the thread was closed 'cause being irrelevant, and potentially dangerous.

Correct! This guide however is update to date at this very moment isn't it? Is it dangerous tho? I don't have a 3ds to try it on.

 

[E1ite007]

Correct! This guide however is update to date at this very moment isn't it? Is it dangerous tho? I don't have a 3ds to try it on.

Fortunately @KleinesSinchen has already test this guide.

 

[linuxares]

Fortunately @KleinesSinchen has already test this guide.

2nd point is the biggest red flag... I'll discuss with the other mods.

 

[Deleted User]

2. Missing setup Luma3DS boot.firm to CTRNAND. If the console SD reader fails at some point this makes the console a full brick.

Actually, the Temporary.gm9 script takes care of this. The Temporary.gm9 script also pits the Original Firmware in the correct location on the SD Card, allowing the uninstall script to work.

 

[KleinesSinchen]

Actually, the Temporary.gm9 script takes care of this. The Temporary.gm9 script also pits the Original Firmware in the correct location on the SD Card, allowing the uninstall script to work.

Okay. Good. Didn't see this. But it shows the problem: All members helping in the 3DS section are used to the "official guide" and the scripts and everything. If a new guide pops up, with custom scripts, this means spending hours to analyse it and maybe test it. You can blame me only partially for not sacrificing even more of my free time. (Same with the videos – it is so tedious to react to problems caused by random YouTube guides.) Why would this be a good idea? Improving on existing methods and descriptions is something different than reinventing the wheel. Understanding all this (and comparing it to the known guide) is hard work for anybody wanting to help users.

I really don't want to offend you or anything like that. I can clearly see that you spent hours too. The question is: Why?​

It took years for The Guide to become what it is now. Thoroughly tested and as noob-proof as possible. The guide is not long because it is complicated. It is long because it is extremely simplified and holds the users hand on every step while maintaining a maximum of security providing links to the latest versions of the needed software. Creating a new guide, possibly easier and faster, with the same good quality would require a lot of testing – including the reactions of some beginners. Being short is not sufficient for being noob-friendly. I get it, many people nowadays don't want to read. "tl;dr" But this does not change the fact, that softmodding a console requires at least a basic knowledge and therefore a somewhat detailed explanation.

I've now noticed that the Temporary.gm9 self-deletes (makes sense with that name). What if Luma3DS or GodMode9 gets an update? That would mean updating boot.firm and 1:/rw/luma/payloads/GodMode9.firm manually (or adding the Megascript). It is hard enough convince beginners to update Luma on SD and CTRNAND while having an semi-automatic option (link to here). Still there have been a lot of cases with "Failed to apply 1 FIRM patch(es)" on corrupted SDs while the failsafe on CTRNAND was outdated. With manual copying… no way.

Fine. The temporary script takes care of proving native firm for uninstallation with the other custom script. Neither your guide nor the script contains any warning about what can happen on B9S removal while the uninstall option is included.

Writing a new guide from scratch is not that easy. Please address these problems.

 

[E1ite007]

The question is: Why?​

I'm not OP, but I kinda know the answer from the experience of all the years seen how others make "ultimate" guides.
'Cause they think mostly, is easy. They think once is written, it will remain "ultimate" forever, cause the title implies it.
Not that OP thinks that way, of 'course he wants to help, but they think is easy to surpass the fool-proof nature of the official guide.

Maybe is easier this guide than the official, but it avoids some stuff and warnings that the official guide includes, and it packs everything onto a single download, and troubleshooting some step, or verifying some files becomes harder.
That's why this guide shouldn't be considered superior to the official one, not even OP should think that.

 

[Deleted User]

I'm not OP, but I kinda know the answer from the experience of all the years seen how others make "ultimate" guides.
'Cause they think mostly, is easy. They think once is written, it will remain "ultimate" forever, cause the title implies it.
Not that OP thinks that way, of 'course he wants to help, but they think is easy to surpass the fool-proof nature of the official guide.

Maybe is easier this guide than the official, but it avoids some stuff and warnings that the official guide includes, and it packs everything onto a single download, and troubleshooting some step, or verifying some files becomes harder.
That's why this guide shouldn't be considered superior to the official one, not even OP should think that.

This was written before the "official" slotTool new-browserhax guide came out. I would not have written this guide if the "official" one had already been written.

 

[Deleted User]

As far as I can see this it should technically work, yes. Could not verify the new method on my test machine (always got stuck on red screen on trying to start slotTool – but this particular console is far from representative) and ended up without CFW.

This can be caused by a bad download. Try deleting all of the files you downloaded from your SD Card and then re-download them.

 

[NightScript]

This was written before the "official" slotTool new-browserhax guide came out. I would not have written this guide if the "official" one had already been written.

Why didn't you try to reach out to them and work together instead of trying to do things for clout though?

 

[Deleted User]

Why didn't you try to reach out to them and work together instead of trying to do things for clout though?

I did look at the github site, but a request for slotTool and new-browserhax was already there, so I made this guide.

 

[NightScript]

I did look at the github site, but a request for slotTool and new-browserhax was already there, so I made this guide.

could have waited or sent in a pull request

 

[linuxares]

Well we discussed this. We do not recommend this guide at all, since it's unsafe. We strongly recommend the guide we all love and use. But stop responding here and the thread will fall in to obscurity if you don't like it.

 

[Deleted User]

could have waited or sent in a pull request

There already was a pull request.

 

[lilyuwuu]

Edit: main comment was removed, will keep this part here?

There might not be any major issues that would render the guide unusable or cause any severe issues with the console, but people have already pointed out possible minor/medium issues, such as:

- GM9Megascript is replaced with whatever scripts you have, in the interest of "bloat" I guess? The issue is that there are other useful things in the megascript that people might want to do, and your script seems to have uninstalling CFW front and center, something that should never be encouraged.

- You seem to copy native firm to the payloads folder. While that might be good on your own setup, on the setup of a random person it is potentially dangerous should they ever launch it and update the console. People shouldn't be able to easily boot stock unless they have an explicit need, in the interest of preventing bricks.

- The page doesn't account for people being unable to make a nand backup due to lack of space (cough cough, 2gb sd cards).

- The NAND backup will only ever have one name, with no date or serial number to identify it. This isn't the Decrypt9 days of NANDmin.bin anymore; you should take advantage of the fact that it's easy to distinguish NAND backups these days.

- DSP isn't dumped, so homebrew sound won't work.

- You say to set the HB title to any app... why? The standard is download play because it's known to work; there can be issues when people use health and safety for whatever reason. There also isn't any need to save the configuration since you're immediately changing it to hblauncher_loader anyway, unless you're setting the takeover title to system settings (and why would anyone ever do that).

- RTC offset isn't set to 0 through Rosalina NTP sync or ctr no timeoffset.

I get that you worked hard on this guide. It sucks to have hard work "criticized" by everyone. But when you're pushing your own guide because you want others to use it "because it works", it reflects poorly on your character.

 

[TurdPooCharger]

Oh wow.

The above poster (Lily) is a long time local of the Nintendo Homebrew discord who helps out those in need. I believe she along with a few others are rotating moderators of that channel.

You know it's bad when someone from a different 3DS community, who knows her chops, decides to make an account here for the sole purpose to critique.