Sanrasxz

joined 2 years ago
[–] Sanrasxz@lemmy.dbzer0.com 1 points 8 months ago

Try searching for rcm jig on Amazon.

[–] Sanrasxz@lemmy.dbzer0.com 2 points 9 months ago (1 children)

Hey Neo, would you be interested in helping to moderate this community? If so, let me know and I will add you.

[–] Sanrasxz@lemmy.dbzer0.com 2 points 10 months ago

Go with separate nsp for base, update, and dlc. That is the standard way to dump games. Combining them into one is a bad idea and you'll be stuck with an outdated bundled update later if a new update comes out.

[–] Sanrasxz@lemmy.dbzer0.com 1 points 10 months ago (2 children)

I mean all the v1 needs is an rcm jig and a pc. Nothing else.

[–] Sanrasxz@lemmy.dbzer0.com 2 points 11 months ago (1 children)

I don't think Scires will do anything more than that. He is just covering his ass, because providing a feature in fusee that is used for nothing but piracy isn't a good look.

That's why he mentioned looking for other types of IPS patches. If he found any, he likely would've kept the feature and used it as justification to leave it in fusee.

[–] Sanrasxz@lemmy.dbzer0.com 1 points 11 months ago (2 children)

I hate AIOs in general, but this isn't as bad as some I've seen. Still got quite some issues though. You should clean up that contents folder.

Lots of completely useless stuff there. For example 010000000001013 can actually cause problems during boot and doesn't do anything. A lot of other random sysmodules that are unnecessary to 99% of users as well.

Crap dnsmitm config that uses the 127.0.0.1 *nintendo* line, which is very general and uses more resources to filter. The rentry or nhguide's dnsmitm configs are far better.

Mission control is installed, but it's BT patches are missing, so it's not going to work.

There's a system settings file in config for some reason, but doesn't appear to have any modifications.

The Hekate ini has no way to boot syscfw for users that want it. (And uses cal0blank even though exosphere.ini already exists)

[–] Sanrasxz@lemmy.dbzer0.com 2 points 11 months ago

Do note 2.74 is the unstable fw with 300mhz clock. I would recommend not using it.

[–] Sanrasxz@lemmy.dbzer0.com 5 points 11 months ago (3 children)

Have you tried updating the modchip to latest 2.75 FW from rehius just to make sure the modchip FW is not corrupt?

You can find the firmware repo here: https://github.com/rehius/usk/releases/tag/PicoFly_2.75_2023.09.09_08-16

[–] Sanrasxz@lemmy.dbzer0.com 4 points 11 months ago (1 children)

I would prefer nsp/nsz since those are eShop dumps and intended to be installed into the system.

Xcis are gamecard dumps and weren't intended to be installed, so the installer has to modify it in order for the console to pick it up as a digital copy.

Basically, the nsp is just cleaner - you install the game without any modifications, and just register the ticket for it to the system.

[–] Sanrasxz@lemmy.dbzer0.com 3 points 11 months ago

Don't believe so, but you can just search for games you want by highlighting the New Games tab and then clicking the search button.

 

Introduction

Japanese Switch consoles (XAW, XKJ, XTJ) are unable to use higher 5GHz channels due to their WiFi chipsets being set to the JPN WiFI region in PRODINFO which restricts their use. You can manually change this region code to unlock the channels and use them in the USA or EU if you have an imported Japanese console.

This guide is meant for use with emuMMC, but it can be followed on sysMMC as well by mounting eMMC RAW GPP in Hekate to NxNandManager instead of the SD card's emuMMC. Be careful and keep PRODINFO backups if messing with PRODINFO on sysMMC.

Getting Started

We'll be using NxNandManager, and HxD to edit the PRODINFO. If you haven't dumped your console's prod.keys yet, you will also need to do that. Use your own console's prod.keys, this is important!

Downloads:

Preparations

  1. Download NxNandManager, and extract the zip file.
  2. Download and install HxD by running the setup.exe after extracting its zip.

If you haven't dumped your keys yet, I'll go over it quickly here. You can skip this if you have already dumped your console's keys.

  1. Download the latest release of Lockpick_RCM.bin, linked above.
  2. Place this file in /bootloader/payloads on your SD card, and boot into Hekate.
  3. Go to the Console Info tab, and tap the Lockpick RCM button.
  4. Click the power button once in Lockpick to dump keys from sysMMC, then click power again, then highlight the option to power off and click power button once to confirm.

Dumping PRODINFO

