Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,098,932
  • Replies Replies 47,953
  • Likes Likes 66
My user file on my emummc stopped working and when i launched it the nintendo message popped up saying that user didnt match previous ones so cant use my files or play my games i backed up. I think i might of accidentally delete prodinfo in nxnand manager but idk. maybe i can restore with my keys i backed up? thanks for the help

If you have backup of the prodinfo you can try to restore it. Since it is an emunand worse case you can start from scratch if you didn't blank out serial number in sysnand.
 
It has been a hot minute since I have dealt with these things, I just need a yes or a no:

Is launching retroarch through a forwarder the same thing as launching it via title override (to have full access to the ram)? Are both methods equivalent to each other?

Unrelated, is there a reason FW 19.0.1 is not available for download? Some new game updates are starting to require it (specifically, the Dragon Quest III HD 2D Remake v1.0.1).
 
Is launching retroarch through a forwarder the same thing as launching it via title override (to have full access to the ram)? Are both methods equivalent to each other?
For almost all effects is the same using a forwarder or title override.

Unrelated, is there a reason FW 19.0.1 is not available for download? Some new game updates are starting to require it (specifically, the Dragon Quest III HD 2D Remake v1.0.1).
FW is indeed available for download if you search on google 19.0.1 ccec27e

ccec27e its the release ID for sure you will find a source for download it.
 
I picked up two switches and my first switch has had driver problems for a while now.

Hekate USB mode for SD card says "Starting UMS". Zadig reports it as "UMS" "Usbstor" and either ejects or connects as usb, mounts it as a drive, but transferring files fails/crashes. After a few minutes, it ejects when idle. In device manager, it says "hekate sd raw usb device" under disk drives. How can I fix this, please?

I'm also having problems with DBI. Transfers start but stall after a few minutes.

Also having an issue with usb file transfer in the hbmenu apps, it just reports "libusbk usb devices -> DBI" in the device manager.

I can't use a file explorer at all. How can I fix this issue? This only happens on one switch, the other two are fine. Could it be the micro sd card going bad? This one is using syscfw while the other two are emumcc.
You could try H2Testw to test the sd card with Hekate USB mode. The program tests the free space, so nothing is deleted.

