Hacking My N3DS Internet Browser Won't open!!!!!!

[Vrpndt]

I was f*cking around with my N3DS XL when I tried to make a CIA out of the Internet browser. After Installing the CIA, nothing happened so I tried to open the Internet browser and then I got a Luma 3DS error. I'll post a link to the crash dump in the comments. PLZZZZZ HELP!!!!!!!!

 

[BaamAlex]

Why do you need the internet browser for .cia files?

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

Or why do you want to make the Internetbrowser to a cia file?

 

[Vrpndt]

Here's the crash dump:https://mega.nz/#!ZdMhFCgR!8H0oBH-hyQQoo3m9BauBh8L_roW8ZwlXAPw9hOCqeFY

 

[TurdPooCharger]

You're not suppose to use FBI when installing system title *.cia files, which specializes in SD card titles. That job is for sysUpdater, which specializes in CTRNAND titles.

And this folks, is why it's especially important not to mess around with your 3DS firmware unless you made a NAND *.bin image backup. If you plan to screw around with CTRNAND for experience, it's best you learn or sandbox with an EmuNAND and not on the SysNAND.

***

@Vrpndt, if your n3DSXL is a EUR region model, as per [3dbrew] Title list for EUR region's New 3DS Internet Browser (SKATER).

• GodMode9 → [1:] SYSNAND CTRNAND/title/00040030/20008802/content/
• On both the two (2) *.app files → NCCH image options... → Encrypt file (...) → Encrypt inplace → etc.

 

[KleinesSinchen]

And this folks, is why it's especially important not to mess around with your 3DS firmware unless you made a NAND *.bin image backup. If you plan to screw around with CTRNAND for experience, it's best you learn or sandbox with an EmuNAND and not on the SysNAND.

Agreed. I did not understand this in the first place:
Dump browser to CIA → Install CIA on same device. Huh??

You're not suppose to use FBI when installing system title *.cia files, which specializes in SD card titles. That job is for sysUpdater, which specializes in CTRNAND titles.

This leads to another questions: Why is the end user supposed to install system titles with FBI in case of broken DS-functionality (“troubleshooting page”)? There must be some kind of difference. I mean this actually works.

 

[BaamAlex]

NAND *.bin image backup

I wanted to ask that too. If i have to restore my backup because i crashed the system. Will my games survive after a backup restore? Or do I practically start "from scratch"?

 

[TurdPooCharger]

This leads to another questions: Why is the end user supposed to install system titles with FBI in case of broken DS-functionality (“troubleshooting page”)? There must be some kind of difference. I mean this actually works.

I'm not familiar of 3DS homebrew before the time of CTRTransfer and boot9strap, but there were several *.cia installers other than FBI such as NASA, [SOON! / SOON!2], and [sysUpdater / SafeSysUpdater / sysDowngrader].

In the early days of 3DS hacking, EmuNAND/RedNAND, downgrading, and region changing the 3DS firmware were very much relevant homebrew options in playing out-of-region games, maintaining compatible with a 3DS flashcart, and playing newer titles that required increasingly higher firmware versions. (As far as I could gather) installing system titles or CTRNAND *.cia was best done with sysUpdater, even though soft bricking was a big risk and recovery options back then were scarce. I believe FBI was in its infancy, NASA was the go to SD card CIA installer up to around firmware 9.2, and sysUpdater was being developed to tackle installing system titles, especially for those running in the background you couldn't just reinstall over unless this was done in extended memory and the 3DS had to be restarted (I don't know for sure). ¯\_(ツ)_/¯

Anyway, to answer your question why you can install SysNAND TWLNAND titles (DSi firmware files) with FBI, I think it's because the 3DS running in its NATIVE_FIRM (3DS mode) can modify its TWL_FIRM (DSi mode), which is not needed until booting a DSiWare game or DS game cart / flashcart. I haven't tried installing a full firmware package found at that darth site with FBI but did learn one can install any CTRNAND title so long it's not in use (ie; Health & Safety, AR Games, System Settings). Those that are system modules ← ??? I also have no clue how these react with FBI.