We are now ready to go. First, we will dump the PRODINFO that needs editing:

  1. Take out the SD card from your Switch with emuMMC and insert it into your PC.
  2. Run NxNandManager.exe on your PC and grant Admin when requested.
  3. In NxNandManager, go to the Options tab and click Configure keyset
  4. Click Import Keys From File, and navigate to /switch on your SD card. Select prod.keys and hit Open. Then hit the Save button in the Configure keyset window. [Reference Picture]
  5. Click File in NxNandManager, and select Open Drive
  6. Select your emuMMC partition on your SD. (This will be about 29GB on V1 and V2 consoles, and about 59GB on OLED consoles.) [Reference Picture]
  7. Select PRODINFO in the partition list.
  8. Select the Advanced Copy button on the right pane.
  9. Select Decrypt in the options, and set a file path to where you want to dump the file. (Any working directory you want to use is fine). [Reference Picture]
  10. Hit Dump to dump the decrypted PRODINFO to your PC.

Editing PRODINFO

  1. Run HxD on your PC, and open the dumped PRODINFO.bin file.
  2. In HxD, click on the Search tab and select Go to. Input 0080 and hit OK.
  3. Copy the North America WlanRegionCode data, provided below:
01 00 00 00 00 00 00 00 52 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4E C4
  1. Go back to HxD, and highlight range 0080 through 020F in HxD. [Reference Picture]
  2. Right click on the highlighted range, and select Paste write. [Reference Picture]
  3. The data should be written to the selected range, and it should turn red to indicate unsaved data. [Reference Picture]
  4. At the top of HxD, select Save to save your PRODINFO changes, and then exit HxD.

Restoring Modified PRODINFO

  1. Open NxNandManager on your PC again. Go to File, and select Open File.
  2. Open the PRODINFO.bin file you just modified with HxD. Right click on PRODINFO in the left pane, and select Encrypt & dump to file. [Reference Picture]
  3. Select a folder (any folder you can find later) to dump the encrypted PRODINFO to, and hit OK. You should find a PRODINFO.enc in the folder you specified.
  4. Select File in NxNandManager, and then select Close file/drive.
  5. Select the File tab again, and select Open Drive
  6. Select your emuMMC partition on your SD.
  7. Select PRODINFO in the partition list on the left pane.
  8. On the right pane, select Restore from file. Find your PRODINFO.enc file, and open it. [Reference Picture]
  9. Accept the prompt to write PRODINFO, then exit NxNandManager.

Finishing Up

You should now have a USA WiFi region code in your emuMMC's PRODINFO, allowing you to use the same channels as USA Switches. Boot into Hekate, and launch emuMMC, then try connecting to any 5GHz network you weren't able to before.

For example, my 5Ghz network on Channel 165 now works fine:


[–] Sanrasxz@lemmy.dbzer0.com 2 points 1 year ago

To add onto this, this is THE best way to get into Pro shops and pro-only access stashes like NekoDrive or Tits Pro. The Missing Content finder discord can help you locate missing content to buy and donate.

[–] Sanrasxz@lemmy.dbzer0.com 1 points 1 year ago* (last edited 1 year ago)

Why on Mariko I don't have the possibility to boot on OFW? It seems that rentry guide add the code for stock nand only for Erista.

You can, just replace your ini. Open your hekate_ipl.ini file with Notepad. (it's inside the bootloader folder on your SD)

Delete everything inside the ini and paste the following in:

[config]
autoboot=0
autoboot_list=0
bootwait=3
autohosoff=0
autonogc=0
updater2p=1
backlight=100

[Atmosphere FSS0 emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emu_boot.bmp

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

[Stock sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/stock_boot.bmp

Can I update emuNand (file) to lastest fw? I'm on 15.0.0 now

Yes. You can update the emummc with Daybreak. Boot into OFW (Stock), and update it to latest.

Then follow this guide to dump your FW from stock and install it on emu: https://nh-server.github.io/switch-guide/extras/updating/#updating-emummc-by-dumping-an-updated-firmware-from-your-sysmmc


I see different file type for game like xci and nsp what is the difference? Should I have to use app like goldleaf?

DBI can install all Switch game files (NSP, NSZ, XCI, XCZ). See this guide for installing them: https://rentry.org/NSUSBInstall/#dbi-installer-mtp

 

Just need a simple torrent box. I've tried using the transmission-openvpn docker container in the past, but it keeps on having issues, either with the systemd service detailed in the manual not working properly, or fuckery with how it saves files, where it makes them owned by root on the host.

Is docker still the best way to go about this? I've used it in the past because I need only the client itself to be on the VPN, but the WebUI needs to be accessible on my actual network. The docker container made this split tunneling setup easy to do.

I'll also be running Jellyfin on the same machine, which also needs to be a local lan server, so running the VPN on the system globally isn't an option, since Jellyfin and the WebUI need to not go through the VPN.

So, any suggestions for what I should do?

view more: next ›