(https://www.heise.de/download/product/h2testw-50539)
 
  • Like
Reactions: rsx
For almost all effects is the same using a forwarder or title override.
That's great. I just noticed that retroarch, running via forwarder, is picking up my playstation bios files correctly. I never got retroarch to acknowledge them running via title override or through the applet mode. Very strange, I had the right files with the right checksums and names, the only thing different is running it via forwarder :unsure:. Oh well, it's working!
FW is indeed available for download if you search on google 19.0.1 ccec27e
Sweet, is it supported by Atmosphere at the moment? Maybe it just hasn't made its way onto the AIO Switch updater yet, the way I normally download my firmware. The darthsternie website doesn't have it either. Although it doesn't normally take 2 months for the firmware to appear there, so I'm wondering. I did find 19.0.1 on someone's github repo posted on October 28th, is this a reputable source?
 
It was a driver issue, works now.

Another problem: Since upgrading to 19.0 I'm trying to change the switch boot logo and having problems every step of the way. Google turns up nothing.
 
I have some issues with my relatively new Switch V2. The battery life seems not as good as what it is supposed to be.

When playing BOTW, around 2 min 45s of playing time cost my switch one percent of battery life (I have counted manually multiple times), which means approximate 275 mins of total playing time (around 4.5 hrs).

It should be 5-5.5 hrs according to Nintendo's official statement and numerous online tests I have watched. I have tried to do some full charge cycles for calibration but it hasn't seemed to be improved.

The attachment is a screenshot of the battery performance when I play BOTW (I have checked in Hetake and it shows the same results in term of battery capacity).

Is there anything wrong? Thanks in advance.
 

Attachments

  • ef88dd1b-4a60-4bee-9e8b-031aff1ba577.jpg
    ef88dd1b-4a60-4bee-9e8b-031aff1ba577.jpg
    140.3 KB · Views: 33
Last edited by sk4vn,
I have some issues with my relatively new Switch V2. The battery life seems not as good as what it is supposed to be.

When playing BOTW, around 2 min 45s of playing time cost my switch one percent of battery life (I have counted manually multiple times), which means approximate 275 mins of total playing time (around 4.5 hrs).

It should be 5-5.5 hrs according to Nintendo's official statement and numerous online tests I have watched. I have tried to do some full charge cycles for calibration but it hasn't seemed to be improved.

The attachment is a screenshot of the battery performance when I play BOTW (I have checked in Hetake and it shows the same results in term of battery capacity).

Is there anything wrong? Thanks in advance.
Every game will drain it differently but 4.5 hour seems pretty good still.
To see battery health, go into hekate -> console info -> battery. Capacity full is your current capacity, capacity (design) is the stock capacity. so just divide current by stock to get your battery health %. 0-100%.
 
Last edited by BigOnYa,
Trying to change the splash screen for Atmosphere and followed the script:

A script can be found inside the source tree (/utilities/insert_splash_screen.py) for inserting a custom splash screen into a release binary. To do so, execute the following command on the script:python insert_splash_screen.py <path to your splash screen image> <path to /atmosphere/package3 on your SD card>

I opened a cmd prompt, connected it, put everything on the sd card then dragged/dropped the paths and according to file explorer, package3 was saved. But it still shows the default boot logo. I also tried it by copying everything to my pc. No good. Any idea?
 
Every game will drain it differently but 4.5 hour seems pretty good still.
To see battery health, go into hekate -> console info -> battery. Capacity full is your current capacity, capacity (design) is the stock capacity. so just divide current by stock to get your battery health %. 0-100%.
Thanks for the reply. The battery health is good as shown in my screenshot, that's why I feel confused.
 
  • Like
Reactions: BigOnYa
is it supported by Atmosphere at the moment?
Yes. Please do not use AIOs packages. Follow the guide: https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/

Trying to change the splash screen for Atmosphere and followed the script:

A script can be found inside the source tree (/utilities/insert_splash_screen.py) for inserting a custom splash screen into a release binary. To do so, execute the following command on the script:python insert_splash_screen.py <path to your splash screen image> <path to /atmosphere/package3 on your SD card>

I opened a cmd prompt, connected it, put everything on the sd card then dragged/dropped the paths and according to file explorer, package3 was saved. But it still shows the default boot logo. I also tried it by copying everything to my pc. No good. Any idea?
If you are using hekate FFS0 method the splash image is controlled by hekate_ipl.ini file

Which bootloader do you use?
 
acording to some sources (cannot post link coz is russian) there will be final fw for ns 20.xx that will cripple very bad atmosphere and other installers, this update will be available at the end of jan 25
 
  • Wow
  • Like
Reactions: impeeza and BigOnYa
acording to some sources (cannot post link coz is russian) there will be final fw for ns 20.xx that will cripple very bad atmosphere and other installers, this update will be available at the end of jan 25
May be. They tried something like that for 3DS but the community got everything working back to normal in seconds
 
Last edited by impeeza,
If you have backup of the prodinfo you can try to restore it. Since it is an emunand worse case you can start from scratch if you didn't blank out serial number in sysnand.
I have boot 0 & 1 with all the numbered rawbin files then I have the full RAWNAND.bin back up. Also have the prodkeys. how do I restore the prodinfo with those? Which of the numbered rawbin files has it? thanks
 
I have boot 0 & 1 with all the numbered rawbin files then I have the full RAWNAND.bin back up. Also have the prodkeys. how do I restore the prodinfo with those? Which of the numbered rawbin files has it? thanks

The nand backup is probably your sysnand backup, the rawnand is your entire nand, you can try to open it with nxnandmanager and see if you can export your prodinfo.
 
  • Like
Reactions: impeeza
The nand backup is probably your sysnand backup, the rawnand is your entire nand, you can try to open it with nxnandmanager and see if you can export your prodinfo.

Do you know if the backup option in Hekate (Backup eMMC) include both emuNand and sysNand?
Also, what's the difference between "SD emuMMC Raw Partition" when toggled on or off during backup?
 
  • Like
Reactions: impeeza

I'm a little confused. I do not use any AIO packs, I only use the convenient updater to download the switche's FW files, then install those through daybreak after manually updating to the latest atmosphere, hekate, and sys-patch (downloaded from their respective github pages ofc). Is there anything wrong with the switch firmware downloads being served by the AIO updater app? I could manually download the firmware, but that seems like extra work to me.

Edit: Had a look at the guide, and that is what I am already doing, save for dumping my own FW files, on account of the fact that I do not have an up-to-date sysnand. Otherwise I probably do that.
 
  • Like
Reactions: impeeza
Fixed it, thanks.

Having an issue: Installs fine, then "The software was closed because an error occurred" Just started happening with a lot of games that worked before. I installed using DBI.
 

Site & Scene News

Popular threads in this forum