Hacking 3DS NOOB PARADISE - Ask questions here

[anthonyplep]

Doing the Plailect guide, when setting up RedNAND for the first time, I'm supposed to open Luma up from the Homebrew Launcher. Luma opens fine, and I choose the "Show current NAND in System Settings" option and then press start to attempt to launch into Luma. I just get black screend, and I'm not sure what to attempt to try and fix this, as I obviously need Luma to launch properly for later in the guide. This is the 4th 3DS I've done and I've never gotten the problem until now. Suggestions?

 

[cbxero]

I'm planning to install Luma3ds, unfortunately I have the latest 3DS update (11.0.0). Any chance I could still install it?

--------------------- MERGED ---------------------------

Nope. Hardmod only.

 

[Temptress Cerise]

So, I have a problem that has me stumped. I'm helping a friend and followed the Plailect guide to the dot. On Part 5 "Section VI - Finalizing setup" Step 8 - Open Health and Safety (which is now FBI). Health and Safety is just Health and Safety. I instructed him to go into Decrypt9 and inject the FBI_inject_with_banner.app again, but the bottom screen flashes red and boots him back into the Homebrew Launcher. All of the button commands work, so he can boot into the Luma3DS config menu, Hourglass9, and EmuNAND9. Much appreciated for the help.

Use Hourglass9. It should be under sysNAND Backup/Restore Options. I am assuming you have A9LH setup now, since you said you can boot into it.

I'm trying to do browserhax but always get this error. What am I doing wrong? (already changed the date and time ) my system is on 10.3.0-22E

That looks like a dummy browser. Maybe someone else can chime in and confirm, but if it is as I say it is, then you'll need a cartridge based entry. Did you get to 10.3.0-22E by way of a cartridge update?

When I launch homebrew channel from the home menu (I am A9LH + LUMA + 11.0.33) it launches fine, by when I try to load a program (for example Emunand9) it just crashes back to home menu. Is this usual behavior or do I have it set up wrong?

Yes, that is completely normal. You need arm9 access for EmuNAND9, that's why we have an a9lh.bin payload for it, so we can run it a boot time. If you've setup A9LH+Luma as instructed by the guide, just hold Y at boot time.

Doing the Plailect guide, when setting up RedNAND for the first time, I'm supposed to open Luma up from the Homebrew Launcher. Luma opens fine, and I choose the "Show current NAND in System Settings" option and then press start to attempt to launch into Luma. I just get black screend, and I'm not sure what to attempt to try and fix this, as I obviously need Luma to launch properly for later in the guide. This is the 4th 3DS I've done and I've never gotten the problem until now. Suggestions?

Make sure you have all the correct files where they are supposed to be. Such as the luma folder, the luma3ds.dat and etc.
Also, black screen is actually normal, it means it has failed and you'll have to try again.

 

[EmperorOfCanada]

Yes, that is completely normal. You need arm9 access for EmuNAND9, that's why we have an a9lh.bin payload for it, so we can run it a boot time. If you've setup A9LH+Luma as instructed by the guide, just hold Y at boot time.
.

I dont actually need to use it, was just wondering if I should be concerned my homebrew channel 'wasnt working' but thanks

 

[Temptress Cerise]

I dont actually need to use it, was just wondering if I should be concerned my homebrew channel 'wasnt working' but thanks

Oh, well in that case, yeah, it's working. I see that question often, when people forget they have the a9lh.bin payloads, and are still sort of trained to the old ways of menuhax.

 

[EmperorOfCanada]

Oh, well in that case, yeah, it's working. I see that question often, when people forget they have the a9lh.bin payloads, and are still sort of trained to the old ways of menuhax.

My knowledge level is getting much better, but Ive only been at this 2 weeks, I still dont have a good 'big picture' of whats going on

 

[Temptress Cerise]

My knowledge level is getting much better, but Ive only been at this 2 weeks, I still dont have a good 'big picture' of whats going on

6 weeks here fam~ <3 You'll get there. And you'll probably end up getting corrected at times too.

 

[proflayton123]

6 weeks here fam~ <3 You'll get there. And you'll probably end up getting corrected at times too.

In the past months, specifically within terminology and stuff I've picked up quickly for abbreviations


Sent from my iPhone using Tapatalk

 

[Queno138]

I've got a question!

The A9LH payload.. is stored in sysnand right?

So what happens if that portion of sysnand corrupts for some unknown reason, use hardmod to fix?

 

[Temptress Cerise]

I've got a question!