There's a second part to this picture, and it concerns with the *.cia files themselves. You may have heard that there are two (2) types of CIAs: standard and legit.

Your standard build CIAs are those with fake or spoofed tickets. These were either stripped from legit purchased CIAs or downloaded through a CDN downloader (freeShop, CIAngel, tikShop, Villain3DS, Nintendo eShop with nonlegit tickets sourced from TIKdevil). Standard (& decrypted) CIAs are universally installable with any 3DS systems that has custom firmware because the CFW ignores the security in checking if the tickets are "real".

Your legit CIAs are of course those you purchased from Nintendo eShop signed with a valid ticket or encrypted specifically to only your 3DS system and no one else's. A litmus test in determining whether a CIA is legit or standard is if the custom firmware is removed or not present (ie, stock firmware), does that title persists or still work?

This leads to another subtype: universal legit CIAs. You may have seen several games bundled with 3DS/2DS special editions from the factory such as Mario Kart 7, Pokemon X/Y, and The Legend of Zelda - Ocarina of Time 3D. What makes these unique is the fact you can install them with custom firmware, uninstall the CFW, and continue to keep them as yours to own and play. Only Nintendo has the master key in signing or creating universal legit CIAs... Which this leads us to another point.

All the CTRNAND titles that makes up your 3DS firmware have universally signed legit tickets and are supposed to be dumped as legit CIAs in GodMode9. If you dump a CTRNAND title as a standard CIA and install that stripped of its legit ticket, installing it in FBI or sysUpdater will break its encryption. While this can be fixed with GodMode9 by encrypting the previously mentioned *.app, this is a band-aid fix as I believe if @Vrpndt were to ever removed his custom firmware, his n3DS browser would stop working again.

The real fix is to go that darth site, download the n3DS EUR 11.8 firmware package (1c27f72bacc76493d770fdf658b5ee27), and reinstall the 0004003020008802.cia that has its legit ticket intact.

