Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,114,276
  • Replies Replies 47,965
  • Likes Likes 66
I get errors while running hekate and atmosphere on my switch, It crashes. Serial number is good. once it boots into the home it crashes
 
Unfortunately, there are no other apps that support installation of .XCI files. You may be stuck converting them to .NSP files at least until ReiNX fully implements .XCI support.
Guys I finally figured out the issue. I think. Well it's installing, I'm just not 100% what the issue was. I decided to use Kosmos as I read something about patches being the possible culprit. Now n1dus is installing and there's no problems. Woohoo!

Now I don't have to get off my fat ass to dig through a pile of games to play something :)
 
Is there any chance that ps2 emulator will be added to the hb app store i only ask cause the ps1 emulator is on the hb app store. Also any chance for game cube emulator being added to the hb app store in the future?
 
Picked up a brand new hackable Switch last week running 4.1.0 on OFW and loaded up Hekate and Atmosphere after full NAND backup. So far I've done nothing aside from play with the Retroarch NRO and haven't gone once into OFW or loaded a single NSP or updated beyond 4.1.0. I hear you can use a modified eShop NSP to access Homebrew with full RAM access without a ban risk though so now I'm curious.

If I switch from CFW to OFW from the Hekate launcher and try to access the eShop via normal Wi-Fi (no 90DNS) is this a high risk scenario for a ban in itself? I presume it's only risky to access eShop from within a CFW.

Also, would it be better to update to latest system update officially or via Choi at this point? I know the former burns fuses but I'm more concerned about Choi triggering a ban accessing the eShop in OFC. That is unless updating officially kills Hekate/CFW access...

Thanks for any help here!
 
Last edited by axiomjunglist,
Anyone know what s the easiest way of keeping your home brew apps and cfw up to date?

I'm using Kosmo atm and switch has been in airplane mode since I hacked it.
 
Hi, looking for advice from the geniuses on here! I''ve been using sxos for quite a while and have finally created an emunand. I'm on 6.1 at the moment but plan to update to 6.2 with choidujournx.

After creating the emunand I now have an emutendo folder on my sd card - am I supposed to transfer everything from my nintendo folder into that folder? Or only some files? Or just leave it as is? Any help much appreciated!
 
Need help, ok so I have SX OS installed emuNAND 6.1.0 and on sysNAND I am on 4.0.1. I updated with ChoiDujourNX with exFAT support. In the SX OS boot menu emuNAND is currently enabled. When I disable it and try to boot CFW the nintendo logo comes up but quickly disappears and I am left with a black screen and have to force shutdown. Is this happening because I updated in emuNAND? Also when I boot up into sysNAND is there anyway to NOT get the “update system to use microSD card” notification? Thank you for the answers!
 
Has anyone made a list of the emulators that exist to run on the Switch?

Also, any way to figure out what firmware a game needs to run? I got Smash Bros and I don't know what version of firmware it uses.
 
Probably a dumb question, but with gcdumptool there's an option to "dump certificates" from your individual game card. Do I want to select "yes" for a legitimate game card dump?

I like gcdumptool because it verifies your dump with an online database to determine if it's good quality. It also names the .xci files instead of just putting the code for the title ID, unlike WAIN.
 
I backed up my 2.1.0, but they are all separated:

w9a90w.jpg


In the videos I saw, it's normally just one "rawnand.bin" so I am confused. Should I just accept this result or will it be screwed up if I ever revert it.
 
I backed up my 2.1.0, but they are all separated:

w9a90w.jpg


In the videos I saw, it's normally just one "rawnand.bin" so I am confused. Should I just accept this result or will it be screwed up if I ever revert it.
Is your SD card formatted FAT32? If so....why? That would be the biggest reason for a file size below 4gb
 
I backed up my 2.1.0, but they are all separated:

w9a90w.jpg


In the videos I saw, it's normally just one "rawnand.bin" so I am confused. Should I just accept this result or will it be screwed up if I ever revert it.

It is normal since your SD card is Fat32.
 
Is your SD card formatted FAT32? If so....why? That would be the biggest reason for a file size below 4gb

I am on older firmware that doesn't support exFAT, so I needed to format to FAT32 so I could still use a microSD with 2.1.0. But now, I'm making the backup so I can update to 4.1.0 on ChoidujourNX without burning fuse. Can I just merge all the "bin" files on the computer or will that mess it up?
 
I am on older firmware that doesn't support exFAT, so I needed to format to FAT32 so I could still use a microSD with 2.1.0. But now, I'm making the backup so I can update to 4.1.0 on ChoidujourNX without burning fuse. Can I just merge all the "bin" files on the computer or will that mess it up?
Dunno, I'd just keep them as is until you need to use them.

Also I guess there's ways to get exfat support without updating. I had already updated to 4.0 so I don't think I have that ability.

You didn't update so you could use the Deja vu exploit, right?
 

Site & Scene News

Popular threads in this forum