The A9LH payload.. is stored in sysnand right?

So what happens if that portion of sysnand corrupts for some unknown reason, use hardmod to fix?

A9LH is installed onto the FIRM1/FIRM0 part of sysNAND, I am sort of fuzzy on the details, but I believe be corrupt Firm0 to force it to jump to Firm1, so it then loads our A9LH.bin payload on the SD Card. However I may be wrong on this, as I don't exactly read all the documentation pertaining to this.

However, if you want to look at how it works, there is this thread here:
https://gbatemp.net/threads/arm9loader-technical-details-and-discussion.408537/

Anyways, if for some reason that ends up corrupting in a wrong way, I guess? Yeah, you'd have to look into a hardmod to flash back a good A9LH sysNAND backup.

 

[ihaveahax]

A9LH is installed onto the FIRM1/FIRM0 part of sysNAND, I am sort of fuzzy on the details, but I believe be corrupt Firm0 to force it to jump to Firm1, so it then loads our A9LH.bin payload on the SD Card. However I may be wrong on this, as I don't exactly read all the documentation pertaining to this.

However, if you want to look at how it works, there is this thread here:
https://gbatemp.net/threads/arm9loader-technical-details-and-discussion.408537/

Anyways, if for some reason that ends up corrupting in a wrong way, I guess? Yeah, you'd have to look into a hardmod to flash back a good A9LH sysNAND backup.

payload is installed to FIRM0 (therefore counts as corrupted), FIRM1 has a specific firmware version and is not corrupted. bootrom loads FIRM0 into memory but it fails a hash/signature check. it loads FIRM1 on top of it, jumps to it because the hash/signature is valid, kernel9loader decrypts the corrupted key and uses it to decrypt the arm9 binary to garbage, it jumps to the garbage and hopefully jumps to the payload.

.....at least that's how I remember it.

 

[EmperorOfCanada]

6 weeks here fam~ <3 You'll get there. And you'll probably end up getting corrected at times too.

You know your stuff pretty well then? Mind if I open a conversation with you to pick your brain?

 

[Temptress Cerise]

payload is installed to FIRM0 (therefore counts as corrupted), FIRM1 has a specific firmware version and is not corrupted. bootrom loads FIRM0 into memory but it fails a hash/signature check. it loads FIRM1 on top of it, jumps to it because the hash/signature is valid, kernel9loader decrypts the corrupted key and uses it to decrypt the arm9 binary to garbage, it jumps to the garbage and hopefully jumps to the payload.

.....at least that's how I remember it.

Thanks for that info~ <3

You know your stuff pretty well then? Mind if I open a conversation with you to pick your brain?

I don't see why not, though if I don't know something, I'll def tell you right off the bat~

 

[Cyber Akuma]

Ok..... here goes.....

I have an original launch model 3DS on 10.7.0-32U firmware, and non-XL New 3DS on firmware version 10.6.0-31U. Neither of these are hacked...... yet. I would also like to transfer everything I can from the O3DS to the N3DS, but from what I have gathered it would be best if I hack them first before doing this, since it would otherwise require me to upgrade to firmware 11.

I just got the N3DS and pretty much have nothing on it, so I am planning to hack that first since I wouldn't risk losing anything. Of the exploitable games, I have Smash and Freakyforms, sounds like it would be easier for me to just use freakyforms than any other type of hack.

So I am looking at this guide here:
https://github.com/Plailect/Guide/wiki/Part-1-(Homebrew)

And I am also looking at the Freakyforks hack page here:
http://plutooo.github.io/freakyhax/

And that link seems to concentrate on just getting Homebrew Launcher to run. Is this necessary to hack it further, or is this a "homebrew only, nothing permanently installed" kind of hack?

Then, the 9.2.0 downgrade instructions on this link:
https://github.com/Plailect/Guide/wiki/Part-2-(9.2.0-Downgrade)

Also mentions that it's best if your 3DS is "reset", while I can't do that for my O3DS, the N3DS was pretty much that way since I just bought it, though I did have to go through initial setup to be able to even use it. Is this what they mean, or is there a way to launch the hack during the initial setup to even further reduce chances of a brick?

The downgrade page also mentioned a save manager, is it possible to run this before you do anything that can cause any kind of permanent modification to the 3DS? Losing my save data is exactly what I was worried about with the O3DS. Can these saves only be restored to the same 3DS, or a different one? If I manage to do a backup and then downgrade, can I restore the backup that was made when the 3DS was on a newer version?