@KleinesSinchen, I was going to talk more about the funny business of swapping places of the *.app/*.nds of an already installed DSiWare game with a different game found in the SYSNAND TWLN drive. I think you can swap the *.sav as well, so you can have something like Zelda 4 Swords on HOME Menu but manually put in Sudoku.

So while you probably can use modern versions of FBI to install (most??, any?) system titles, I use sysUpdater out of habit as that's how the really old timers did it.

I wanted to ask that too. If i have to restore my backup because i crashed the system. Will my games survive after a backup restore? Or do I practically start "from scratch"?

Unless the NAND back up was made recently in terms of the games added to your library collection, restoring a NAND *.bin image will result in losing your tickets. Your 3DS will acknowledge the existence of your titles marked with X's in:

• System Settings → Data Management → Nintendo 3DS → Software

but does not believe you own those titles and will not show them in HOME Menu.

Unless you made backups of your saves and extdata, you would either have to reinstall games, saves, extdata, etc. by:

(1) mounting the Nintendo 3DS folder with your movable.sed using the desktop program fuse-3ds and Python script 3ds-save-tool to decrypted and extract your saves in a form that Checkpoint or JKSM save manager can use. This is if you have your titles backed up as *.cia already.
​

or

(2) following a sucky and painstaking procedure dumping your games in GodMode9, extracting the encrypted 00000001.sav files, reinstalling said dumped CIAs, implementing those *.sav back to their directories, and then backing up + restoring the saves with Checkpoint or JKSM to bypass anti-cheat save protection.
​

Basically, don't find yourself in this scenario by following good practice in backing your saves/extdata with save manager of choice.

 

[Vrpndt]

a NAND *.bin image

Well, I do have a NAND backup on my PC so could restoring it fix the problem?
BTW sorry I didn't reply earlier, I've been busy with things.

 

[KleinesSinchen]

Well, I do have a NAND backup on my PC so could restoring it fix the problem?
BTW sorry I didn't reply earlier, I've been busy with things.

If the image is intact it probably will. It would be a good idea to make another image of the current state before attempting this. Just in case... And take account of TurdPooCharger's warnings:

Unless the NAND back up was made recently in terms of the games added to your library collection, restoring a NAND *.bin image will result in losing your tickets. Your 3DS will acknowledge the existence of your titles marked with X's in:

• System Settings → Data Management → Nintendo 3DS → Software

but does not believe you own those titles and will not show them in HOME Menu.

Unless you made backups of your saves and extdata, you would either have to reinstall games, saves, extdata, etc. by:

(1) mounting the Nintendo 3DS folder with your movable.sed using the desktop program fuse-3ds and Python script 3ds-save-tool to decrypted and extract your saves in a form that Checkpoint or JKSM save manager can use. This is if you have your titles backed up as *.cia already.
​

or

(2) following a sucky and painstaking procedure dumping your games in GodMode9, extracting the encrypted 00000001.sav files, reinstalling said dumped CIAs, implementing those *.sav back to their directories, and then backing up + restoring the saves with Checkpoint or JKSM to bypass anti-cheat save protection.
​

Basically, don't find yourself in this scenario by following good practice in backing your saves/extdata with save manager of choice.

 

[TurdPooCharger]

Well, I do have a NAND backup on my PC so could restoring it fix the problem?
BTW sorry I didn't reply earlier, I've been busy with things.

Unless this NAND *.bin image is super new between the time you made it until now where you did not install any new games, I would not recommend restoring the SysNAND because that make you lose all your tickets. No tickets = no show on HOME Menu.

Approach A

1. Backup all your saves and extdata with Checkpoint or JKSM save manager should anything bad happen.

2. Find / go to that darth site as was mentioned in my above post and reinstall the EUR region New 3DS browser system applet *.cia with FBI and/or sysUpdater. Install only that *.cia and no other ones. I'm assuming your UK flag flairs means you have a EUR n3DS.​

Approach B

1. Back up all your saves and extdata with Checkpoint or JKSM.
2. If you have GodMode9 v1.7.1, (HOME) → Scripts... → NANDManager → <X> Backup SysNAND → etc. (Just in case).
   
3. (HOME) → Scripts... → GM9Megascript → Dump Options → System File Dump Options →
   • Dump [ LocalFriendCodeSeedB / SecureInfoA / movable.sed / ticket.db / title.db / import.db / certs.db ]
4. (HOME) → Scripts... → NANDManager → <R> Restore SysNAND (Safe) → etc. (With the older NAND *.bin image you saved).
   
5. (HOME) → Scripts... → GM9Megascript → Inject Options →
   • Inject [ LocalFriendCodeSeedB / SecureInfoA / movable.sed / ticket.db / title.db ]
   • This bulletin has nothing to do with fixing the browser issue. @annson24, where's import and certs option? どうして?!
6. Update your 3DS firmware and check if the browser's fixed.

 

[KleinesSinchen]

Unless this NAND *.bin image is super new between the time you made it until now where you did not install any new games, I would not recommend restoring the SysNAND because that make you lose all your tickets. No tickets = no show on HOME Menu.

Sorry. I was a bit fast and incautious; should have emphasized this more. I'm truly not myself today.

 

[TurdPooCharger]

Sorry. I was a bit fast and incautious; should have emphasized this more. I'm truly not myself today.

Nah, you're fine. 3DS homebrewing, when you get down to nitty gritty, is WAAY too complex and shiet. Something that's relatively simple to hack for the end user, but when you go down that rabbit hole figuring out how anything works... Oh mein Gott.

 

[KleinesSinchen]

Nah, you're fine. 3DS homebrewing, when you get down to nitty gritty, is WAAY too complex and shiet. Something that's relatively simple to hack for the end user, but when you go down that rabbit hole figuring out how anything works... Oh mein Gott.

It was just a fallacy. I though about myself: I have so many backups (not only 3DS, my computer backup... forget it).
If it happened to me, image from the current status, restore last backup, done.
At least I pointed out to backup the current status.

Oh mein Gott.

German fragment. You really brightened up my bad day! And thanks for the detailed explanation above.