The instructions also seem to be written from a much older time when menuhax and browserhax were viable, I am not sure how to use freakyforms instead of menuhax for the 9.2.0 downgrade, or the further steps.

Do these downgrade instructions work on any 3DS that's not on version 11? Is it possible to downgrade a N3DS all the way down to 2.1.0 for arm9loaderhax? 2.1.0 was way way before the N3DS's time.

Once I am fully hacked, can I still do everything I normally could do on a non-hacked system? Play online, use the eshop, install game updates/patches, etc? I am not talking about roms, but software I actually purchased on the eshop or have on cart. Could new games possibly have some kind of security that prevent them from running on a hacked system? Again, I am talking about legally purchased games on cart, not roms.

And finally, after I manage (assuming I don't screw up and brick) to fully hack my N3DS, what would be the best way to do a system transfer before I fully hack my O3DS? I don't want to fully hack my O3DS before I do a transfer since there are many steps where it can go wrong AND there is a high chance the 9.2.0 downgrade can fail since I have five years of downloads on it, as well as the ambassador program and DSiWare, just about everything that could possibly get in the way of the downgrade and brick it. Which is why I want to hack it as little as possible just long enough to perform a system transfer to the fully hacked N3DS before I format and fully hack the O3DS. Can I do a system transfer before any of the downgrade steps?

 

[Temptress Cerise]

Ok..... here goes.....

I have an original launch model 3DS on 10.7.0-32U firmware, and non-XL New 3DS on firmware version 10.6.0-31U. Neither of these are hacked...... yet. I would also like to transfer everything I can from the O3DS to the N3DS, but from what I have gathered it would be best if I hack them first before doing this, since it would otherwise require me to upgrade to firmware 11.

I just got the N3DS and pretty much have nothing on it, so I am planning to hack that first since I wouldn't risk losing anything. Of the exploitable games, I have Smash and Freakyforms, sounds like it would be easier for me to just use freakyforms than any other type of hack.

So I am looking at this guide here:
https://github.com/Plailect/Guide/wiki/Part-1-(Homebrew)

And I am also looking at the Freakyforks hack page here:
http://plutooo.github.io/freakyhax/

And that link seems to concentrate on just getting Homebrew Launcher to run. Is this necessary to hack it further, or is this a "homebrew only, nothing permanently installed" kind of hack?

Then, the 9.2.0 downgrade instructions on this link:
https://github.com/Plailect/Guide/wiki/Part-2-(9.2.0-Downgrade)

Also mentions that it's best if your 3DS is "reset", while I can't do that for my O3DS, the N3DS was pretty much that way since I just bought it, though I did have to go through initial setup to be able to even use it. Is this what they mean, or is there a way to launch the hack during the initial setup to even further reduce chances of a brick?

The downgrade page also mentioned a save manager, is it possible to run this before you do anything that can cause any kind of permanent modification to the 3DS? Losing my save data is exactly what I was worried about with the O3DS. Can these saves only be restored to the same 3DS, or a different one? If I manage to do a backup and then downgrade, can I restore the backup that was made when the 3DS was on a newer version?

The instructions also seem to be written from a much older time when menuhax and browserhax were viable, I am not sure how to use freakyforms instead of menuhax for the 9.2.0 downgrade, or the further steps.

Do these downgrade instructions work on any 3DS that's not on version 11? Is it possible to downgrade a N3DS all the way down to 2.1.0 for arm9loaderhax? 2.1.0 was way way before the N3DS's time.

Once I am fully hacked, can I still do everything I normally could do on a non-hacked system? Play online, use the eshop, install game updates/patches, etc? I am not talking about roms, but software I actually purchased on the eshop or have on cart. Could new games possibly have some kind of security that prevent them from running on a hacked system? Again, I am talking about legally purchased games on cart, not roms.

And finally, after I manage (assuming I don't screw up and brick) to fully hack my N3DS, what would be the best way to do a system transfer before I fully hack my O3DS? I don't want to fully hack my O3DS before I do a transfer since there are many steps where it can go wrong AND there is a high chance the 9.2.0 downgrade can fail since I have five years of downloads on it, as well as the ambassador program and DSiWare, just about everything that could possibly get in the way of the downgrade and brick it. Which is why I want to hack it as little as possible just long enough to perform a system transfer to the fully hacked N3DS before I format and fully hack the O3DS. Can I do a system transfer before any of the downgrade steps?

DAMN. At least you broke it down into paragraphs. OK. I gotchu fam.

Part 1 of Plailect's guide is there to help you setup Homebrew via menuhax. If you are going to use Freakyforms Deluxe, in other words Freakyhax, you'll basically skip that, and anytime in the guide it asks you to launch Homebrew, you'll have to do it with your entrypoint, Freakyhax.

Homebrew isn't permanent, you'd just have to undo whatever it is you used to set it up.

Yes, it's best to reset, as in do a System Format, especially on N3DS systems. Even if you've done the initial setup already, this does not count as a System Format. You have to do one via System Settings.

With Freakyhax as your Homebrew entry point, you can use SVDT to try and backup all your saves.
Link: https://github.com/meladroit/svdt/releases

Saves aren't tied to console, so you'd be able to restore them on any of the two systems you want. People even share their saves.

As for restoring the backup, you can't do a proper NAND backup on anything but 9.2. You need arm9 privileges for that, which Homebrew access alone does not grant, this is why we downgrade to 9.2.

I've used the steps with oot3dhax, ninjahax, and menuhax. The reason the guide uses menuhax though, is because most people would be on a system version that allows this, it also points you in the correct direction if you happen to be on 10.6, 10.7 and 11.0 (11.0 requiring a hard mode at the time of this message).

The guide is all encompassing. Meant for 2DS/o3DS and N3DS systems. Just make to use the correct files for your system type and system region, and you'll be fine. OTPHelper will unbrick 2.1 which makes it usable on n3DS. I've done it on an n3DS system, and it works, others have to!

As for the system transfer, you won't be able to. Sadly a system transfer requires internet access, and as such will ask you to update before being able to go through. You'll have to hack them both.

 

[Cyber Akuma]

As for the system transfer, you won't be able to. Sadly a system transfer requires internet access, and as such will ask you to update before being able to go through. You'll have to hack them both.

Dammit, I was afraid of that. Is there no homebrew that can trick it into thinking it has the latest or perform the transfer itself or something? I really REALLY don't want to downgrade a 3DS that has over 5 years of my data and literally every problematic program listed during the already not 100% assured 9.2.0 downgrade process without getting the data OFF of it first.

 

[Temptress Cerise]

Dammit, I was afraid of that. Is there no homebrew that can trick it into thinking it has the latest or perform the transfer itself or something? I really REALLY don't want to downgrade a 3DS that has over 5 years of my data and literally every problematic program listed during the already not 100% assured 9.2.0 downgrade process without getting the data OFF of it first.

You could look into ctr-httpwn, but I am unsure it would work.
Link: https://github.com/yellows8/ctr-httpwn

Again, for your use case, I am not sure it would work, you could look over the documentation it has and see if it could possibly work and try it out.

 

[vb_encryption_vb]

Dammit, I was afraid of that. Is there no homebrew that can trick it into thinking it has the latest or perform the transfer itself or something? I really REALLY don't want to downgrade a 3DS that has over 5 years of my data and literally every problematic program listed during the already not 100% assured 9.2.0 downgrade process without getting the data OFF of it first.

The only way to keep your data is as follows.

1. Update both systems so you can system transfer.

2. Hardmod and make a backup of sysnand 11.0 ( Put some place safe, will be needed later )

3. Format system, make backup again of 11.0 via hardmod, patch and write back. Proceed to downgrade to 9.2

4. Follow the rest of the guide, when it gets to the end, installing emunand_original.bin, use the very first dump you made of 11.0 after the system transfer. This will return your 3ds to 11.0 with a9lh with all your games, saves, etc. Make sure you back up your Nintendo 3ds folder first.

 

[weika]

So I've been doing alot of googling lately and I'm getting more and more confused on the subject; which is updating my japanese new3DS (8.1.0-0J) to 9.0-9.2J for installing CFW reliably.

I do have both blue & red gateway cards and I'm aware there's a way with cubic ninja and a webserver but supposedly it doesn't work anymore?
Is there anything I could do with just the gateway?

 

[Temptress Cerise]

So I've been doing alot of googling lately and I'm getting more and more confused on the subject; which is updating my japanese new3DS (8.1.0-0J) to 9.0-9.2J for installing CFW reliably.

I do have both blue & red gateway cards and I'm aware there's a way with cubic ninja and a webserver but supposedly it doesn't work anymore?
Is there anything I could do with just the gateway?

With just the gateway? Pretty sure you'll need a HBL entry point first.
This might be relevant though.
Link: http://gbatemp.net/threads/8-1j-n3d...ard-update-to-9-2j.424265/page-3#post-6415269

Could always ask there.